maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Olivier Lamy (JIRA)" <j...@codehaus.org>
Subject [jira] (MCOMPILER-190) No compile errors with plexus-compiler-eclipse
Date Mon, 03 Dec 2012 09:08:14 GMT

     [ https://jira.codehaus.org/browse/MCOMPILER-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Olivier Lamy moved PLXCOMP-215 to MCOMPILER-190:
------------------------------------------------

                     Component/s:     (was: plexus-compiler)
    Attachment Licence (Apache)
: Grant license to ASF for inclusion in ASF works (as per the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache
License</a> ยง5)
                             Key: MCOMPILER-190  (was: PLXCOMP-215)
                         Project: Maven 2.x Compiler Plugin  (was: Plexus Components)
    
> No compile errors with plexus-compiler-eclipse
> ----------------------------------------------
>
>                 Key: MCOMPILER-190
>                 URL: https://jira.codehaus.org/browse/MCOMPILER-190
>             Project: Maven 2.x Compiler Plugin
>          Issue Type: Bug
>    Affects Versions: 3.0
>         Environment: Mac OS X 10.8.2 x86_64
> JDK 1.6.0_37
> Maven 3.0.4 (r1232337)
>            Reporter: Peter Palmreuther
>              Labels: compiler, eclipse
>             Fix For: 3.1
>
>         Attachments: pce.tar.gz
>
>
> I'm trying to make use of plexus-compiler-eclipse by configuring maven-compiler-plugin
(3.0) with a compilerId of 'eclipse' and dependency to plexus-compiler-eclipse, version 2.0
(couldn't select 2.0 in affects version above, so I left blank).
> I have java classes that definitely should raise a compiler error.
> 'mvn compile' gives
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.0:compile
(default-compile) on project sample: Execution default-compile of goal org.apache.maven.plugins:maven-compiler-plugin:3.0:compile
failed: basedir ${project.basedir}/target/classes does not exist
> on a clean project. Nothing else, no compiler error with respect to erroneous class.
And in fact no compiled class.
> But more critical to mee seems compilation on a non-clean project, i.e. 'target/classes'
exists.
> Output of 'mavn compile' than is
> [INFO] --- maven-compiler-plugin:3.0:compile (default-compile) @ sample ---
> [INFO] Changes detected - recompiling the module!
> [WARNING] Dummy.java:[5] Type mismatch: cannot convert from Integer to String
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD SUCCESS
> I've attached a sample project which can be used to reproduce the behavior.
> 1. Extract to an empty directory
> 2. chdir to this directory
> 2.a if in doubt: mvn clean
> 4. mvn compile
> 4.a error message about non-existent output directory
> 5. mkdir -p target/classes
> 6. mvn compile
> 7. see above mentioned warning, but build "succeeds" (of course no class file was generated)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message