Hi Stephan, It's a question of distributing your resources. If u do have a separate project for your xsds and xmlbeans output, then you are right and the stuff my plugin does is not necessary. In my approach I did have the xsd in the same project, where I use the generated classes. This did not work under eclipse, because eclipse did not find the generated stuff on the classpath and there was no (obvious) way, how to solve that. Therefore my approach.
For the project/repository dependency I would propose the same solution as Stephan did. Wilfred: No my plugin is not open source because I wrote it for my company, but I will grazely look away, when you copy the logic and put it in a different file in your project :-) -- Christian. > -----Ursprüngliche Nachricht----- > Von: Stephen Duncan [mailto:[EMAIL PROTECTED] > Gesendet: Freitag, 5. Mai 2006 12:07 > An: Maven Users List > Betreff: Re: XMLBeans Plugin + Eclipse Mayhem > > I don't think I understand why you did this. The normal > xmlbeans plugin will produce a jar with the > xmlbeans-generated code by default. > I think Wilfred's problem is just that the eclipse:eclipse > is giving him a project-dependcy for the sibling projects. > Since Eclispe isn't generating the xmlbeans sources, this > doesn't do anything for him. > > Wilfred, I think you just need to run mvn install on the > xmlbeans project, and then run eclipse:eclipse on only the > subproject so that it uses the dependency in your local > repository, instead of the Eclipse project. > > -Stephen --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
