[
https://issues.jboss.org/browse/JBJCA-847?page=com.atlassian.jira.plugin....
]
Logan McGrath commented on JBJCA-847:
-------------------------------------
No it's not, so the POM probably needs to be changed to be just a JAR. I'm still
wondering if a Maven archetype would work better than the code generator because you could
create the necessary composite project containing both JAR and RAR projects. The only
other solution is to do the "slightly contorted Maven POM", but that'll
leave a lot of Maven users scratching their heads.
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
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