You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Matthew Adams (JIRA)" <ji...@codehaus.org> on 2013/01/31 00:31:13 UTC
[jira] (MCOMPILER-200) Provide optional boolean parameter
Matthew Adams created MCOMPILER-200:
---------------------------------------
Summary: Provide optional boolean parameter <skipMain>
Key: MCOMPILER-200
URL: https://jira.codehaus.org/browse/MCOMPILER-200
Project: Maven 2.x Compiler Plugin
Issue Type: Improvement
Reporter: Matthew Adams
This issue relates to MCOMPILER-132; in fact, MCOMPILER-132 might just end up depending on this issue.
NB: I'm using ajc exclusively as my compiler.
Firstly, I can already instruct maven-compiler-plugin to skip test source compilation via the "<skip>true</skip>" parameter. I'm just asking it to do the same for compiling main code, because I don't want it to waste the time attempting to compile via javac when I know it's going to break. It doesn't make symmetrical sense that I can skip test source compilation and not main source compilation. I also acknowledge the argument made in MCOMPILER-132 that not all projects need compilation and should be able to skip it.
Secondly, I'm not comfortable using "<compilerId>aspectj</compilerId>" along with plexus-compiler-aspectj because it's woefully out of date (the latest version, 2.1, depends on aspectj 1.6.0, but the current ajc release is 1.7.1).
Lastly, I don't feel like I have enough control over the ajc compiler using compilerId aspectj. I prefer to use org.codehaus.mojo:aspectj-maven-plugin, binding execution id "default-compile" to the compile phase & execution id "default-testCompile" to testCompile.
--
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
[jira] (MCOMPILER-200) Provide optional boolean parameter
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MCOMPILER-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olivier Lamy closed MCOMPILER-200.
----------------------------------
Resolution: Duplicate
Assignee: Olivier Lamy
duplicate.
NOTE I have upgrade aspectj plexus compiler to last aspectj 1.7.1
test snapshot from https://oss.sonatype.org/content/repositories/plexus-snapshots
And nothing prevent overriding aspectj dependencies in compiler-plugin declaration.
just <dependencies> section in the plugin pom part.
> Provide optional boolean parameter <skipMain>
> ---------------------------------------------
>
> Key: MCOMPILER-200
> URL: https://jira.codehaus.org/browse/MCOMPILER-200
> Project: Maven 2.x Compiler Plugin
> Issue Type: Improvement
> Reporter: Matthew Adams
> Assignee: Olivier Lamy
>
> This issue relates to MCOMPILER-132; in fact, MCOMPILER-132 might just end up depending on this issue.
> NB: I'm using ajc exclusively as my compiler.
> Firstly, I can already instruct maven-compiler-plugin to skip test source compilation via the "<skip>true</skip>" parameter. I'm just asking it to do the same for compiling main code, because I don't want it to waste the time attempting to compile via javac when I know it's going to break. It doesn't make symmetrical sense that I can skip test source compilation and not main source compilation. I also acknowledge the argument made in MCOMPILER-132 that not all projects need compilation and should be able to skip it.
> Secondly, I'm not comfortable using "<compilerId>aspectj</compilerId>" along with plexus-compiler-aspectj because it's woefully out of date (the latest version, 2.1, depends on aspectj 1.6.0, but the current ajc release is 1.7.1).
> Lastly, I don't feel like I have enough control over the ajc compiler using compilerId aspectj. I prefer to use org.codehaus.mojo:aspectj-maven-plugin, binding execution id "default-compile" to the compile phase & execution id "default-testCompile" to testCompile.
--
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