[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=12705519#comment-12705519 ] 

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

Yeah, there was a reason for some of those contortions in the original POM template. If you see this reference...

http://www.mailinglistarchive.com/html/users@maven.apache.org/2010-02/msg00482.html

... (which is oddly one of the only discussions I could ever find in a lot of Google searching!) you'll get a clue on how to proceed. Actually, if one reads Maven's maven-rar-plugin documentation, specifically the bit about including the JAR file, it seems like Maven is supposed to automatically find the Java class files, compile them, and embed them as an internal JAR. It seems obvious that Maven's RAR plugin has been gathering a lot of dust since this is such an obscure activity.

I've put a few hours into this and have a POM that finally compiles, tests and packages. I haven't tested throwing the final RAR into JBoss yet, but I think I've solved almost all of the hitches. I'm going to upload my suggested POM (it's not a pom.xml template replacement, but it wouldn't take much to do that.) but merely an example.

Also, the Maven directory structure (which seems a little brain-dead to me, but I adhered to it) says that the xml configuration files should be in src/main/rar/META-INF, so ironjacamar.xml and ra.xml (if one is made) should be getting generated and dumped there.
                
> 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