[
https://issues.jboss.org/browse/JBJCA-847?page=com.atlassian.jira.plugin....
]
Logan McGrath commented on JBJCA-847:
-------------------------------------
I'm working on a fix. Here's the specific problems I've confirmed with how
they're being addressed:
* Executing "mvn test" gives java.lang.ClassNotFoundException.
** Could not reproduce, instead, the deployment failed with
org.jboss.jca.common.metadata.ParserException: "IJ010065: Missing mandatory jndi-name
attribute: connection-definition"
* Build errors due to package names starting with "java" rather than the TLPN
given when generating the code (com, org, net, etc.)
** Cause: generated pom.xml designates the source directory as src/main rather than
src/main/java.
** Resolution: remove source directory and test directory declarations from pom.xml.
* "The method XXX must override a superclass method" error:
** Cause: Maven compiler plugin is configured to for Java 1.5 source and target.
** Resolution: Configure the Maven compiler plugin for Java 1.6 source and target.
The generated POM is pretty hard to read, and it doesn't exactly follow a lot of the
"standard" Maven conventions. Here's the enumerated changes:
* I changed the declared version from 0.1 to 0.0.1-SNAPSHOT: the generated project is a
development version, after all, and this is the "default version" created in
many Maven archetypes
* Changed packaging to RAR from JAR: Maven projects should not produce primary artifacts
that are different from their declared packaging, and the generated POM tries to do just
that (bad!)
* Removed JAR and RAR plugins: Maven will use the default configurations for these
plugins, and also because of the above item
It may actually make sense to create a Maven archetype for use in place of the code
generator. The reason being that Maven can itself operate as a code generator, and you get
a much cleaner output.
Here's the diff:
http://pastebin.com/Va8AD2cY
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
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