geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Sisson (JIRA)" <>
Subject [jira] Created: (GERONIMO-1856) Provide more control over eclipse project name generation
Date Sat, 15 Apr 2006 13:40:00 GMT
Provide more control over eclipse project name generation

         Key: GERONIMO-1856
     Project: Geronimo
        Type: Improvement
    Security: public (Regular issues) 
  Components: buildsystem  
    Versions: 1.1    
    Reporter: John Sisson
 Assigned to: John Sisson 
    Priority: Minor
     Fix For: 1.1

Currently if you use the maven m:eclipse command to generate eclipse projects for geronimo
the eclipse project name is the same as the maven artifactId for the project.

This has a number of issues:

* The configs/activemq project generates an eclipse project with the name "activemq" which
clashes with activemq itself if you have it in your eclipse workspace.
* You cannot import two different versions of geronimo into the one eclipse workspace
* The sorting of geronimo eclipse projects is not optimal.  It would be nice to be able to
group together all the modules projects and configs projects for example.

This change enables you to set the prefix to use on eclipse projects for geronimo.  Different
prefixes can be set for projects in the applications, assemblies, configs, modules and plugins

The default is to only set a prefix on the projects under the configs directory, since the
artifactId for these projects don't have a "generonimo-" prefix.

See the properties with the prefix "geronimo.maven.eclipse" in the etc/

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message