Eclipse project names not generated consistently
------------------------------------------------
Key: GERONIMO-2194
URL: http://issues.apache.org/jira/browse/GERONIMO-2194
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: buildsystem
Affects Versions: 1.1
Environment: Maven eclipse plugin version 1.11
Reporter: John Sisson
Assigned To: John Sisson
Priority: Trivial
Fix For: 1.1.1
h1. Problem
When running maven the maven eclipse plugin to generate eclipse projects for
Geronimo, e.g.
{{maven m:eclipse -Dmaven.eclipse.src.download=false}}
A number of configs and modules eclipse project names are not built using the
{{geronimo.maven.eclipse.xx}} properties in the
{{geronimo/etc/project.properties}} file.
(i) This problem only impacts developers working on Geronimo itself who use
eclipse with version 1.11 or later of the maven eclipse plugin.
h1. Symptom
When importing existing projects into eclipse you will see the following
projects do not have a prefix that you specified in the
{{geronimo/etc/project.properties}} file:
* axis
* axis-deployer
* client-deployer
* ge-activemq-rar
* shared-lib
* unavailable-client-deployer
* unavailable-ejb-deployer
* unavailable-webservices-deployer
h1. Cause
A number of new project.properties files have been added since GERONIMO-1856
was committed before the 1.1 release was shipped. These newly added
project.properties files did not set the {{maven.eclipse.project.name}}
property like other Geronimo projects.
h1. Solution
The newly added project.property files have been fixed so that they set the
{{maven.eclipse.project.name}} property like the other Geronimo modules/configs.
h1. Workaround
None.
--
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
