You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Mark Hobson (JIRA)" <ji...@codehaus.org> on 2005/09/02 22:08:02 UTC
[jira] Created: (MNG-827) Allow eclipse plugin .project name to be customised
Allow eclipse plugin .project name to be customised
---------------------------------------------------
Key: MNG-827
URL: http://jira.codehaus.org/browse/MNG-827
Project: Maven 2
Type: Improvement
Components: maven-plugins
Versions: 2.0-beta-1
Reporter: Mark Hobson
Currently the EclipseWriter uses the POM artifactId as the eclipse project name in .project. This should be configurable for use-cases where different versions of the same project are used within the same eclipse workspace (since eclipse project names must be unique within workspaces).
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MNG-827) Allow eclipse plugin .project name to be customised
Posted by "Mark Hobson (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-827?page=comments#action_46217 ]
Mark Hobson commented on MNG-827:
---------------------------------
Nope this hasn't been resolved yet.
I was proposing an eclipse plugin config property to customise the project name within the eclipse workspace. This is to allow different versions of the same project to co-exist in eclipse (since project names must be unique in eclipse).
The problem is that a recent eclipse plugin patch dynamically links projects together within the workspace based on their dependencies and whether they also exist in the workspace. This is done by assuming that the project name is always equal to the artifactId - which would obviously break down if it were customisable as I proposed.
Although handy, I'm not entirely convinced that dynamic project linking is the correct approach. Especially as it can lead to differences between eclipse & maven compliation and currently does not support multiple versions of a project within the workspace (as detailed in the above comments).
Has anyone got any opinions on this?
> Allow eclipse plugin .project name to be customised
> ---------------------------------------------------
>
> Key: MNG-827
> URL: http://jira.codehaus.org/browse/MNG-827
> Project: Maven 2
> Type: Improvement
> Components: maven-eclipse-plugin
> Versions: 2.0-beta-1
> Reporter: Mark Hobson
>
>
> Currently the EclipseWriter uses the POM artifactId as the eclipse project name in .project. This should be configurable for use-cases where different versions of the same project are used within the same eclipse workspace (since eclipse project names must be unique within workspaces).
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MNG-827) Allow eclipse plugin .project name to be customised
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-827?page=all ]
Brett Porter updated MNG-827:
-----------------------------
Fix Version: 2.0-beta-4
> Allow eclipse plugin .project name to be customised
> ---------------------------------------------------
>
> Key: MNG-827
> URL: http://jira.codehaus.org/browse/MNG-827
> Project: Maven 2
> Type: Improvement
> Components: maven-eclipse-plugin
> Versions: 2.0-beta-1
> Reporter: Mark Hobson
> Fix For: 2.0-beta-4
>
>
> Currently the EclipseWriter uses the POM artifactId as the eclipse project name in .project. This should be configurable for use-cases where different versions of the same project are used within the same eclipse workspace (since eclipse project names must be unique within workspaces).
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MNG-827) Allow eclipse plugin .project name to be customised
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-827?page=all ]
Brett Porter updated MNG-827:
-----------------------------
Priority: Minor (was: Major)
Fix Version: (was: 2.0-beta-4)
not required for the first full release of the eclipse plugin IMO
> Allow eclipse plugin .project name to be customised
> ---------------------------------------------------
>
> Key: MNG-827
> URL: http://jira.codehaus.org/browse/MNG-827
> Project: Maven 2
> Type: Improvement
> Components: maven-eclipse-plugin
> Versions: 2.0-beta-1
> Reporter: Mark Hobson
> Priority: Minor
>
>
> Currently the EclipseWriter uses the POM artifactId as the eclipse project name in .project. This should be configurable for use-cases where different versions of the same project are used within the same eclipse workspace (since eclipse project names must be unique within workspaces).
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MNG-827) Allow eclipse plugin .project name to be customised
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-827?page=all ]
Brett Porter updated MNG-827:
-----------------------------
Component: (was: maven-plugins)
maven-eclipse-plugin
so this should be closed as fixed? any ideas when it was fixed?
> Allow eclipse plugin .project name to be customised
> ---------------------------------------------------
>
> Key: MNG-827
> URL: http://jira.codehaus.org/browse/MNG-827
> Project: Maven 2
> Type: Improvement
> Components: maven-eclipse-plugin
> Versions: 2.0-beta-1
> Reporter: Mark Hobson
>
>
> Currently the EclipseWriter uses the POM artifactId as the eclipse project name in .project. This should be configurable for use-cases where different versions of the same project are used within the same eclipse workspace (since eclipse project names must be unique within workspaces).
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MNG-827) Allow eclipse plugin .project name to be customised
Posted by "Mark Hobson (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-827?page=comments#action_45732 ]
Mark Hobson commented on MNG-827:
---------------------------------
Not too sure about that since we'd end up with rather verbose project names, e.g. myproject-1.5.3-SNAPSHOT. If any SNAPSHOT suffix was dropped then perhaps it could be managable.
Linking to projects within the workspace is a nice idea, although I'm not too sure about how maven's strict dependency versioning could still be maintained. For example, if a:1.0 depended on b:1.0 and b:1.1 was in the workspace would a be linked to b? If so then eclipse could happily compile a with b:1.1 during coding, but then maven might break at buildtime since it expects b:1.0.
A solution might be to use the full artifactId:version for the project name, but still things could get out of sync when SNAPSHOTs are involved - eclipse would be working with the latest source code whereas maven would be working with the last installed SNAPSHOTs. We then have the complexity of groupIds to add into the mix - how would we deal with like-named artifactIds that belong to different groupIds within the same workspace?
I personally like the non-linking behaviour of .classpath files since you know for sure that eclipse and maven are seeing eye-to-eye.
> Allow eclipse plugin .project name to be customised
> ---------------------------------------------------
>
> Key: MNG-827
> URL: http://jira.codehaus.org/browse/MNG-827
> Project: Maven 2
> Type: Improvement
> Components: maven-plugins
> Versions: 2.0-beta-1
> Reporter: Mark Hobson
>
>
> Currently the EclipseWriter uses the POM artifactId as the eclipse project name in .project. This should be configurable for use-cases where different versions of the same project are used within the same eclipse workspace (since eclipse project names must be unique within workspaces).
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MNG-827) Allow eclipse plugin .project name to be customised
Posted by "Trygve Laugstol (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-827?page=comments#action_45731 ]
Trygve Laugstol commented on MNG-827:
-------------------------------------
Would a flag "append version" suffice? The things is that I'm imagining the possibility for the Eclipse plugin to go look in the current workspace and find all existing projects that's in the workspace and try to find the ones it can make links to. I'm not sure but I think making the project name not deviate too much from the artifact id might be good for that reason.
> Allow eclipse plugin .project name to be customised
> ---------------------------------------------------
>
> Key: MNG-827
> URL: http://jira.codehaus.org/browse/MNG-827
> Project: Maven 2
> Type: Improvement
> Components: maven-plugins
> Versions: 2.0-beta-1
> Reporter: Mark Hobson
>
>
> Currently the EclipseWriter uses the POM artifactId as the eclipse project name in .project. This should be configurable for use-cases where different versions of the same project are used within the same eclipse workspace (since eclipse project names must be unique within workspaces).
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MNG-827) Allow eclipse plugin .project name to be customised
Posted by "Mark Hobson (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-827?page=comments#action_45734 ]
Mark Hobson commented on MNG-827:
---------------------------------
Ah, I hadn't realised this had been applied already.. wondered why my workspace was broken after a m2 eclipse:eclipse ;)
> Allow eclipse plugin .project name to be customised
> ---------------------------------------------------
>
> Key: MNG-827
> URL: http://jira.codehaus.org/browse/MNG-827
> Project: Maven 2
> Type: Improvement
> Components: maven-plugins
> Versions: 2.0-beta-1
> Reporter: Mark Hobson
>
>
> Currently the EclipseWriter uses the POM artifactId as the eclipse project name in .project. This should be configurable for use-cases where different versions of the same project are used within the same eclipse workspace (since eclipse project names must be unique within workspaces).
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MECLIPSE-44) Allow eclipse plugin .project name to
be customised
Posted by "fabrizio giustina (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-44?page=all ]
fabrizio giustina updated MECLIPSE-44:
--------------------------------------
Version: 2.0
> Allow eclipse plugin .project name to be customised
> ---------------------------------------------------
>
> Key: MECLIPSE-44
> URL: http://jira.codehaus.org/browse/MECLIPSE-44
> Project: Maven 2.x Eclipse Plugin
> Type: Bug
> Versions: 2.0
> Reporter: Mark Hobson
> Priority: Minor
>
>
> Currently the EclipseWriter uses the POM artifactId as the eclipse project name in .project. This should be configurable for use-cases where different versions of the same project are used within the same eclipse workspace (since eclipse project names must be unique within workspaces).
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org