None of this is necessary. With the latest m2eclipse, xmlbeans are
detected, classpath is added and the goals of maven that - at least if
you use the default lifecycle) - generate the xmlbeans classes are
executed. Enable workspace auto-refresh, do "update project
configuration" and you should be fine.
Stefan
huntc wrote:
In addition to:
huntc wrote:
To cope, what I've now done under the xmlbeans project properties is:
1. Moved the maven builder up before the java builder (as per
recommendation). I presume that this ensures my generated classes are
created before java gets to compile.
2. Added target/generated-classes/xmlbeans as a class folder under Java
Build Path/Libraries. I presume that this then allows any dependent
sources in my project to resolve its imports.
3. Exported this same class folder under "Order and Export". This should
then allow other projects in the workspace to resolve the generated
classes when things are being resolved via the workspace.
4. Add xmlbeans as a compile-time dependency.
--
best regards,
Stefan Seidel
software developer
________________________
VUB Printmedia GmbH
Chopinstraße 4
D-04103 Leipzig
Germany
tel. +49 (341) 9 60 50 07
fax. +49 (341) 9 60 50 92
mail. [EMAIL PROTECTED]
web. www.vub.de
HRB Köln 24015
UStID DE 122 649 251
GF Dr. Achim Preuss Neudorf,
Dr. Christian Preuss Neudorf
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
