Re: Eclipse project names conflict

Wed, 20 Oct 2010 11:10:09 -0700 

On 20/10/10 17:49, Mark Struberg wrote:

As there is only one project involved I suggest we rename
one of the artifactIds so that our code works in widest
possible number of configurations

+1

I think we should avoid any special eclipse-plugin configuration or similar in 
our poms. Others use Netbeans or Idea and would not benefit from this tweak.
On the contrary. Maven provides these tools to help developers get on with their work. So we should use them all so that people can get going as quickly as possible whether they are using Eclipses, Netbeans or Idea (all of which I believe Maven supports). 

Rob


LieGrue,
strub

--- On Wed, 10/20/10, Robert Matthews<[email protected]>  wrote:


From: Robert Matthews<[email protected]>
Subject: Re: Eclipse project names conflict
To: [email protected]
Date: Wednesday, October 20, 2010, 1:55 PM
I already tried this after I emailed
you. Although it changes the name of the projects properly
it doesn't name the referenced projects properly - so it
doesn't build.

As there is only one project involved I suggest we rename
one of the artifactIds so that our code works in widest
possible number of configurations, ie I don't think we
should dictate that one uses one plug-in over another.

Rob


On 20/10/10 14:19, Dan Haywood wrote:

I have a better solution; when importing into

m2eclipse, specify the "name template" to include the
groupId:artifactId.

Here's how:
1. File>  Import
2. On the next dialog, Maven>  Existing Maven

Projects

3. On the next dialog
a) open up advanced, and for name template, select

"[groupId].[artifactId]"

b) specify root directory
c) refresh
d) import

If you prefer to use mvn eclipse:eclipse to generate

the .project/.classpath, then it is (see [1]):

mvn eclipse:eclipse

-Declipse.projectNameTemplate="[groupId].[artifactId]"


I'll add that configuration to the root POM.

Make sense?
Dan

[1] 
http://docs.codehaus.org/display/GEOT/2.5.8+Maven+Eclipse+Plugin+Goals#2.5.8MavenEclipsePluginGoals-CustomizingtheNameoftheGeneratedProjects


On 20/10/2010 14:13, Robert Matthews wrote:

Dan

Our naming policy has caused a problem in Eclipse

where multiple project with same name (eg progmodel) cannot
be accommodated by it.  We have three POMs with the
same artifcact ID, two of which are Java/jar modules (the
other is  POM and doesn't seem to affect things). The
eclipse plugin uses the artifact name for the Eclipse
project name and therefore ends up with two projects with
the same name.

Ideally we should change one of the module's

artifact ID.

Rob

Reply via email to