[prev in list] [next in list] [prev in thread] [next in thread]
List: jibx-users
Subject: Re: [jibx-users] New user: questions on maven plugin (partial
From: "Alexandros Karypidis" <akarypid () yahoo ! gr>
Date: 2011-05-14 8:49:22
Message-ID: op.vvgqskxxn8mdop () vfgrl10a-cxyrg ! vf-gr ! internal ! vodafone ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Hello Don,
Thank you for your input!
I guess (1) makes absolute sense.
Regarding (2), you are correct that the generated classes are included in
the JAR archive. However, please see my later e-mail which explains why
this does not work in the multi-module config.The sequence of events which
explains why this happens is here:
http://www.mail-archive.com/jibx-users@lists.sourceforge.net/msg04655.html
For example: suppose I am building project "prjA" which contains "module1"
and "module2". In "module2" the jibx-maven-plugin is configured to
generate bindings, which also references classes from "module1".
As it is now, the plug-in generates classes in "module1/target/...".
However, "module1" has already been packaged by then so those classes
won't make it into the module1.jar archive...
Any ideas how to handle this?
Kind regards,
Alexandros
On Fri, 13 May 2011 22:56:05 +0300, Don Corley <don@donandann.com> wrote:
> Alexandros,
>
> Wow, that's a lot of questions. Let me see if I can help you.
>
> 1. If you run:
> mvn compile
> The JiBX binding compiler will not run. This is the correct behavior.
> Remember JiBX adds byte codes AFTER your code is >compiled (in the
> 'process-classes' phase). Use
> mvn package
> and you should be okay.
>
> 2. If you use standard maven directories, your generated classes should
> automatically be included in your jar files. If you are >having
> problems, try taking a look at some of our examples, here:
> http://jibx.svn.sourceforge.net/viewvc/jibx/trunk/plugins/maven-plugin/test-suite/
>
> 3. Yes, there was a bug in multi-module generation:
> http://jira.codehaus.org/browse/JIBX-431
> It has been fixed.
>
> This fixed code will be included in the 1.2.4 release. To use it now,
> just check it out of our svn repo and build it:
>
> svn co
> https://jibx.svn.sourceforge.net/svnroot/jibx/trunk/plugins/maven->plugin/jibx-maven-plugin
> cd jibx-maven-plugin
> mvn install
>
> Remember to change your plugin name to jibx-maven-plugin (from
> maven-jibx-plugin) and update the revision number to >1.2.4-SNAPSHOT.
> jibx-maven-plugin is the new plugin name.
>
> If you can't get this to work, email me back and I'll release a bugfix
> (1.2.3.1) version.
>
> Hope this helps!
>
> Don
[Attachment #5 (multipart/related)]
[Attachment #7 (text/html)]
<!DOCTYPE html><html><head>
<style type="text/css">"body { font-family:'Times New Roman'; \
font-size:13px"}</style> </head><body><div>
Hello Don,<br>
<br>
Thank you for your input!<br>
<br>
I guess (1) makes absolute sense.</div><div><br>
Regarding (2), you are correct that the generated classes are included
in the JAR archive. However, please see my later e-mail which explains
why this does not work in the multi-module config.The sequence of events
which explains why this happens is here: \
http://www.mail-archive.com/jibx-users@lists.sourceforge.net/msg04655.html<br> \
<br>For example: suppose I am building project "prjA" which contains "module1" and \
"module2". In "module2" the jibx-maven-plugin is configured to generate bindings, \
which also references classes from "module1".<br>
<br>
As it is now, the plug-in generates classes in "module1/target/...".
However, "module1" has already been packaged by then so those classes
won't make it into the module1.jar archive...<br>
<br>
Any ideas how to handle this?
</div><div><br></div><div>Kind \
regards,</div><div>Alexandros</div><div><br></div><div>On Fri, 13 May 2011 22:56:05 \
+0300, Don Corley <don@donandann.com> wrote:<br></div><br><blockquote \
style="margin: 0 0 0.80ex; border-left: #0000FF 2px solid; padding-left: 1ex"><div \
class="gmail_quote"><div>Alexandros,</div><div><br></div><div>Wow, that's a lot of \
questions. Let me see if I can help you.</div><div><br></div><div> 1. If you \
run:</div><div><font class="Apple-style-span" face="'courier new', monospace">mvn \
compile</font></div><div>The JiBX binding compiler will not run. This is the correct \
behavior. Remember JiBX adds byte codes AFTER your code is compiled (in the '<span \
class="Apple-style-span" style="font-family: Courier, monospace; font-size: 14px; \
">process-classes' </span>phase). Use</div> <div><font class="Apple-style-span" \
face="'courier new', monospace">mvn package</font></div><div>and you should be \
okay.</div><div><br></div><div>2. If you use standard maven directories, your \
generated classes should automatically be included in your jar files. If you are \
having problems, try taking a look at some of our examples, here:</div> <div><a \
href="http://jibx.svn.sourceforge.net/viewvc/jibx/trunk/plugins/maven-plugin/test-suit \
e/">http://jibx.svn.sourceforge.net/viewvc/jibx/trunk/plugins/maven-plugin/test-suite/</a></div>
<div><br></div><div>3. Yes, there was a bug in multi-module generation:</div><div><a \
href="http://jira.codehaus.org/browse/JIBX-431">http://jira.codehaus.org/browse/JIBX-431</a></div>
<div>It has been fixed.</div><div><br></div><div>This fixed code will be included in \
the 1.2.4 release. To use it now, just check it out of our svn repo and build \
it:</div><div><br></div><div><font class="Apple-style-span" face="'courier new', \
monospace">svn co <a \
href="https://jibx.svn.sourceforge.net/svnroot/jibx/trunk/plugins/maven-plugin/jibx-ma \
ven-plugin">https://jibx.svn.sourceforge.net/svnroot/jibx/trunk/plugins/maven-plugin/jibx-maven-plugin</a></font></div>
<div><font class="Apple-style-span" face="'courier new', \
monospace">cd jibx-maven-plugin</font></div><div><font class="Apple-style-span" \
face="'courier new', monospace">mvn install</font></div><div><br></div> <div>Remember \
to change your plugin name to jibx-maven-plugin (from maven-jibx-plugin) and \
update the revision number to 1.2.4-SNAPSHOT. jibx-maven-plugin is the new \
plugin name.</div><div><br></div><div>If you can't get this to work, email me back \
and I'll release a bugfix (1.2.3.1) version.</div> <div><br></div><div>Hope this \
helps!</div><div><br></div><div>Don</div></div> \
</blockquote><br><br><br></body></html>
------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
jibx-users mailing list
jibx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-users
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic