[
https://jira.jboss.org/jira/browse/JBIDE-1406?page=com.atlassian.jira.plu...
]
Rob Stryker commented on JBIDE-1406:
------------------------------------
1) I will not provide an argument such as ${project_path:/projectA} because then it, once
again, ties the packages file to the project's NAME which may change based on how the
user imports the project. The goal by the JIRA reporter here is to have something similar
to old archives, where "./some/folder/path" was a path within the current
project, without being required to know the name of the project.
2) I do not think the difference between a dot and an underscore is an issue worth arguing
about. Sorry.
3) Providing only an eclipse extension does not allow for the library to be used from an
external ant script upon a packaging file and ties the library directly to eclipse and
makes it impossible to be used from ant. Instead, the current API allows the
${current.project} variable to be set before each build and cleared afterwards.
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