[jboss-jira] [JBoss JIRA] (JBJCA-847) CodeGenerator Maven configuration misconfigures src/build paths, sets incorrect java version.
Murray Todd Williams (JIRA)
jira-events at lists.jboss.org
Wed Jul 11 16:59:12 EDT 2012
[ https://issues.jboss.org/browse/JBJCA-847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12705555#comment-12705555 ]
Murray Todd Williams commented on JBJCA-847:
--------------------------------------------
Actually, the *proper* approach would be to just fix the darned Maven RAR Plugin. I took at look at it's JIRA page (http://jira.codehaus.org/browse/MRAR) and it's pretty obvious that there's nobody at the helm. This amazes me since RAR is one of the eight native Maven <packaging> types! (http://stackoverflow.com/questions/5544019/what-are-all-the-default-maven-packing-types) and is part of Maven's default built-in functionality!
But I don't happen to have oodles of time to take on another Open Source volunteer effort (working on JBoss stuff is much more exciting and fruitful) so the best thing I think is to "work around" the Maven RAR plugin that is so long-in-the-tooth. (5 years since its last major update!)
> CodeGenerator Maven configuration misconfigures src/build paths, sets incorrect java version.
> ---------------------------------------------------------------------------------------------
>
> Key: JBJCA-847
> URL: https://issues.jboss.org/browse/JBJCA-847
> Project: IronJacamar
> Issue Type: Bug
> Components: Code Generator
> Affects Versions: 1.1.0.Beta1
> Reporter: Murray Todd Williams
> Assignee: Jeff Zhang
> Labels: maven
> Attachments: jbjca-847.patch, pom.xml
>
>
> If one uses the CodeGenerator (via command line or Eclipse plugin) with the option to export to Maven, the resulting code (a) cannot be imported into an Eclipse Maven project, (b) cannot run a test via "mvn test" and (c) generates Eclipse code errors because the source/target are set to Java 1.5 but the @Override annotation is not allowed for Interface overrides in Java 1.5.
> (I've lumped these all into one JIRA ticket report because I think it can all be resolved with some tweaks to the pom.xml generation.)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list