[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-1406) Package archive configuration is coupled to project name

[Rob Stryker (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBIDE-1406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12421528#action_12421528 ] 

Rob Stryker commented on JBIDE-1406:
------------------------------------

To be clear, the user wants to ensure that upon committing a project with a .packages file, the project name is not required at all, as the project name is a transient detail that may change.  The user also wants to be able to import the same source project (coppied to another folder of course) twice under two different names without having to hand-modify the packages file. 

> Package archive configuration is coupled to project name
> --------------------------------------------------------
>
>                 Key: JBIDE-1406
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-1406
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Archives
>    Affects Versions: 2.0.0.GA
>         Environment: Eclipse 3.3.1.1 on openSUSE 10.3
>            Reporter: Rob Hasselbaum
>            Assignee: Rob Stryker
>             Fix For: 3.0.0.alpha
>
>
> The ".packages" configuration file contains references to the project name. This is problematic if the configuration is checked into a revision control system, since it requires all checkouts of the project to use the same name in Eclipse. This means a developer cannot have more than one copy of the project in Eclipse at the same time (e.g. different branches), and in addition, all members of a team are forced to use the same project name.
> I have entered this as a bug rather than an enhancement request because this is a regression from JBoss IDE 1.6.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira