huntc wrote:
- make sure you run "Maven / Update Project configuration" and after
that check target/generated-sources/xmlbeans folder is added to the
project source folders (you should see it in the Package Explorer)
I have now done that - the generated-sources were then added (Java Build
Path/source) (they weren't there previously) and the generated-classes got
added (Java Build Path/Libraries) (also weren't there previously).
However I then got a slew of errors for the project around the compilation
of the xmlbeans generated source... all sorts of weird stuff.
That is probably why generated classes are not available to other
projects..
To resolve those build errors you may need to add xmlbeans as a
dependency in your project pom.xml
- check that project that depends on project with generated sources
actually have project reference and not the jar in "Maven Dependencies"
classpaht container (verify that dependency version match project
version, you can enable Maven version decorator to make it easier, see
Window / Preferences / General / Appearance / Label Decorators / Maven
version decorator)
This seems anti-m2eclipse to me... it should all just work right?
Absolutely. And I already verified that it does work with the test
projects we have. If it doesn't work for you, please create jira issue
and provide complete test project that would allow us to reproduce it.
See some instructions at
http://docs.codehaus.org/display/M2ECLIPSE/Reporting+Issues
I shouldn't have to go around configuring dependencies manually should I?
Not sure what you mean. My instructions are just to help you to
diagnose the issue and identify what is going wrong.
Note that there is a known oddness (which is also considered bad Maven
practice) in xmlbeans plugin, which dynamically adds project
dependencies. Those dependencies can be visible when you run Maven, but
not when dependencies are resolved in the IDE. So, it is better to
explicitly declare such dependencies in your project, in your case - the
xmlbeans itself.
BTW: is this issue related:
http://jira.codehaus.org/browse/MNGECLIPSE-374
I don't think it is related. MNGECLIPSE-374 is about execution of
xmlbeans plugin and more specifically issue with xerces not available in
the plugin classpath, but in your case it is simply dependency
resolution. The latter is working with the test project I have.
Thanks
Eugene
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
