Hi there, Since my last post, problems have continued to plague me with m2eclipse and xmlbeans plugin integration.
In summary everything works from mvn on the command line, but workspace dependencies continued to create issues when I had the xmlbeans project open. By "xmlbeans project" I mean the project that declares the xmlbeans plugin and generates source and classes under the target folder. If the project is closed, and thus the mvn repository is used, all is well. 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. Do these sound like sane steps? Cheers, -C -- View this message in context: http://www.nabble.com/xmlbeans-again-tp18566725p19282600.html Sent from the Maven Eclipse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
