Well, then I'd suggest just manually removing the project dependency &
setting the repository dependency.
Alternatively, you can try to add "target/generate-sources" as a
source folder in the XSD project. It's not perfect, in that there
will be a lot of errors shown about not being able to resolve
something, but you can then refer to the XMLBeans classes elsewhere.
That's what I'm doing now, since I have some extra classes inside my
xmlbeans project.
-Stephen
On 5/5/06, Wilfred Springer <[EMAIL PROTECTED]> wrote:
Hi Stephen,
> 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.
The problem with that approach is that all of the other dependencies
will also be turned into dependencies to jar files in M2_REPO, which is
not what I want. (I have many more modules as siblings of
'project-client'.)
>
> -Stephen
>
> On 5/5/06, Domsch, Christian <[EMAIL PROTECTED]> wrote:
> > Hi Wilfred,
> >
> > Yes I had the same problem and I think I have a working solution. The key
is, that I wrote an additional plugin, that would generate a jar containing the
generated sources and classes from xmlbeans. My normal project now includes this
project.
> >
> > The process is like this:
> >
> > The normal XMLBeans Plugin generates ist sources and classes and puts them
to a defined location. My plugin picks up thoses resources at the same location and
builds the jar and installes it into the local repository. For this, my plugin runs
in the process-resources phase.
> >
> > Now the project insode eclipse can resolve anything it needs, with one
downside that you have to run the lifecycle one time outside eclipse for the initial
generation of this jar.
> >
> > Greetings,
> >
> > Christian Domsch.
> >
> > P.S.: I attached the pom and the source for this plugin.
> >
> > > -----Ursprüngliche Nachricht-----
> > > Von: Wilfred Springer [mailto:[EMAIL PROTECTED]
> > > Gesendet: Freitag, 5. Mai 2006 08:20
> > > An: [EMAIL PROTECTED]
> > > Cc: Maven Users List
> > > Betreff: XMLBeans Plugin + Eclipse Mayhem
> > >
> > > Hi all,
> > >
> > > I am using the XMLBeans Maven Plugin in a couple of projects,
> > > but using this plugin in combination with Eclipse is giving
> > > me a headache. I was just wondering if somebody has already solved it.
> > >
> > > The layout of my project is a little like this:
> > >
> > > project
> > > +--- pom.xml
> > > +--- project-xml-binding
> > > +--- pom.xml
> > > +--- src/main/xsd/test.xsd
> > > +----src/main/xsdconfig/xsdconfig.xml
> > > +--- project-client
> > > +--- pom.xml
> > > +--- src/main/java
> > >
> > >
> > > The 'project-client' module depends on project-xml-binding.
> > > The problem
> > > is that client code in 'project-client' does not always see
> > > the classes
> > > or source files generated from the XMLBeans plugin. So
> > > Eclipse is giving
> > > a lot of warnings for missing class file definitions, I don't
> > > have code
> > > completion, and my tests do not always run when running it
> > > from Eclipse.
> > >
> > > So the question is: how do I make sure that my client code has all of
> > > the class definitions of the 'project-xml-binding' project,
> > > and how do I
> > > configure my poms to make sure that eclipse:eclipse is giving me the
> > > proper project settings?
> > >
> > > Thanks,
> > >
> > > Wilfred
> > >
> > > Wilfred Springer | Software Architect | TomTom |
> > > [EMAIL PROTECTED] | +31 646 720 990
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >
>
>
> --
> Stephen Duncan Jr
> www.stephenduncanjr.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
Wilfred Springer | Software Architect | TomTom |
[EMAIL PROTECTED] | +31 646 720 990
--
Stephen Duncan Jr
www.stephenduncanjr.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
