Yes, Eclipse 3.3
On 2/17/08, Arnaud HERITIER [EMAIL PROTECTED] wrote:
Do you have eclipse 3.3 ??
On Feb 17, 2008 6:28 PM, deckrider [EMAIL PROTECTED] wrote:
On Feb 15, 2008 10:59 PM, Wendy Smoak [EMAIL PROTECTED] wrote:
On Feb 15, 2008 9:09 PM, deckrider [EMAIL PROTECTED] wrote:
On Feb 15, 2008 10:59 PM, Wendy Smoak [EMAIL PROTECTED] wrote:
On Feb 15, 2008 9:09 PM, deckrider [EMAIL PROTECTED] wrote:
1. Check out the project, but don't use Eclipse to check it out.
2. Run 'mvn elicpse:eclipse' from the parent.
3. Now start Eclipse and import the existing
Do you have eclipse 3.3 ??
On Feb 17, 2008 6:28 PM, deckrider [EMAIL PROTECTED] wrote:
On Feb 15, 2008 10:59 PM, Wendy Smoak [EMAIL PROTECTED] wrote:
On Feb 15, 2008 9:09 PM, deckrider [EMAIL PROTECTED] wrote:
1. Check out the project, but don't use Eclipse to check it out.
2. Run
Looks like your parent project is just of pom type. In this case there wont
be an eclipse project generated since there is not artifact to deliver.
There are 2 things you can do:
1. Fire a feture request in JIRA so that simple eclipe project type is
created from pom type porject.
2. Create a
Sorry for the silly question but I'm trying to understand the best way
to use Eclipse with Maven2 multi module projects.
Here is my understanding:
1. Check out the project, but don't use Eclipse to check it out.
2. Run 'mvn elicpse:eclipse' from the parent.
3. Now start Eclipse and import the
On Feb 15, 2008 9:09 PM, deckrider [EMAIL PROTECTED] wrote:
1. Check out the project, but don't use Eclipse to check it out.
2. Run 'mvn elicpse:eclipse' from the parent.
3. Now start Eclipse and import the existing project.
This results in all the children coming into Eclipse as separate