[
https://jira.jboss.org/jira/browse/JBIDE-1406?page=com.atlassian.jira.plu...
]
Rob Stryker commented on JBIDE-1406:
------------------------------------
During the course of this jira, paths for filesets and archives were refactored for
in-workspace paths. Specifically, in-workspace paths that were absolute (had a leading
slash) are unchanged entirely, but paths that do not have a leading slash now work
differently.
In previous versions, all paths that were marked as "in workspace" or
"workspace relative" ignored the leading slash and worked the same regardless.
For example, "projectA/output" was treated the same as
"/projectA/output".
In version 2.0 of the descriptor, however, this is no longer true. Paths that do not have
a leading slash will be treated as relative to the project it's declared in, or in the
future, where the specific descriptor file is located. As of now since all descriptor
files are at the root of the project, this is not an issue, but further changes will be
required to allow for multiple descriptors per file.
Since old archives do not have a version attached to their descriptor, old archives should
continue to work without any changes. New archives that are created in a new descriptor
file should be using version 1.2 of the descriptor file. A potential migration issue here
is if one member of a team upgrades to jboss tools 3.0, creates a new project archives,
and it defaults to descriptor version 2.0. Members of the team still on an older jboss
tools version will interpret this file incorrectly.
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