You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Martin Desruisseaux (JIRA)" <ji...@codehaus.org> on 2007/04/06 18:07:01 UTC
[jira] Created: (MECLIPSE-251) Allows prefixing of eclipse project
name
Allows prefixing of eclipse project name
----------------------------------------
Key: MECLIPSE-251
URL: http://jira.codehaus.org/browse/MECLIPSE-251
Project: Maven 2.x Eclipse Plugin
Issue Type: New Feature
Components: multiproject
Affects Versions: 2.4
Reporter: Martin Desruisseaux
This issue is related to MECLIPSE-44, MECLIPSE-119 and MECLIPSE-161. They were closed as fixed by MECLIPSE-189, but the later doesn't adress fully our issue (or works only if we are lucky).
We have two Maven projects (namely _Geotools_ and _Geoserver_) made of many modules. Some Geoserver modules may (by accident) have the same name than Geotools modules. For example both Geotools and Geoserver have a module named "_main_". We need to import those two projects in Eclipse, because they are closely related and share the same pool of developpers. Before MECLIPSE-189, it was not possible with those names, because of module name clash like "_main_". Since MECLIPSE-189, it is possible if we are lucky enough to have different Geotools and Geoserver version numbers.
We would like a way to prefix every Eclipse module names. For example we would like a way to add {{"gt-"}} in front of every Geotools modules imported in Eclipse. I realize that the common practice in Maven projects seems to be long module names (for example "{{maven-eclipse-plugin}}"), but such practice seems quite redundant with group name. We would like to keep module names that match SVN directory names or Maven report directory names (otherwise we often get broken links in generated HTML pages), and we would like to keep the path names simple and intelligible (long module names don't bring much compared to full path names, which should already be unique).
The ability to add some prefix before Eclipse project names would help. If this is not possible, something like {{addGroupNameToProjectName}} property (similar to {{addVersionToProjectName}} defined in MECLIPSE-189) could be a fallback.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MECLIPSE-251) Allows prefixing of eclipse project
name
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carlos Sanchez closed MECLIPSE-251.
-----------------------------------
Resolution: Fixed
Fixed using [] for the variables
> Allows prefixing of eclipse project name
> ----------------------------------------
>
> Key: MECLIPSE-251
> URL: http://jira.codehaus.org/browse/MECLIPSE-251
> Project: Maven 2.x Eclipse Plugin
> Issue Type: New Feature
> Components: multiproject
> Affects Versions: 2.4
> Reporter: Martin Desruisseaux
> Assignee: Carlos Sanchez
> Fix For: 2.4
>
> Attachments: 20070509-maven-eclipse-plugin.patch
>
>
> This issue is related to MECLIPSE-44, MECLIPSE-119 and MECLIPSE-161. They were closed as fixed by MECLIPSE-189, but the later doesn't adress fully our issue (or works only if we are lucky).
> We have two Maven projects (namely _Geotools_ and _Geoserver_) made of many modules. Some Geoserver modules may (by accident) have the same name than Geotools modules. For example both Geotools and Geoserver have a module named "_main_". We need to import those two projects in Eclipse, because they are closely related and share the same pool of developpers. Before MECLIPSE-189, it was not possible with those names, because of module name clash like "_main_". Since MECLIPSE-189, it is possible if we are lucky enough to have different Geotools and Geoserver version numbers.
> We would like a way to prefix every Eclipse module names. For example we would like a way to add {{"gt-"}} in front of every Geotools modules imported in Eclipse. I realize that the common practice in Maven projects seems to be long module names (for example "{{maven-eclipse-plugin}}"), but such practice seems quite redundant with group name. We would like to keep module names that match SVN directory names or Maven report directory names (otherwise we often get broken links in generated HTML pages), and we would like to keep the path names simple and intelligible (long module names don't bring much compared to full path names, which should already be unique).
> The ability to add some prefix before Eclipse project names would help. If this is not possible, something like {{addGroupNameToProjectName}} property (similar to {{addVersionToProjectName}} defined in MECLIPSE-189) could be a fallback.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (MECLIPSE-251) Allows prefixing of eclipse project
name
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carlos Sanchez reopened MECLIPSE-251:
-------------------------------------
There are problem with the syntax used, it doesn't work in the reactor as the variables (${groupId}, ${artifactId}) are injected by maven
> Allows prefixing of eclipse project name
> ----------------------------------------
>
> Key: MECLIPSE-251
> URL: http://jira.codehaus.org/browse/MECLIPSE-251
> Project: Maven 2.x Eclipse Plugin
> Issue Type: New Feature
> Components: multiproject
> Affects Versions: 2.4
> Reporter: Martin Desruisseaux
> Assignee: Carlos Sanchez
> Fix For: 2.4
>
> Attachments: 20070509-maven-eclipse-plugin.patch
>
>
> This issue is related to MECLIPSE-44, MECLIPSE-119 and MECLIPSE-161. They were closed as fixed by MECLIPSE-189, but the later doesn't adress fully our issue (or works only if we are lucky).
> We have two Maven projects (namely _Geotools_ and _Geoserver_) made of many modules. Some Geoserver modules may (by accident) have the same name than Geotools modules. For example both Geotools and Geoserver have a module named "_main_". We need to import those two projects in Eclipse, because they are closely related and share the same pool of developpers. Before MECLIPSE-189, it was not possible with those names, because of module name clash like "_main_". Since MECLIPSE-189, it is possible if we are lucky enough to have different Geotools and Geoserver version numbers.
> We would like a way to prefix every Eclipse module names. For example we would like a way to add {{"gt-"}} in front of every Geotools modules imported in Eclipse. I realize that the common practice in Maven projects seems to be long module names (for example "{{maven-eclipse-plugin}}"), but such practice seems quite redundant with group name. We would like to keep module names that match SVN directory names or Maven report directory names (otherwise we often get broken links in generated HTML pages), and we would like to keep the path names simple and intelligible (long module names don't bring much compared to full path names, which should already be unique).
> The ability to add some prefix before Eclipse project names would help. If this is not possible, something like {{addGroupNameToProjectName}} property (similar to {{addVersionToProjectName}} defined in MECLIPSE-189) could be a fallback.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MECLIPSE-251) Allows prefixing of eclipse project
name
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carlos Sanchez closed MECLIPSE-251.
-----------------------------------
Assignee: Carlos Sanchez
Resolution: Fixed
Fix Version/s: 2.4
Fixed in other way, added addGroupIdToProjectName and projectNameTemplate parameters which you could use to prevent duplications
> Allows prefixing of eclipse project name
> ----------------------------------------
>
> Key: MECLIPSE-251
> URL: http://jira.codehaus.org/browse/MECLIPSE-251
> Project: Maven 2.x Eclipse Plugin
> Issue Type: New Feature
> Components: multiproject
> Affects Versions: 2.4
> Reporter: Martin Desruisseaux
> Assignee: Carlos Sanchez
> Fix For: 2.4
>
> Attachments: 20070509-maven-eclipse-plugin.patch
>
>
> This issue is related to MECLIPSE-44, MECLIPSE-119 and MECLIPSE-161. They were closed as fixed by MECLIPSE-189, but the later doesn't adress fully our issue (or works only if we are lucky).
> We have two Maven projects (namely _Geotools_ and _Geoserver_) made of many modules. Some Geoserver modules may (by accident) have the same name than Geotools modules. For example both Geotools and Geoserver have a module named "_main_". We need to import those two projects in Eclipse, because they are closely related and share the same pool of developpers. Before MECLIPSE-189, it was not possible with those names, because of module name clash like "_main_". Since MECLIPSE-189, it is possible if we are lucky enough to have different Geotools and Geoserver version numbers.
> We would like a way to prefix every Eclipse module names. For example we would like a way to add {{"gt-"}} in front of every Geotools modules imported in Eclipse. I realize that the common practice in Maven projects seems to be long module names (for example "{{maven-eclipse-plugin}}"), but such practice seems quite redundant with group name. We would like to keep module names that match SVN directory names or Maven report directory names (otherwise we often get broken links in generated HTML pages), and we would like to keep the path names simple and intelligible (long module names don't bring much compared to full path names, which should already be unique).
> The ability to add some prefix before Eclipse project names would help. If this is not possible, something like {{addGroupNameToProjectName}} property (similar to {{addVersionToProjectName}} defined in MECLIPSE-189) could be a fallback.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MECLIPSE-251) Allows prefixing of eclipse project
name
Posted by "Francois Fernandes (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francois Fernandes updated MECLIPSE-251:
----------------------------------------
Attachment: 20070509-maven-eclipse-plugin.patch
As I've had the same problem, here's a little patch which should do the work. I would appreciate any feedback and notes about it. This patch is based on the revision 520045 at https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-eclipse-plugin.
To prefix a project with a specific name just add -Declipse.projectNamePrefix=myprefix to the command line and it should work. Inside the configuration of the plugin just specifiy <projectNamePrefix>myprefix</projectNamePrefix>.
One thing I haven't done (shame on me) was to generate testcases (again, shame on me). The probleme was, that I have no idea of the correct way how to implement such a testcase using the existing plexus framework.
> Allows prefixing of eclipse project name
> ----------------------------------------
>
> Key: MECLIPSE-251
> URL: http://jira.codehaus.org/browse/MECLIPSE-251
> Project: Maven 2.x Eclipse Plugin
> Issue Type: New Feature
> Components: multiproject
> Affects Versions: 2.4
> Reporter: Martin Desruisseaux
> Attachments: 20070509-maven-eclipse-plugin.patch
>
>
> This issue is related to MECLIPSE-44, MECLIPSE-119 and MECLIPSE-161. They were closed as fixed by MECLIPSE-189, but the later doesn't adress fully our issue (or works only if we are lucky).
> We have two Maven projects (namely _Geotools_ and _Geoserver_) made of many modules. Some Geoserver modules may (by accident) have the same name than Geotools modules. For example both Geotools and Geoserver have a module named "_main_". We need to import those two projects in Eclipse, because they are closely related and share the same pool of developpers. Before MECLIPSE-189, it was not possible with those names, because of module name clash like "_main_". Since MECLIPSE-189, it is possible if we are lucky enough to have different Geotools and Geoserver version numbers.
> We would like a way to prefix every Eclipse module names. For example we would like a way to add {{"gt-"}} in front of every Geotools modules imported in Eclipse. I realize that the common practice in Maven projects seems to be long module names (for example "{{maven-eclipse-plugin}}"), but such practice seems quite redundant with group name. We would like to keep module names that match SVN directory names or Maven report directory names (otherwise we often get broken links in generated HTML pages), and we would like to keep the path names simple and intelligible (long module names don't bring much compared to full path names, which should already be unique).
> The ability to add some prefix before Eclipse project names would help. If this is not possible, something like {{addGroupNameToProjectName}} property (similar to {{addVersionToProjectName}} defined in MECLIPSE-189) could be a fallback.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira