[jboss-jira] [JBoss JIRA] (JBJCA-847) CodeGenerator Maven configuration misconfigures src/build paths, sets incorrect java version.

[Murray Todd Williams (JIRA)]

    [ https://issues.jboss.org/browse/JBJCA-847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12705481#comment-12705481 ] 

Murray Todd Williams commented on JBJCA-847:
--------------------------------------------

Logan, question for clarification: your new POM builds a JAR instead of RAR now? I'm confused... I thought the whole purpose was to build a resource adapter.

Granted, my own (manual) attempt at this has involved creating a Maven project with two sub-modules: one that builds the JAR and the other that packages the RAR. (And it seems like it might make sense to make a third that breaks the Connection and ConnectionFactory interfaces into a separate JAR that could be used by the end-users' applications.)

But I had also read somewhere that it was possible (although apparently not considered fully "proper") to write a slightly contorted Maven POM that would construct  a RAR, itself containing the classes in a compiled JAR.
                
> 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