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
