> another suggestion: if you are starting from a maven project with a
> parent project in the root dir, try creating a new project in eclipse,
> calling it (yourproject)-parent and linking all the needed resources
> (pom.xml, the /src dir, ...). In this way you will be able to use
> resources from
> -Original Message-
> From: Fabrizio Giustina [mailto:[EMAIL PROTECTED]
> Sent: dimanche 23 octobre 2005 22:43
> To: Maven Developers List
> Subject: Re: [Feedback] Limitations of using the m2 eclipse plugin
[snip]
> another suggestion: if you are starting from a ma
On 10/23/05, Vincent Massol <[EMAIL PROTECTED]> wrote:
> > normally I move the parent project to a subdirectory or, if the parent
> > project only contains a pom.xml file, I import it in another project
> > as a linked resource (calling it pom-parent.xml or something similar)
>
> Ok. I would hate t
> -Original Message-
> From: Fabrizio Giustina [mailto:[EMAIL PROTECTED]
> Sent: dimanche 23 octobre 2005 21:41
> To: Maven Developers List
> Subject: Re: [Feedback] Limitations of using the m2 eclipse plugin
>
> On 10/23/05, Vincent Massol <[EMAIL PROTECTED]&g
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: dimanche 23 octobre 2005 21:27
> To: Maven Developers List
> Subject: Re: [Feedback] Limitations of using the m2 eclipse plugin
>
> Vincent Massol wrote:
> > Hi,
> >
>
On 10/23/05, Vincent Massol <[EMAIL PROTECTED]> wrote:
> I have been a long fan of using a master eclipse project. I'm now trying to
> use the m1/m2-preferred strategy, which is to have one eclipse project per
> module. I'm doing this using "m2 eclipse:eclipse".
well, actually that's also the ecli
Vincent Massol wrote:
Hi,
1/ How do I edit files that in pom packaging projects (i.e. top level
directories)? This is for example where the common pom.xml files are
located.
It seems that using ../parent-project/pom.xml is working for some people.
FYI, Eclipse have decided that they want to a
Hi,
I have been a long fan of using a master eclipse project. I'm now trying to
use the m1/m2-preferred strategy, which is to have one eclipse project per
module. I'm doing this using "m2 eclipse:eclipse".
However, I've found the following limitations which still make this strategy
less good than
