I would have to look at what xmlbeans plugin does. From the doc at
http://mojo.codehaus.org/xmlbeans-maven-plugin/usage.html it generates
sources at target/generated-sources/xmlbeans folder, so that folder just
need to be added as a source folder in Eclipse buildpath.
Update Sources action is using mavenProject.getCompileSourceRoots() to
collect all source folders and if xmlbeans don't add its folder up there
it won't be added to Eclipse buildpath automatically. I am also not sure
if xmlbeans is doing anything fancy about generated classes or they can
be compiled by regular javac...
regards,
Eugene
VUB Stefan Seidel wrote:
Yes, this works and that's the way we're handling it here (separate
eclipse & maven output folders+adding some maven output folders to the
classpath). Unfortunately every time I use "Update source folders" the
manually added classpath entry is removed.
Anyway, it would not be useful to always add the XMLBeans output folder
to the class path entries, I suppose, so I don't have any ideas on how
to make the m2eclipse plugin work better with this maven plugin.
regards,
Stefan
Am Montag, den 23.04.2007, 08:20 -0400 schrieb Eugene Kuleshov:
Have you tried to add target/classes folder as classpath folder into
the buildpath? Not sure if it will work if that folder is the same as
folder used to compile other source classes, but if you can make
xmlbeans to compile its classes into a separate folder it should work in
Eclipse.
regards,
Eugene
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
