> -Original Message-
> From: amit kumar [mailto:[EMAIL PROTECTED]
> Sent: 29 January 2008 10:27
> To: Maven Users List
> Subject: Re: Maven with Eclipse
>
> I was not able to locale 0.12 version of m2eclipse plug at
> http://m2eclipse.codehaus.org/update-dev/plugins/
I was not able to locale 0.12 version of m2eclipse plug at
http://m2eclipse.codehaus.org/update-dev/plugins/
Ben I would definitely try the plug in you had mentioned because my
experience with m2eclipse plug in for eclipse is not so "cool" in
terms of reliability while working from Eclipse console
You could try
http://code.google.com/p/q4e/
Other maven plugin, not as well known as mevenide or M2Eclipse plugin,
but for me it works a lot better...
Tom
Ben Lidgey schrieb:
There is a newer version of the M2Eclipse plugin (0.0.12) which might make a difference.
Also, there are settings i
There is a newer version of the M2Eclipse plugin (0.0.12) which might make a
difference. Also, there are settings in Eclipse to control the highlighting
(see Windows-Preferences-Java-Editor and see if the "Report problems as you
type" box is checked).
Ben
> -Original Message-
> From:
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
10 matches
Mail list logo
