[
https://issues.jboss.org/browse/JBDS-2002?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBDS-2002:
----------------------------------
This could also be accomplished by switching from having a .target file to having a
feature.xml file for the whole site.
Does anyone actually consume the .target file by itself? Because if not, we'd be
better off switching to an overall feature + site.xml because then we'd gain:
a) ability to install whole TP via a single feature, including orphan plugins like jsch
b) one less artifact to maintain in SVN (and ultimately in Nexus)
c) ability to define a RANGE of requirements, rather than just a single version
could JBDS product include a range of feature versions?
-------------------------------------------------------
Key: JBDS-2002
URL:
https://issues.jboss.org/browse/JBDS-2002
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Build, installer, updatesite
Affects Versions: 5.0.0.Beta1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 5.0.0.CR1
Idea would be to allow the pieces under jbds.all to be updated w/o having to update the
top-level feature.
For example, instead of the feature including o.j.t.foo_3.3.0.vYYYYMMDDhhmm-Hxxx-Beta1,
it could instead include [3.3.0,3.4.0)
Might need p2.inf directions, eg:
http://www.eclipse.org/forums/index.php/t/210526/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira