The issue isn't the number of source directories, it's the location.
product-ejb has in the project.xml ../product/source/src
This isn't allowed in eclipse.
I could set it to an absolute path, but that's nasty as it assumes
everyone checks out in the same location.
On Tue, 26 Oct 2004 17:24:15
D]
> Subject: Re: maven with eclipse, mevenide et al
>
>
> >This all works fine for maven builds, but of course eclipse doesn't
> >like its source files to be anywhere other than a direct descendent of
> >the project directory.
>
> Hmm, that's news to me. I
>This all works fine for maven builds, but of course eclipse doesn't
>like its source files to be anywhere other than a direct descendent of
>the project directory.
Hmm, that's news to me. I have 6 independent source directories in one
project
in Eclipse.
Try going into the Properties for the pro
Yes, I'm thinking that the current structure probably needs to be
modularised in a more intelligent way. It's not that maven is unhappy,
it's more the eclipse problem of the sourcecode being 'elsewhere'.
we used to have 1 project controlled by ant that build a heap of
artefacts, such as client jar
Take a look at the updated (in CVS) docs. I added a bit about using the
generated source directory to import your xdcolet directory as a source
directory. That way, when eclipse does a clean compile, it doesn't wipe out
your source... I htink you are using xdoclet to generate a lot of the ejb
st
We are using the following layout:
projectRoot
|---applications
||---application.j2ee
| |---maven.xml
| |---project.xml [...]
|---containers
||---application.jboss (Self contained JBoss test environment)
| |---maven.xml
| |---project.xml [...]
|---modu
