[
https://jira.jboss.org/jira/browse/JBIDE-1406?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen reopened JBIDE-1406:
----------------------------------------
and i'm reopening it because of the comments below:
1) The string substitution variables in eclipse are only tied to selection if you
don't specify an argument to them, e.g. ${project_path:/projectA/.archives} is rather
deterministic won't you say ?
2) Why use a different notion ($current.project vs. ${current_project} ?)
3) If you don't like that why not provide an extension to the common eclipse
substitution when it executes, e.g. ${archives_current_project} or something similar ?
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