1:14 p.m.
Nick Boldt created JBDS-2002:
--------------------------------
Summary: 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.Beta1
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
2:30 p.m.
[
https://issues.jboss.org/browse/JBDS-2002?page=com.atlassian.jira.plugin....
]
Nick Boldt updated JBDS-2002:
-----------------------------
Fix Version/s: 5.0.0.CR1
(was: 5.0.0.Beta1)
Slip
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
2:45 a.m.
[
https://issues.jboss.org/browse/JBDS-2002?page=com.atlassian.jira.plugin....
]
Mickael Istria commented on JBDS-2002:
--------------------------------------
I've seen some .product files using qualifier wildcard:
<features>
<feature id="o.j.t.foo" version="1.3.0.qualifier"/>
<feature id="o.j.t.bar" version="1.3.0.qualifier"/>
</features>
It works with Tycho, and p2 in general I guess.
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
12:31 p.m.
[
https://issues.jboss.org/browse/JBDS-2002?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBDS-2002:
----------------------------------
We include multiple features too, but without the version attribute:
https://svn.jboss.org/repos/devstudio/trunk/product/features/com.jboss.jb...
I would think that unless we set a match="equivalent" or
match="compatible" attribute on the features, this will just resolve to the
single resolved .qualifier 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
10:25 a.m.
[
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
11:46 p.m.
[
https://issues.jboss.org/browse/JBDS-2002?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBDS-2002:
----------------------------------
http://dev.eclipse.org/mhonarc/lists/p2-dev/msg04701.html implies that the best way to
achieve this is by including a big feature which in turn provides include ranges. See also
JBIDE-10915
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
12:14 a.m.
[
https://issues.jboss.org/browse/JBDS-2002?page=com.atlassian.jira.plugin....
]
Nick Boldt updated JBDS-2002:
-----------------------------
Fix Version/s: 5.0.1.GA
6.0.0.M1
(was: 5.0.0.CR1)
Slip to 5.0.1 or 6.0.0.M1
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.1.GA, 6.0.0.M1
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
10:56 p.m.
[
https://issues.jboss.org/browse/JBDS-2002?page=com.atlassian.jira.plugin....
]
Nick Boldt updated JBDS-2002:
-----------------------------
Fix Version/s: (was: 5.0.1.GA)
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: 6.0.0.M1
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
7:15 p.m.
[
https://issues.jboss.org/browse/JBDS-2002?page=com.atlassian.jira.plugin....
]
Nick Boldt closed JBDS-2002.
----------------------------
Resolution: Rejected
Between the plan to do JBDS BYOE (with a top-level controlling feature) and the fact that
developers DO want to consume .target files instead of a feature to define content... this
won't happen.
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: 6.0.0.Alpha1
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
For more information on JIRA, see: http://www.atlassian.com/software/jira
4317
days inactive
4538
days old
jbosstools-issues@lists.jboss.org
8 comments
2 participants
participants (2)
-
Mickael Istria (JIRA) -
Nick Boldt (JIRA)