Maven 2.x Eclipse Plugin

Allow custom project name for eclipse projects

Details

  • Type: New Feature New Feature
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Duplicate
  • Affects Version/s: 2.2
  • Fix Version/s: 2.4
  • Component/s: None
  • Labels:
    None
  • Testcase included:
    yes
  • Number of attachments :
    1

Description

If you download 2 versions of the same artifact, or 2 artifacts with the same artifactId then when you create eclipse the projects you have to load them into different workspaces because the eclipse project name is the same (ie. based on artifactId). I added a parameter eclipse.projectName to allow you to specify an alternate name to artifactId to get around this problem.

Example uses:
-Declipse.projectName='$

{project.artifactId}:${project.version}'
-Declipse.projectName='${project.groupId}:${project.artifactId}

:$

{project.version}

'
-Declipse.projectName=my-different-project-name

Issue Links

duplicates

New Feature - A new feature of the product, which has yet to be developed. MECLIPSE-189 addVersionToProjectName property

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Improvement - An improvement or enhancement to an existing feature or task. MECLIPSE-44 Allow eclipse plugin .project name to be customised

  • Minor - Minor loss of function, or other problem where easy workaround is present.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
is depended upon by

Bug - A problem which impairs or prevents the functions of the product. GEOT-995 Reinsert/remove "gt2-" prefix in all module name

  • Minor - Minor loss of function, or other problem where easy workaround is present.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
is duplicated by

Improvement - An improvement or enhancement to an existing feature or task. MECLIPSE-161 need flag to specify eclipse project name

  • Minor - Minor loss of function, or other problem where easy workaround is present.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
is related to

Improvement - An improvement or enhancement to an existing feature or task. MECLIPSE-40 Multi project dependencies should not require eclipse project names to be the artifactId

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Kenney Westerhof added a comment -

I prefer a switch like 'eclipse.addVersionToProjectNames'.

The -Declipse.projectname=LITERAL_STRING is dangerous and won't work in a reactor build.

Show
Kenney Westerhof added a comment - I prefer a switch like 'eclipse.addVersionToProjectNames'. The -Declipse.projectname=LITERAL_STRING is dangerous and won't work in a reactor build.
Hide
Permalink
Andrea Aime added a comment -

This inability to customize the project is byting us (Geotools/Geoserver projects) as well... we do have a "main" module in both projects, and at the same time maven works better if you have directory name=module name (see scm tags handling).... even having the ability to just write to the "project" property would be nice, it would allow for a customisation like:

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-eclipse-plugin</artifactId>
<configuration>
<project>gt2-$

{project}

</project>
</configuration>
</plugin>

Show
Andrea Aime added a comment - This inability to customize the project is byting us (Geotools/Geoserver projects) as well... we do have a "main" module in both projects, and at the same time maven works better if you have directory name=module name (see scm tags handling).... even having the ability to just write to the "project" property would be nice, it would allow for a customisation like: <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-eclipse-plugin</artifactId> <configuration> <project>gt2-$ {project} </project> </configuration> </plugin>
Hide
Permalink
Brian Fox added a comment -

I'm confused. All the ones linked to this as duplicates are closed and none of them have a fix version. Was this fixed?

Show
Brian Fox added a comment - I'm confused. All the ones linked to this as duplicates are closed and none of them have a fix version. Was this fixed?
Hide
Permalink
Brian Fox added a comment -

I can't find where this was fixed. All the duplicate issues are closed, but none of them have a fix version

Show
Brian Fox added a comment - I can't find where this was fixed. All the duplicate issues are closed, but none of them have a fix version
Hide
Permalink
Brian Fox added a comment -

ok I found the duplicate that resolves it.

Show
Brian Fox added a comment - ok I found the duplicate that resolves it.

People

  • Assignee:
    Carlos Sanchez
    Reporter:
    David Rice
Vote (6)
Watch (6)

Dates

  • Created:
    Updated:
    Resolved: