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 > > > VUB Stefan Seidel wrote: > > We use the XMLBeans plugin, too. The problem is, that the generated > > classes are put into target/classes and Eclipse doesn't look there. It > > only considers its own compiled classes. Also, in multi-module-projects, > > the generated class files are in some sub-"target/classes"-Folder, so > > Eclipse doesn't even know about that. > > > > Brian: You could just file an issue in JIRA. > > > > Stefan > > > > Am Sonntag, den 22.04.2007, 19:30 -0400 schrieb Brian Bonner: > > > >> Thanks, Eugene, but it didn't work. MaI suspect that the Maven > >> XMLBeans plugin is not using "sources" in a way that m2Eclipse is > >> finding them as a source folder. I can put together a simple project > >> to show what I mean. > >> > >> Brian > >> > >> On 4/22/07, Eugene Kuleshov <[EMAIL PROTECTED]> wrote: > >> > >>> It may just work if you run "update sources" action on project that > >>> has xmlbeans (just in case, backup .classpath file, so you can roll it > >>> back). If it won't work you can also try to manually add > >>> target/xmlbeans-source in buildpath properties. > >>> > >>> regards, > >>> Eugene > >>> > >>> > >>> bkbonner wrote: > >>> > >>>> I have a project where I use the XMLBeans plugin to generate the XMLBeans > >>>> classes necessary for a particular project. When I built this project > >>>> using > >>>> plain old maven and the maven-eclipse-plugin, the dependent projects > >>>> would > >>>> referencing the resulting JAR file from this project from my local > >>>> repository. > >>>> > >>>> I've been using the M2Eclipse plugin for a while and had to go back and > >>>> make > >>>> changes to the older application. It shows a reference to the locally > >>>> installed project, but it doesn't find anything to put on the classpath. > >>>> > >>>> The Maven XMLBeans plugin generates sources in the target/xmlbeans-source > >>>> directory, but the speak of. > >>>> > >>>> Eugene, do you have any suggestions as to how I should configure XMLBeans > >>>> Plugin to put stuff on the classpath of the project? Is this the right > >>>> way > >>>> to get M2Eclipse to recognize the code properly? i.e. how does M2Eclipse > >>>> look for referencing projects that are in the eclipse workspace. > >>>> > >>>> I hope this is somewhat clear. > >>>> > >>>> > >>> --------------------------------------------------------------------- > >>> To unsubscribe from this list please visit: > >>> > >>> http://xircles.codehaus.org/manage_email > >>> > >>> > >>> > >> --------------------------------------------------------------------- > >> To unsubscribe from this list please visit: > >> > >> http://xircles.codehaus.org/manage_email > >> > > > > > > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > -- Mit freundlichen Grüßen, Stefan Seidel Software-Entwickler ________________________ VUB Printmedia GmbH Chopinstraße 4, 04103 Leipzig 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
