[ http://jira.codehaus.org/browse/MOJO-374?page=comments#action_65184 ]
Anagnostopoulos Kostis commented on MOJO-374:
---------------------------------------------
Hi Anders,
{quote}
We have decide to assign the outputDirectory into part of the src tree.
The reasoning for this is Eclipse,s refreshes. It ends up beeing quite a noisy
problem having the Eclipse refreshing each time a maven build passes.
We also tried to put the outputDirectory into target/generated/something, but
again choose not to.
{quote}
Why not?
{quote}
I'm not saying we were absolutely right in this decision. I'm just having
problems with the IDE integrations having sources outside the main source area.
{quote}
I think its better to have all generated sources in under {{target}} folder
since
clean plugin work as is (i had also thought of modifying it, but then i just
used the {{target}} dir)
I also think you should make the JAXB sources a separate mvn project.
That way the result jar may be reused by other projects as is.
Have you tried [maven2 pluging for eclipse|http://m2eclipse.codehaus.org/] ?
I have tried for multi-module projects and:
* i managed to have as eclipse project the POM-type parent project !
(notice that eclipse:eclipse does not generate any files for POM-type projects)
* the parent project includes all source folders from all sub-modules.
Unfortunately, the current version 0.0.5 embeds an older version of maven2,
ending up embeding its bugs also :-(
Nevertheless, i have actually fixed this problem (embeded a newer version of
maven2 into the eclipse plugin) but the result file
is too big to include it here. Contact me "ankostis at gmail.com" to give you
my build of it.
Just wish that menger would do the same...
{quote}
In spite of the severe improved eclipse:eclipse pluging (as well goes
idea:idea) in M2, I have problems understanding how these plugins can know
where to find underlying plugin's <configuration><outputDirectory> and make a
100% plug and play IDE project.
{quote}
see this part of mojo's {{execute()}} method:
{noformat}
// Mark XJC_generated java files for compilation.
project.addCompileSourceRoot(outputDirectory);
{noformat}
{quote}
What happens here is that jaxb1 will generate source into directory
src/java/mycom/core/logging/config/jaxb
And here we have made a convension in our project that the "last" package (in
this case jaxb) should ONLY contain the generated code. And this directory we
will be cleaning.
{quote}
You certainly need a multi-nodule maven structure here. One for JAXB, one for
the rest code, having as dependency the JAXB
-----
Hope i helped, waiting for your results, have you checked
[Hyperjaxb2|http://hyperjaxb2.dev.java.net]?
ankostis
> JAXB1 maven plugin (using sun's lib)
> ------------------------------------
>
> Key: MOJO-374
> URL: http://jira.codehaus.org/browse/MOJO-374
> Project: Mojo
> Type: New Feature
> Components: Plugin Submission
> Reporter: Anagnostopoulos Kostis
> Priority: Minor
> Attachments: jaxb1-maven-plugin.tgz, pom.xml, pom.xml
>
>
> Dear housmates,
> this is the JAXB1 plugin for maven2 using sun's implementation libs for JAXB
> API.
> It's dependency libs are not uploaded to ibiblio yet but the poms exists that
> refer to sun for download
> due to licencing problems.
> That was before JAXB became an open-source project at
> https://jaxb.dev.java.net/.
> Now, all libs are CDDL or ASF licenced, so it is possible to upload them
> directly to ibiblio.
> The problem is under which groupId to upload them?
> I include the next matrix of all the JAXB1 libs as an aid to the discussion
> we had
> at the codehaus mailling lists concerning the placement of the dependency
> libs in ibiblio.org.
> I also hope that it would help anyone involved into uploading the actual libs
> to ibiblio,
> since i intend to spend my Easter vacations away from the PC.
> h4.JAXB1 Reference Implementation Libs
> ||jaxb lib || current or suggested groupId || included packages ||
> notes |
> |dom.jar | - | org.w3c | not a plugin dependency |
> |jaxb-api-doc.zip | javax.xml | javax.xml | not a plugin dependency |
> |jaxb-api-doc.zip | javax.xml | javax.xml | not a plugin dependency |
> |jaxb-api.jar | javax.xml | javax.xml | |
> |jaxb-api-src.zip | javax.xml | javax.xml | not a plugin dependency |
> |jaxb-impl.jar | javax.xml | com.sun.xml | |
> |jaxb-libs.jar | javax.xml | com.sun.msv, jp.gr.relax, org.iso_relax| |
> |jaxb-xjc.jar | javax.xml | com.sun.tools, com.sun.xml, org.apache | |
> |jaxp-api.jar | javax.xml | javax.xml | *runtime* dependency, among
> others usefull for JDK 1.4 clients using the XMLGregorianCalendar class
> (included in JDK1.5 by default) |
> |jax-qname.jar | javax.xml | javax.xml | *runtime* dependency
> (included in JDK1.5 by default) |
> |namespace.jar | javax.xml | javax.xml | *runtime* dependency
> (included in JDK1.5 by default) |
> |relaxngDatatype.jar | javax.xml | org.relaxng.datatype | *runtime*
> dependency |
> |sax.jar | - | org.xml.sax | not a plugin dependency |
> |xalan.jar | - | ... | not a plugin dependency |
> |xercesImpl.jar | - | ... | not a plugin dependency |
> |xsdlib.jar | javax.xml | com.sun.msv, com.sun.xml.util | *runtime*
> dependency |
> Of course the matrix would be more complete if it included the exact licence
> of each lib,
> but i think this is easy to figure out...
> ankostis
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
