[ http://issues.apache.org/jira/browse/GERONIMO-1856?page=all ]
John Sisson updated GERONIMO-1856:
----------------------------------
Description:
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 directories.
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/project.properties file.
**NOTE** eclipse project name prefixes are only used when using the maven
eclipse plugin version 1.11 (at the time of writing yet to be released).
http://maven.apache.org/maven-1.x/plugins/eclipse/
was:
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 directories.
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/project.properties file.
> Provide more control over eclipse project name generation
> ---------------------------------------------------------
>
> Key: GERONIMO-1856
> URL: http://issues.apache.org/jira/browse/GERONIMO-1856
> Project: Geronimo
> Type: Improvement
> Security: public(Regular issues)
> Components: buildsystem
> Versions: 1.1
> Reporter: John Sisson
> Assignee: 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 directories.
> 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/project.properties file.
> **NOTE** eclipse project name prefixes are only used when using the maven
> eclipse plugin version 1.11 (at the time of writing yet to be released).
> http://maven.apache.org/maven-1.x/plugins/eclipse/
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
