12:36 a.m.
Nick Boldt created JBDS-2402:
--------------------------------
Summary: ensure BYOE feature provides URL from which to update
Key: JBDS-2402
URL: https://issues.jboss.org/browse/JBDS-2402
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: updatesite
Affects Versions: 6.0.0.CR1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 6.0.0.CR1
We recently removed 'org.eclipse.equinox.p2.touchpoint.eclipse.addRepository'
touchpoints from *p2.inf files in JBDS, and the result is that until a user scans
Central's update site, there are no entries listed in the Available Software Sites
pref page.
So, we need to ensure that this is added back in.
Rather than putting it in the JBDS Branded Product feature, however, I would rather see it
put into the BYOE / Core Features feature, so that anyone who's installed from
Marketplace can also get updates from the site on devstudio.jboss.com. We can also use
this mechanism to replace the 6.0-staging site (currently in Marketplace) by the 6.0 site
(once we go GA) and clean the old site out of users' Eclipse installs so they only get
updates from the official site, not the staging one.
--
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
12:38 a.m.
[
https://issues.jboss.org/browse/JBDS-2402?page=com.atlassian.jira.plugin....
]
Nick Boldt updated JBDS-2402:
-----------------------------
Attachment: jbds2402-add-touchpoints.patch.txt
Patch:
[^jbds2402-add-touchpoints.patch.txt]
Note that when we're ready for GA, we'll want something more like this:
{code}
-org.eclipse.equinox.p2.touchpoint.eclipse.addRepository(type:0,location:https${#58}//devstudio.jboss.com/updates/6.0-staging/,name:JBoss
Developer Studio 6.0 Updates);\
-org.eclipse.equinox.p2.touchpoint.eclipse.addRepository(type:1,location:https${#58}//devstudio.jboss.com/updates/6.0-staging/,name:JBoss
Developer Studio 6.0 Updates);\
{code}
ensure BYOE feature provides URL from which to update
------------------------------------------------------
Key: JBDS-2402
URL: https://issues.jboss.org/browse/JBDS-2402
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: updatesite
Affects Versions: 6.0.0.CR1
Reporter: Nick Boldt
Assignee: Nick Boldt
Labels: respin-b
Fix For: 6.0.0.CR1
Attachments: jbds2402-add-touchpoints.patch.txt
We recently removed 'org.eclipse.equinox.p2.touchpoint.eclipse.addRepository'
touchpoints from *p2.inf files in JBDS, and the result is that until a user scans
Central's update site, there are no entries listed in the Available Software Sites
pref page.
So, we need to ensure that this is added back in.
Rather than putting it in the JBDS Branded Product feature, however, I would rather see
it put into the BYOE / Core Features feature, so that anyone who's installed from
Marketplace can also get updates from the site on devstudio.jboss.com. We can also use
this mechanism to replace the 6.0-staging site (currently in Marketplace) by the 6.0 site
(once we go GA) and clean the old site out of users' Eclipse installs so they only get
updates from the official site, not the staging one.
--
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
12:40 a.m.
[
https://issues.jboss.org/browse/JBDS-2402?page=com.atlassian.jira.plugin....
]
Nick Boldt edited comment on JBDS-2402 at 11/26/12 6:40 PM:
------------------------------------------------------------
Patch:
[^jbds2402-add-touchpoints.patch.txt]
Note that when we're ready for GA, we'll want something more like this:
{code}
instructions.configure=\
-org.eclipse.equinox.p2.touchpoint.eclipse.addRepository(type:0,location:https${#58}//devstudio.jboss.com/updates/6.0-staging/,name:JBoss
Developer Studio 6.0 Updates);\
-org.eclipse.equinox.p2.touchpoint.eclipse.addRepository(type:1,location:https${#58}//devstudio.jboss.com/updates/6.0-staging/,name:JBoss
Developer Studio 6.0 Updates);\
+org.eclipse.equinox.p2.touchpoint.eclipse.removeRepository(type:0,location:https${#58}//devstudio.jboss.com/updates/6.0-staging/,name:JBoss
Developer Studio 6.0 Updates);\
+org.eclipse.equinox.p2.touchpoint.eclipse.removeRepository(type:1,location:https${#58}//devstudio.jboss.com/updates/6.0-staging/,name:JBoss
Developer Studio 6.0 Updates);\
+org.eclipse.equinox.p2.touchpoint.eclipse.addRepository(type:0,location:https${#58}//devstudio.jboss.com/updates/6.0/,name:JBoss
Developer Studio 6.0 Updates);\
+org.eclipse.equinox.p2.touchpoint.eclipse.addRepository(type:1,location:https${#58}//devstudio.jboss.com/updates/6.0/,name:JBoss
Developer Studio 6.0 Updates);\
and
instructions.unconfigure=\
+org.eclipse.equinox.p2.touchpoint.eclipse.removeRepository(type:0,location:https${#58}//devstudio.jboss.com/updates/6.0/,name:JBoss
Developer Studio 6.0 Updates);\
+org.eclipse.equinox.p2.touchpoint.eclipse.removeRepository(type:1,location:https${#58}//devstudio.jboss.com/updates/6.0/,name:JBoss
Developer Studio 6.0 Updates);\
{code}
was (Author: nickboldt):
Patch:
[^jbds2402-add-touchpoints.patch.txt]
Note that when we're ready for GA, we'll want something more like this:
{code}
instructions.configure=\
-org.eclipse.equinox.p2.touchpoint.eclipse.addRepository(type:0,location:https${#58}//devstudio.jboss.com/updates/6.0-staging/,name:JBoss
Developer Studio 6.0 Updates);\
-org.eclipse.equinox.p2.touchpoint.eclipse.addRepository(type:1,location:https${#58}//devstudio.jboss.com/updates/6.0-staging/,name:JBoss
Developer Studio 6.0 Updates);\
+org.eclipse.equinox.p2.touchpoint.eclipse.removeRepository(type:0,location:https${#58}//devstudio.jboss.com/updates/6.0-staging/,name:JBoss
Developer Studio 6.0 Updates);\
+org.eclipse.equinox.p2.touchpoint.eclipse.removeRepository(type:1,location:https${#58}//devstudio.jboss.com/updates/6.0-staging/,name:JBoss
Developer Studio 6.0 Updates);\
+org.eclipse.equinox.p2.touchpoint.eclipse.addRepository(type:0,location:https${#58}//devstudio.jboss.com/updates/6.0/,name:JBoss
Developer Studio 6.0 Updates);\
+org.eclipse.equinox.p2.touchpoint.eclipse.addRepository(type:1,location:https${#58}//devstudio.jboss.com/updates/6.0/,name:JBoss
Developer Studio 6.0 Updates);\
and
instructions.unconfigure=\
-org.eclipse.equinox.p2.touchpoint.eclipse.removeRepository(type:0,location:https${#58}//devstudio.jboss.com/updates/6.0-staging/,name:JBoss
Developer Studio 6.0 Updates);\
-org.eclipse.equinox.p2.touchpoint.eclipse.removeRepository(type:1,location:https${#58}//devstudio.jboss.com/updates/6.0-staging/,name:JBoss
Developer Studio 6.0 Updates);\
+org.eclipse.equinox.p2.touchpoint.eclipse.removeRepository(type:0,location:https${#58}//devstudio.jboss.com/updates/6.0/,name:JBoss
Developer Studio 6.0 Updates);\
+org.eclipse.equinox.p2.touchpoint.eclipse.removeRepository(type:1,location:https${#58}//devstudio.jboss.com/updates/6.0/,name:JBoss
Developer Studio 6.0 Updates);\
{code}
ensure BYOE feature provides URL from which to update
------------------------------------------------------
Key: JBDS-2402
URL: https://issues.jboss.org/browse/JBDS-2402
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: updatesite
Affects Versions: 6.0.0.CR1
Reporter: Nick Boldt
Assignee: Nick Boldt
Labels: respin-b
Fix For: 6.0.0.CR1, 6.0.0.GA
Attachments: jbds2402-add-touchpoints.patch.txt
We recently removed 'org.eclipse.equinox.p2.touchpoint.eclipse.addRepository'
touchpoints from *p2.inf files in JBDS, and the result is that until a user scans
Central's update site, there are no entries listed in the Available Software Sites
pref page.
So, we need to ensure that this is added back in.
Rather than putting it in the JBDS Branded Product feature, however, I would rather see
it put into the BYOE / Core Features feature, so that anyone who's installed from
Marketplace can also get updates from the site on devstudio.jboss.com. We can also use
this mechanism to replace the 6.0-staging site (currently in Marketplace) by the 6.0 site
(once we go GA) and clean the old site out of users' Eclipse installs so they only get
updates from the official site, not the staging one.
--
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
12:40 a.m.
[
https://issues.jboss.org/browse/JBDS-2402?page=com.atlassian.jira.plugin....
]
Nick Boldt edited comment on JBDS-2402 at 11/26/12 6:38 PM:
------------------------------------------------------------
Patch:
[^jbds2402-add-touchpoints.patch.txt]
Note that when we're ready for GA, we'll want something more like this:
{code}
instructions.configure=\
-org.eclipse.equinox.p2.touchpoint.eclipse.addRepository(type:0,location:https${#58}//devstudio.jboss.com/updates/6.0-staging/,name:JBoss
Developer Studio 6.0 Updates);\
-org.eclipse.equinox.p2.touchpoint.eclipse.addRepository(type:1,location:https${#58}//devstudio.jboss.com/updates/6.0-staging/,name:JBoss
Developer Studio 6.0 Updates);\
+org.eclipse.equinox.p2.touchpoint.eclipse.removeRepository(type:0,location:https${#58}//devstudio.jboss.com/updates/6.0-staging/,name:JBoss
Developer Studio 6.0 Updates);\
+org.eclipse.equinox.p2.touchpoint.eclipse.removeRepository(type:1,location:https${#58}//devstudio.jboss.com/updates/6.0-staging/,name:JBoss
Developer Studio 6.0 Updates);\
+org.eclipse.equinox.p2.touchpoint.eclipse.addRepository(type:0,location:https${#58}//devstudio.jboss.com/updates/6.0/,name:JBoss
Developer Studio 6.0 Updates);\
+org.eclipse.equinox.p2.touchpoint.eclipse.addRepository(type:1,location:https${#58}//devstudio.jboss.com/updates/6.0/,name:JBoss
Developer Studio 6.0 Updates);\
and
instructions.unconfigure=\
-org.eclipse.equinox.p2.touchpoint.eclipse.removeRepository(type:0,location:https${#58}//devstudio.jboss.com/updates/6.0-staging/,name:JBoss
Developer Studio 6.0 Updates);\
-org.eclipse.equinox.p2.touchpoint.eclipse.removeRepository(type:1,location:https${#58}//devstudio.jboss.com/updates/6.0-staging/,name:JBoss
Developer Studio 6.0 Updates);\
+org.eclipse.equinox.p2.touchpoint.eclipse.removeRepository(type:0,location:https${#58}//devstudio.jboss.com/updates/6.0/,name:JBoss
Developer Studio 6.0 Updates);\
+org.eclipse.equinox.p2.touchpoint.eclipse.removeRepository(type:1,location:https${#58}//devstudio.jboss.com/updates/6.0/,name:JBoss
Developer Studio 6.0 Updates);\
{code}
was (Author: nickboldt):
Patch:
[^jbds2402-add-touchpoints.patch.txt]
Note that when we're ready for GA, we'll want something more like this:
{code}
-org.eclipse.equinox.p2.touchpoint.eclipse.addRepository(type:0,location:https${#58}//devstudio.jboss.com/updates/6.0-staging/,name:JBoss
Developer Studio 6.0 Updates);\
-org.eclipse.equinox.p2.touchpoint.eclipse.addRepository(type:1,location:https${#58}//devstudio.jboss.com/updates/6.0-staging/,name:JBoss
Developer Studio 6.0 Updates);\
{code}
ensure BYOE feature provides URL from which to update
------------------------------------------------------
Key: JBDS-2402
URL: https://issues.jboss.org/browse/JBDS-2402
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: updatesite
Affects Versions: 6.0.0.CR1
Reporter: Nick Boldt
Assignee: Nick Boldt
Labels: respin-b
Fix For: 6.0.0.CR1, 6.0.0.GA
Attachments: jbds2402-add-touchpoints.patch.txt
We recently removed 'org.eclipse.equinox.p2.touchpoint.eclipse.addRepository'
touchpoints from *p2.inf files in JBDS, and the result is that until a user scans
Central's update site, there are no entries listed in the Available Software Sites
pref page.
So, we need to ensure that this is added back in.
Rather than putting it in the JBDS Branded Product feature, however, I would rather see
it put into the BYOE / Core Features feature, so that anyone who's installed from
Marketplace can also get updates from the site on devstudio.jboss.com. We can also use
this mechanism to replace the 6.0-staging site (currently in Marketplace) by the 6.0 site
(once we go GA) and clean the old site out of users' Eclipse installs so they only get
updates from the official site, not the staging one.
--
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
12:40 a.m.
[
https://issues.jboss.org/browse/JBDS-2402?page=com.atlassian.jira.plugin....
]
Nick Boldt updated JBDS-2402:
-----------------------------
Fix Version/s: 6.0.0.GA
ensure BYOE feature provides URL from which to update
------------------------------------------------------
Key: JBDS-2402
URL: https://issues.jboss.org/browse/JBDS-2402
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: updatesite
Affects Versions: 6.0.0.CR1
Reporter: Nick Boldt
Assignee: Nick Boldt
Labels: respin-b
Fix For: 6.0.0.CR1, 6.0.0.GA
Attachments: jbds2402-add-touchpoints.patch.txt
We recently removed 'org.eclipse.equinox.p2.touchpoint.eclipse.addRepository'
touchpoints from *p2.inf files in JBDS, and the result is that until a user scans
Central's update site, there are no entries listed in the Available Software Sites
pref page.
So, we need to ensure that this is added back in.
Rather than putting it in the JBDS Branded Product feature, however, I would rather see
it put into the BYOE / Core Features feature, so that anyone who's installed from
Marketplace can also get updates from the site on devstudio.jboss.com. We can also use
this mechanism to replace the 6.0-staging site (currently in Marketplace) by the 6.0 site
(once we go GA) and clean the old site out of users' Eclipse installs so they only get
updates from the official site, not the staging one.
--
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
1:05 a.m.
[
https://issues.jboss.org/browse/JBDS-2402?page=com.atlassian.jira.plugin....
]
Max Rydahl Andersen commented on JBDS-2402:
-------------------------------------------
I dont grok why you want to add any mention of devstudio.jboss.com staging servers in
these p2-infs ?
These should just point to devstudio.jboss.com directly - staging is not necessary to put
in here.
ensure BYOE feature provides URL from which to update
------------------------------------------------------
Key: JBDS-2402
URL: https://issues.jboss.org/browse/JBDS-2402
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: updatesite
Affects Versions: 6.0.0.CR1
Reporter: Nick Boldt
Assignee: Nick Boldt
Labels: respin-b
Fix For: 6.0.0.CR1, 6.0.0.GA
Attachments: jbds2402-add-touchpoints.patch.txt
We recently removed 'org.eclipse.equinox.p2.touchpoint.eclipse.addRepository'
touchpoints from *p2.inf files in JBDS, and the result is that until a user scans
Central's update site, there are no entries listed in the Available Software Sites
pref page.
So, we need to ensure that this is added back in.
Rather than putting it in the JBDS Branded Product feature, however, I would rather see
it put into the BYOE / Core Features feature, so that anyone who's installed from
Marketplace can also get updates from the site on devstudio.jboss.com. We can also use
this mechanism to replace the 6.0-staging site (currently in Marketplace) by the 6.0 site
(once we go GA) and clean the old site out of users' Eclipse installs so they only get
updates from the official site, not the staging one.
--
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
9:22 a.m.
[
https://issues.jboss.org/browse/JBDS-2402?page=com.atlassian.jira.plugin....
]
Mickael Istria commented on JBDS-2402:
--------------------------------------
[~nickboldt]: I would rather see it put into the BYOE / Core Features
feature, so that anyone who's installed from Marketplace can also get updates from the
site on devstudio.jboss.com.
Big *+1*. IMO, the product feature should only contain product-related stuff (Id, splash
& co). All other JBDS stuff (URLs for Central, URL for updates...) should go to the
BYOE feature, since it's included in the product.
[~maxandersen]: I dont grok why you want to add any mention of
devstudio.jboss.com staging servers in these p2-infs ?
This patch removes usage of the staging site in GA. We've used the staging site in
Alpha releases since this was the only existing JBDS 6 repo at this time.
Maybe we could have set both site (staging and GA) in all versions, and just ensure we
delete the staging site when we publish the GA site. So in all case, user gets ability to
update from a staging to another staging, or from a staging to a GA.
ensure BYOE feature provides URL from which to update
------------------------------------------------------
Key: JBDS-2402
URL: https://issues.jboss.org/browse/JBDS-2402
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: updatesite
Affects Versions: 6.0.0.CR1
Reporter: Nick Boldt
Assignee: Nick Boldt
Labels: respin-b
Fix For: 6.0.0.CR1, 6.0.0.GA
Attachments: jbds2402-add-touchpoints.patch.txt
We recently removed 'org.eclipse.equinox.p2.touchpoint.eclipse.addRepository'
touchpoints from *p2.inf files in JBDS, and the result is that until a user scans
Central's update site, there are no entries listed in the Available Software Sites
pref page.
So, we need to ensure that this is added back in.
Rather than putting it in the JBDS Branded Product feature, however, I would rather see
it put into the BYOE / Core Features feature, so that anyone who's installed from
Marketplace can also get updates from the site on devstudio.jboss.com. We can also use
this mechanism to replace the 6.0-staging site (currently in Marketplace) by the 6.0 site
(once we go GA) and clean the old site out of users' Eclipse installs so they only get
updates from the official site, not the staging one.
--
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
12:47 p.m.
[
https://issues.jboss.org/browse/JBDS-2402?page=com.atlassian.jira.plugin....
]
Max Rydahl Andersen commented on JBDS-2402:
-------------------------------------------
The BYOE feature aren't installed via the installer afaik, the product feature is or
does it apply both ?
ensure BYOE feature provides URL from which to update
------------------------------------------------------
Key: JBDS-2402
URL: https://issues.jboss.org/browse/JBDS-2402
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: updatesite
Affects Versions: 6.0.0.CR1
Reporter: Nick Boldt
Assignee: Nick Boldt
Labels: respin-b
Fix For: 6.0.0.CR1, 6.0.0.GA
Attachments: jbds2402-add-touchpoints.patch.txt
We recently removed 'org.eclipse.equinox.p2.touchpoint.eclipse.addRepository'
touchpoints from *p2.inf files in JBDS, and the result is that until a user scans
Central's update site, there are no entries listed in the Available Software Sites
pref page.
So, we need to ensure that this is added back in.
Rather than putting it in the JBDS Branded Product feature, however, I would rather see
it put into the BYOE / Core Features feature, so that anyone who's installed from
Marketplace can also get updates from the site on devstudio.jboss.com. We can also use
this mechanism to replace the 6.0-staging site (currently in Marketplace) by the 6.0 site
(once we go GA) and clean the old site out of users' Eclipse installs so they only get
updates from the official site, not the staging one.
--
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
1:13 p.m.
[
https://issues.jboss.org/browse/JBDS-2402?page=com.atlassian.jira.plugin....
]
Mickael Istria commented on JBDS-2402:
--------------------------------------
Some clarification:
* The product definition is com.jboss.jbds.all. It contains mainly branding. It's not
the definition used for packaging.
* The "BYOE feature" is com.jboss.jbds.product.feature, and defines all JBDS/JBT
stuff we want to install in an Eclipse, and some sites to configure with p2.inf. It also
defines all 3rd-party feature we want to install as "imports".
* The "packaged" product is called com.jboss.jbds.all and simply includes the
com.jboss.jbds.product.feature. This one is used to create the binary of JBDS product.
So:
* Even if installing the BYOE feature, one has access to JBDS branding definition
(com.jboss.jbds.all), although it's not used/enabled in his Eclipse.
* BYOE and JBDS product share the same feature of JBDS, which allows factorization of some
customization.
In case I'm telling something wrong, I hope [~nickboldt] or [~dgolovin] will tell the
truth ASAP.
ensure BYOE feature provides URL from which to update
------------------------------------------------------
Key: JBDS-2402
URL: https://issues.jboss.org/browse/JBDS-2402
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: updatesite
Affects Versions: 6.0.0.CR1
Reporter: Nick Boldt
Assignee: Nick Boldt
Labels: respin-b
Fix For: 6.0.0.CR1, 6.0.0.GA
Attachments: jbds2402-add-touchpoints.patch.txt
We recently removed 'org.eclipse.equinox.p2.touchpoint.eclipse.addRepository'
touchpoints from *p2.inf files in JBDS, and the result is that until a user scans
Central's update site, there are no entries listed in the Available Software Sites
pref page.
So, we need to ensure that this is added back in.
Rather than putting it in the JBDS Branded Product feature, however, I would rather see
it put into the BYOE / Core Features feature, so that anyone who's installed from
Marketplace can also get updates from the site on devstudio.jboss.com. We can also use
this mechanism to replace the 6.0-staging site (currently in Marketplace) by the 6.0 site
(once we go GA) and clean the old site out of users' Eclipse installs so they only get
updates from the official site, not the staging one.
--
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
1:15 p.m.
[
https://issues.jboss.org/browse/JBDS-2402?page=com.atlassian.jira.plugin....
]
Mickael Istria edited comment on JBDS-2402 at 11/27/12 7:15 AM:
----------------------------------------------------------------
Some clarification:
* The product definition is com.jboss.jbds.product.product. It contains mainly branding.
It's not the definition used for packaging.
* The "BYOE feature" is com.jboss.jbds.product.feature, and defines all JBDS/JBT
stuff we want to install in an Eclipse, and some sites to configure with p2.inf. It also
defines all 3rd-party feature we want to install as "imports".
* The "packaged" product is called com.jboss.jbds.all and simply includes the
com.jboss.jbds.product.feature. This one is used to create the binary of JBDS product.
So:
* Even if installing the BYOE feature, one has access to JBDS branding definition
(com.jboss.jbds.product.product), although it's not used/enabled in his Eclipse.
* BYOE and JBDS product share the same feature of JBDS, which allows factorization of some
customization.
In case I'm telling something wrong, I hope [~nickboldt] or [~dgolovin] will tell the
truth ASAP.
was (Author: mickael_istria):
Some clarification:
* The product definition is com.jboss.jbds.all. It contains mainly branding. It's not
the definition used for packaging.
* The "BYOE feature" is com.jboss.jbds.product.feature, and defines all JBDS/JBT
stuff we want to install in an Eclipse, and some sites to configure with p2.inf. It also
defines all 3rd-party feature we want to install as "imports".
* The "packaged" product is called com.jboss.jbds.all and simply includes the
com.jboss.jbds.product.feature. This one is used to create the binary of JBDS product.
So:
* Even if installing the BYOE feature, one has access to JBDS branding definition
(com.jboss.jbds.all), although it's not used/enabled in his Eclipse.
* BYOE and JBDS product share the same feature of JBDS, which allows factorization of some
customization.
In case I'm telling something wrong, I hope [~nickboldt] or [~dgolovin] will tell the
truth ASAP.
ensure BYOE feature provides URL from which to update
------------------------------------------------------
Key: JBDS-2402
URL: https://issues.jboss.org/browse/JBDS-2402
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: updatesite
Affects Versions: 6.0.0.CR1
Reporter: Nick Boldt
Assignee: Nick Boldt
Labels: respin-b
Fix For: 6.0.0.CR1, 6.0.0.GA
Attachments: jbds2402-add-touchpoints.patch.txt
We recently removed 'org.eclipse.equinox.p2.touchpoint.eclipse.addRepository'
touchpoints from *p2.inf files in JBDS, and the result is that until a user scans
Central's update site, there are no entries listed in the Available Software Sites
pref page.
So, we need to ensure that this is added back in.
Rather than putting it in the JBDS Branded Product feature, however, I would rather see
it put into the BYOE / Core Features feature, so that anyone who's installed from
Marketplace can also get updates from the site on devstudio.jboss.com. We can also use
this mechanism to replace the 6.0-staging site (currently in Marketplace) by the 6.0 site
(once we go GA) and clean the old site out of users' Eclipse installs so they only get
updates from the official site, not the staging one.
--
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
4:58 p.m.
[
https://issues.jboss.org/browse/JBDS-2402?page=com.atlassian.jira.plugin....
]
Work on JBDS-2402 started by Nick Boldt.
ensure BYOE feature provides URL from which to update
------------------------------------------------------
Key: JBDS-2402
URL: https://issues.jboss.org/browse/JBDS-2402
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: updatesite
Affects Versions: 6.0.0.CR1
Reporter: Nick Boldt
Assignee: Nick Boldt
Labels: respin-b
Fix For: 6.0.0.CR1, 6.0.0.GA
Attachments: jbds2402-add-touchpoints.patch.txt
We recently removed 'org.eclipse.equinox.p2.touchpoint.eclipse.addRepository'
touchpoints from *p2.inf files in JBDS, and the result is that until a user scans
Central's update site, there are no entries listed in the Available Software Sites
pref page.
So, we need to ensure that this is added back in.
Rather than putting it in the JBDS Branded Product feature, however, I would rather see
it put into the BYOE / Core Features feature, so that anyone who's installed from
Marketplace can also get updates from the site on devstudio.jboss.com. We can also use
this mechanism to replace the 6.0-staging site (currently in Marketplace) by the 6.0 site
(once we go GA) and clean the old site out of users' Eclipse installs so they only get
updates from the official site, not the staging one.
--
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
5:02 p.m.
[
https://issues.jboss.org/browse/JBDS-2402?page=com.atlassian.jira.plugin....
]
Nick Boldt updated JBDS-2402:
-----------------------------
Attachment: JBDS2402-40x.patch.txt
JBDS2402-JBDS2371.patch.txt
Assumptions:
a) Max would prefer to not have the staging URL in the installed product today (CR1x)
b) GA version should DEFINITELY not reference the staging site, and should in fact REMOVE
it should you update from pre-GA to GA
c) we won't likely be dropping CR1x to Early Access since we're in fact doing a
CR1b this week instead
d) JBDS-2371 was rejected (but apparently my patch slipped in somehow *in trunk only*)
Therefore, new patches to approve:
Trunk: [^JBDS2402-JBDS2371.patch.txt]
60x branch: [^JBDS2402-40x.patch.txt]
You'll note that now, on installation, the /6.0/ URL is added and the /6.0-staging/
URL is removed. On uninstallation, both URLs are removed (just in case).
ensure BYOE feature provides URL from which to update
------------------------------------------------------
Key: JBDS-2402
URL: https://issues.jboss.org/browse/JBDS-2402
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: updatesite
Affects Versions: 6.0.0.CR1
Reporter: Nick Boldt
Assignee: Nick Boldt
Labels: respin-b
Fix For: 6.0.0.CR1, 6.0.0.GA
Attachments: JBDS2402-40x.patch.txt, jbds2402-add-touchpoints.patch.txt,
JBDS2402-JBDS2371.patch.txt
We recently removed 'org.eclipse.equinox.p2.touchpoint.eclipse.addRepository'
touchpoints from *p2.inf files in JBDS, and the result is that until a user scans
Central's update site, there are no entries listed in the Available Software Sites
pref page.
So, we need to ensure that this is added back in.
Rather than putting it in the JBDS Branded Product feature, however, I would rather see
it put into the BYOE / Core Features feature, so that anyone who's installed from
Marketplace can also get updates from the site on devstudio.jboss.com. We can also use
this mechanism to replace the 6.0-staging site (currently in Marketplace) by the 6.0 site
(once we go GA) and clean the old site out of users' Eclipse installs so they only get
updates from the official site, not the staging one.
--
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
5:06 p.m.
[
https://issues.jboss.org/browse/JBDS-2402?page=com.atlassian.jira.plugin....
]
Nick Boldt updated JBDS-2402:
-----------------------------
Attachment: (was: JBDS2402-40x.patch.txt)
ensure BYOE feature provides URL from which to update
------------------------------------------------------
Key: JBDS-2402
URL: https://issues.jboss.org/browse/JBDS-2402
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: updatesite
Affects Versions: 6.0.0.CR1
Reporter: Nick Boldt
Assignee: Nick Boldt
Labels: respin-b
Fix For: 6.0.0.CR1, 6.0.0.GA
Attachments: JBDS2402-40x.patch_v2.txt, JBDS2402-JBDS2371.patch_v2.txt
We recently removed 'org.eclipse.equinox.p2.touchpoint.eclipse.addRepository'
touchpoints from *p2.inf files in JBDS, and the result is that until a user scans
Central's update site, there are no entries listed in the Available Software Sites
pref page.
So, we need to ensure that this is added back in.
Rather than putting it in the JBDS Branded Product feature, however, I would rather see
it put into the BYOE / Core Features feature, so that anyone who's installed from
Marketplace can also get updates from the site on devstudio.jboss.com. We can also use
this mechanism to replace the 6.0-staging site (currently in Marketplace) by the 6.0 site
(once we go GA) and clean the old site out of users' Eclipse installs so they only get
updates from the official site, not the staging one.
--
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
5:06 p.m.
[
https://issues.jboss.org/browse/JBDS-2402?page=com.atlassian.jira.plugin....
]
Nick Boldt updated JBDS-2402:
-----------------------------
Attachment: (was: JBDS2402-JBDS2371.patch.txt)
ensure BYOE feature provides URL from which to update
------------------------------------------------------
Key: JBDS-2402
URL: https://issues.jboss.org/browse/JBDS-2402
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: updatesite
Affects Versions: 6.0.0.CR1
Reporter: Nick Boldt
Assignee: Nick Boldt
Labels: respin-b
Fix For: 6.0.0.CR1, 6.0.0.GA
Attachments: JBDS2402-40x.patch_v2.txt, JBDS2402-JBDS2371.patch_v2.txt
We recently removed 'org.eclipse.equinox.p2.touchpoint.eclipse.addRepository'
touchpoints from *p2.inf files in JBDS, and the result is that until a user scans
Central's update site, there are no entries listed in the Available Software Sites
pref page.
So, we need to ensure that this is added back in.
Rather than putting it in the JBDS Branded Product feature, however, I would rather see
it put into the BYOE / Core Features feature, so that anyone who's installed from
Marketplace can also get updates from the site on devstudio.jboss.com. We can also use
this mechanism to replace the 6.0-staging site (currently in Marketplace) by the 6.0 site
(once we go GA) and clean the old site out of users' Eclipse installs so they only get
updates from the official site, not the staging one.
--
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
5:06 p.m.
[
https://issues.jboss.org/browse/JBDS-2402?page=com.atlassian.jira.plugin....
]
Nick Boldt updated JBDS-2402:
-----------------------------
Attachment: (was: jbds2402-add-touchpoints.patch.txt)
ensure BYOE feature provides URL from which to update
------------------------------------------------------
Key: JBDS-2402
URL: https://issues.jboss.org/browse/JBDS-2402
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: updatesite
Affects Versions: 6.0.0.CR1
Reporter: Nick Boldt
Assignee: Nick Boldt
Labels: respin-b
Fix For: 6.0.0.CR1, 6.0.0.GA
Attachments: JBDS2402-40x.patch_v2.txt, JBDS2402-JBDS2371.patch_v2.txt
We recently removed 'org.eclipse.equinox.p2.touchpoint.eclipse.addRepository'
touchpoints from *p2.inf files in JBDS, and the result is that until a user scans
Central's update site, there are no entries listed in the Available Software Sites
pref page.
So, we need to ensure that this is added back in.
Rather than putting it in the JBDS Branded Product feature, however, I would rather see
it put into the BYOE / Core Features feature, so that anyone who's installed from
Marketplace can also get updates from the site on devstudio.jboss.com. We can also use
this mechanism to replace the 6.0-staging site (currently in Marketplace) by the 6.0 site
(once we go GA) and clean the old site out of users' Eclipse installs so they only get
updates from the official site, not the staging one.
--
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
5:06 p.m.
[
https://issues.jboss.org/browse/JBDS-2402?page=com.atlassian.jira.plugin....
]
Nick Boldt updated JBDS-2402:
-----------------------------
Attachment: JBDS2402-40x.patch_v2.txt
JBDS2402-JBDS2371.patch_v2.txt
Assumptions:
a) Max would prefer to not have the staging URL in the installed product today (CR1x)
b) GA version should DEFINITELY not reference the staging site, and should in fact REMOVE
it should you update from pre-GA to GA
c) we won't likely be dropping CR1x to Early Access since we're in fact doing a
CR1b this week instead
d) JBDS-2371 was rejected (but apparently my patch slipped in somehow *in trunk only*)
Therefore, new patches to approve:
Trunk: [^JBDS2402-JBDS2371.patch_v2.txt]
60x branch: [^JBDS2402-40x.patch_v2.txt]
You'll note that now, on installation, the /6.0/ URL is added and the /6.0-staging/
URL is removed. On uninstallation, both URLs are removed (just in case).
ensure BYOE feature provides URL from which to update
------------------------------------------------------
Key: JBDS-2402
URL: https://issues.jboss.org/browse/JBDS-2402
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: updatesite
Affects Versions: 6.0.0.CR1
Reporter: Nick Boldt
Assignee: Nick Boldt
Labels: respin-b
Fix For: 6.0.0.CR1, 6.0.0.GA
Attachments: JBDS2402-40x.patch_v2.txt, JBDS2402-JBDS2371.patch_v2.txt
We recently removed 'org.eclipse.equinox.p2.touchpoint.eclipse.addRepository'
touchpoints from *p2.inf files in JBDS, and the result is that until a user scans
Central's update site, there are no entries listed in the Available Software Sites
pref page.
So, we need to ensure that this is added back in.
Rather than putting it in the JBDS Branded Product feature, however, I would rather see
it put into the BYOE / Core Features feature, so that anyone who's installed from
Marketplace can also get updates from the site on devstudio.jboss.com. We can also use
this mechanism to replace the 6.0-staging site (currently in Marketplace) by the 6.0 site
(once we go GA) and clean the old site out of users' Eclipse installs so they only get
updates from the official site, not the staging one.
--
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
5:06 p.m.
[
https://issues.jboss.org/browse/JBDS-2402?page=com.atlassian.jira.plugin....
]
Nick Boldt edited comment on JBDS-2402 at 11/27/12 11:06 AM:
-------------------------------------------------------------
Patch:
-REMOVED jbds2402-add-touchpoints.patch.txt-
Note that when we're ready for GA, we'll want something more like this:
{code}
instructions.configure=\
-org.eclipse.equinox.p2.touchpoint.eclipse.addRepository(type:0,location:https${#58}//devstudio.jboss.com/updates/6.0-staging/,name:JBoss
Developer Studio 6.0 Updates);\
-org.eclipse.equinox.p2.touchpoint.eclipse.addRepository(type:1,location:https${#58}//devstudio.jboss.com/updates/6.0-staging/,name:JBoss
Developer Studio 6.0 Updates);\
+org.eclipse.equinox.p2.touchpoint.eclipse.removeRepository(type:0,location:https${#58}//devstudio.jboss.com/updates/6.0-staging/,name:JBoss
Developer Studio 6.0 Updates);\
+org.eclipse.equinox.p2.touchpoint.eclipse.removeRepository(type:1,location:https${#58}//devstudio.jboss.com/updates/6.0-staging/,name:JBoss
Developer Studio 6.0 Updates);\
+org.eclipse.equinox.p2.touchpoint.eclipse.addRepository(type:0,location:https${#58}//devstudio.jboss.com/updates/6.0/,name:JBoss
Developer Studio 6.0 Updates);\
+org.eclipse.equinox.p2.touchpoint.eclipse.addRepository(type:1,location:https${#58}//devstudio.jboss.com/updates/6.0/,name:JBoss
Developer Studio 6.0 Updates);\
and
instructions.unconfigure=\
+org.eclipse.equinox.p2.touchpoint.eclipse.removeRepository(type:0,location:https${#58}//devstudio.jboss.com/updates/6.0/,name:JBoss
Developer Studio 6.0 Updates);\
+org.eclipse.equinox.p2.touchpoint.eclipse.removeRepository(type:1,location:https${#58}//devstudio.jboss.com/updates/6.0/,name:JBoss
Developer Studio 6.0 Updates);\
{code}
was (Author: nickboldt):
Patch:
[^jbds2402-add-touchpoints.patch.txt]
Note that when we're ready for GA, we'll want something more like this:
{code}
instructions.configure=\
-org.eclipse.equinox.p2.touchpoint.eclipse.addRepository(type:0,location:https${#58}//devstudio.jboss.com/updates/6.0-staging/,name:JBoss
Developer Studio 6.0 Updates);\
-org.eclipse.equinox.p2.touchpoint.eclipse.addRepository(type:1,location:https${#58}//devstudio.jboss.com/updates/6.0-staging/,name:JBoss
Developer Studio 6.0 Updates);\
+org.eclipse.equinox.p2.touchpoint.eclipse.removeRepository(type:0,location:https${#58}//devstudio.jboss.com/updates/6.0-staging/,name:JBoss
Developer Studio 6.0 Updates);\
+org.eclipse.equinox.p2.touchpoint.eclipse.removeRepository(type:1,location:https${#58}//devstudio.jboss.com/updates/6.0-staging/,name:JBoss
Developer Studio 6.0 Updates);\
+org.eclipse.equinox.p2.touchpoint.eclipse.addRepository(type:0,location:https${#58}//devstudio.jboss.com/updates/6.0/,name:JBoss
Developer Studio 6.0 Updates);\
+org.eclipse.equinox.p2.touchpoint.eclipse.addRepository(type:1,location:https${#58}//devstudio.jboss.com/updates/6.0/,name:JBoss
Developer Studio 6.0 Updates);\
and
instructions.unconfigure=\
+org.eclipse.equinox.p2.touchpoint.eclipse.removeRepository(type:0,location:https${#58}//devstudio.jboss.com/updates/6.0/,name:JBoss
Developer Studio 6.0 Updates);\
+org.eclipse.equinox.p2.touchpoint.eclipse.removeRepository(type:1,location:https${#58}//devstudio.jboss.com/updates/6.0/,name:JBoss
Developer Studio 6.0 Updates);\
{code}
ensure BYOE feature provides URL from which to update
------------------------------------------------------
Key: JBDS-2402
URL: https://issues.jboss.org/browse/JBDS-2402
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: updatesite
Affects Versions: 6.0.0.CR1
Reporter: Nick Boldt
Assignee: Nick Boldt
Labels: respin-b
Fix For: 6.0.0.CR1, 6.0.0.GA
Attachments: JBDS2402-40x.patch_v2.txt, JBDS2402-JBDS2371.patch_v2.txt
We recently removed 'org.eclipse.equinox.p2.touchpoint.eclipse.addRepository'
touchpoints from *p2.inf files in JBDS, and the result is that until a user scans
Central's update site, there are no entries listed in the Available Software Sites
pref page.
So, we need to ensure that this is added back in.
Rather than putting it in the JBDS Branded Product feature, however, I would rather see
it put into the BYOE / Core Features feature, so that anyone who's installed from
Marketplace can also get updates from the site on devstudio.jboss.com. We can also use
this mechanism to replace the 6.0-staging site (currently in Marketplace) by the 6.0 site
(once we go GA) and clean the old site out of users' Eclipse installs so they only get
updates from the official site, not the staging one.
--
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
5:08 p.m.
[
https://issues.jboss.org/browse/JBDS-2402?page=com.atlassian.jira.plugin....
]
Nick Boldt updated JBDS-2402:
-----------------------------
Comment: was deleted
(was: Assumptions:
a) Max would prefer to not have the staging URL in the installed product today (CR1x)
b) GA version should DEFINITELY not reference the staging site, and should in fact REMOVE
it should you update from pre-GA to GA
c) we won't likely be dropping CR1x to Early Access since we're in fact doing a
CR1b this week instead
d) JBDS-2371 was rejected (but apparently my patch slipped in somehow *in trunk only*)
Therefore, new patches to approve:
Trunk: [^JBDS2402-JBDS2371.patch.txt]
60x branch: [^JBDS2402-40x.patch.txt]
You'll note that now, on installation, the /6.0/ URL is added and the /6.0-staging/
URL is removed. On uninstallation, both URLs are removed (just in case).
)
ensure BYOE feature provides URL from which to update
------------------------------------------------------
Key: JBDS-2402
URL: https://issues.jboss.org/browse/JBDS-2402
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: updatesite
Affects Versions: 6.0.0.CR1
Reporter: Nick Boldt
Assignee: Nick Boldt
Labels: respin-b
Fix For: 6.0.0.CR1, 6.0.0.GA
Attachments: JBDS2402-40x.patch_v2.txt, JBDS2402-JBDS2371.patch_v2.txt
We recently removed 'org.eclipse.equinox.p2.touchpoint.eclipse.addRepository'
touchpoints from *p2.inf files in JBDS, and the result is that until a user scans
Central's update site, there are no entries listed in the Available Software Sites
pref page.
So, we need to ensure that this is added back in.
Rather than putting it in the JBDS Branded Product feature, however, I would rather see
it put into the BYOE / Core Features feature, so that anyone who's installed from
Marketplace can also get updates from the site on devstudio.jboss.com. We can also use
this mechanism to replace the 6.0-staging site (currently in Marketplace) by the 6.0 site
(once we go GA) and clean the old site out of users' Eclipse installs so they only get
updates from the official site, not the staging one.
--
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
5:10 p.m.
[
https://issues.jboss.org/browse/JBDS-2402?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBDS-2402:
----------------------------------
Building now locally from 60x branch. When done, I need to:
* install from installer; verify URL is shown in JBDS and that I can search for updates
(even if none found)
* install BYOE feature into Eclipse JEE SR1 from locally built site; verify URL is shown
and that I can search for updates (even if none shown)
* uninstall BYOE feature from Eclipse JEE SR1; verify on restart that URL is gone
ensure BYOE feature provides URL from which to update
------------------------------------------------------
Key: JBDS-2402
URL: https://issues.jboss.org/browse/JBDS-2402
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: updatesite
Affects Versions: 6.0.0.CR1
Reporter: Nick Boldt
Assignee: Nick Boldt
Labels: respin-b
Fix For: 6.0.0.CR1, 6.0.0.GA
Attachments: JBDS2402-40x.patch_v2.txt, JBDS2402-JBDS2371.patch_v2.txt
We recently removed 'org.eclipse.equinox.p2.touchpoint.eclipse.addRepository'
touchpoints from *p2.inf files in JBDS, and the result is that until a user scans
Central's update site, there are no entries listed in the Available Software Sites
pref page.
So, we need to ensure that this is added back in.
Rather than putting it in the JBDS Branded Product feature, however, I would rather see
it put into the BYOE / Core Features feature, so that anyone who's installed from
Marketplace can also get updates from the site on devstudio.jboss.com. We can also use
this mechanism to replace the 6.0-staging site (currently in Marketplace) by the 6.0 site
(once we go GA) and clean the old site out of users' Eclipse installs so they only get
updates from the official site, not the staging one.
--
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
5:56 p.m.
[
https://issues.jboss.org/browse/JBDS-2402?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBDS-2402:
----------------------------------
Local build results:
* install from installer; verify URL is shown in JBDS *{color:green}OK{color}*
* install BYOE feature into Eclipse JEE SR1 from locally built site; verify URL is shown
*{color:green}OK{color}*
* uninstall BYOE feature from Eclipse JEE SR1; verify on restart that URL is gone
... *{color:red}NAMED entry removed, but not the URL itself - persists as an unnamed
entry{color}*
{code}org.eclipse.equinox.p2.touchpoint.eclipse.removeRepository(type:1,location:https${#58}//devstudio.jboss.com/updates/6.0/,name:JBoss
Developer Studio 6.0 Updates);{code}
So... either I need to list all the various ways we might see this URL come up (named,
unnamed)...
{code}org.eclipse.equinox.p2.touchpoint.eclipse.removeRepository(type:1,location:https${#58}//devstudio.jboss.com/updates/6.0/,name:JBoss
Developer Studio 6.0 Updates);
org.eclipse.equinox.p2.touchpoint.eclipse.removeRepository(type:1,locatio...;
{code}
... or just not bother to remove them on uninstallation.
ensure BYOE feature provides URL from which to update
------------------------------------------------------
Key: JBDS-2402
URL: https://issues.jboss.org/browse/JBDS-2402
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: updatesite
Affects Versions: 6.0.0.CR1
Reporter: Nick Boldt
Assignee: Nick Boldt
Labels: respin-b
Fix For: 6.0.0.CR1, 6.0.0.GA
Attachments: JBDS2402-40x.patch_v2.txt, JBDS2402-JBDS2371.patch_v2.txt
We recently removed 'org.eclipse.equinox.p2.touchpoint.eclipse.addRepository'
touchpoints from *p2.inf files in JBDS, and the result is that until a user scans
Central's update site, there are no entries listed in the Available Software Sites
pref page.
So, we need to ensure that this is added back in.
Rather than putting it in the JBDS Branded Product feature, however, I would rather see
it put into the BYOE / Core Features feature, so that anyone who's installed from
Marketplace can also get updates from the site on devstudio.jboss.com. We can also use
this mechanism to replace the 6.0-staging site (currently in Marketplace) by the 6.0 site
(once we go GA) and clean the old site out of users' Eclipse installs so they only get
updates from the official site, not the staging one.
--
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
7:35 p.m.
[
https://issues.jboss.org/browse/JBDS-2402?page=com.atlassian.jira.plugin....
]
Nick Boldt updated JBDS-2402:
-----------------------------
Attachment: JBDS2402-JBDS2371.patch_v3.txt
JBDS2402-40x.patch_v3.txt
Updated patches to remove everything added under the covers during JBDS BYOE installation
so the resulting uninstalled Eclipse looks the same as before.
* [^JBDS2402-JBDS2371.patch_v3.txt]
* [^JBDS2402-40x.patch_v3.txt]
ensure BYOE feature provides URL from which to update
------------------------------------------------------
Key: JBDS-2402
URL: https://issues.jboss.org/browse/JBDS-2402
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: updatesite
Affects Versions: 6.0.0.CR1
Reporter: Nick Boldt
Assignee: Nick Boldt
Labels: respin-b
Fix For: 6.0.0.CR1, 6.0.0.GA
Attachments: JBDS2402-40x.patch_v2.txt, JBDS2402-40x.patch_v3.txt,
JBDS2402-JBDS2371.patch_v2.txt, JBDS2402-JBDS2371.patch_v3.txt
We recently removed 'org.eclipse.equinox.p2.touchpoint.eclipse.addRepository'
touchpoints from *p2.inf files in JBDS, and the result is that until a user scans
Central's update site, there are no entries listed in the Available Software Sites
pref page.
So, we need to ensure that this is added back in.
Rather than putting it in the JBDS Branded Product feature, however, I would rather see
it put into the BYOE / Core Features feature, so that anyone who's installed from
Marketplace can also get updates from the site on devstudio.jboss.com. We can also use
this mechanism to replace the 6.0-staging site (currently in Marketplace) by the 6.0 site
(once we go GA) and clean the old site out of users' Eclipse installs so they only get
updates from the official site, not the staging one.
--
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
7:40 p.m.
New subject: [JBoss JIRA] (JBDS-2402) ensure BYOE feature provides URL from which to update, and cleans up URLs when uninstalled
[
https://issues.jboss.org/browse/JBDS-2402?page=com.atlassian.jira.plugin....
]
Nick Boldt updated JBDS-2402:
-----------------------------
Summary: ensure BYOE feature provides URL from which to update, and cleans up URLs
when uninstalled (was: ensure BYOE feature provides URL from which to update )
ensure BYOE feature provides URL from which to update, and cleans up
URLs when uninstalled
-------------------------------------------------------------------------------------------
Key: JBDS-2402
URL: https://issues.jboss.org/browse/JBDS-2402
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: updatesite
Affects Versions: 6.0.0.CR1
Reporter: Nick Boldt
Assignee: Nick Boldt
Labels: respin-b
Fix For: 6.0.0.CR1, 6.0.0.GA
Attachments: JBDS2402-40x.patch_v2.txt, JBDS2402-40x.patch_v3.txt,
JBDS2402-JBDS2371.patch_v2.txt, JBDS2402-JBDS2371.patch_v3.txt
We recently removed 'org.eclipse.equinox.p2.touchpoint.eclipse.addRepository'
touchpoints from *p2.inf files in JBDS, and the result is that until a user scans
Central's update site, there are no entries listed in the Available Software Sites
pref page.
So, we need to ensure that this is added back in.
Rather than putting it in the JBDS Branded Product feature, however, I would rather see
it put into the BYOE / Core Features feature, so that anyone who's installed from
Marketplace can also get updates from the site on devstudio.jboss.com. We can also use
this mechanism to replace the 6.0-staging site (currently in Marketplace) by the 6.0 site
(once we go GA) and clean the old site out of users' Eclipse installs so they only get
updates from the official site, not the staging one.
--
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
7:42 p.m.
New subject: [JBoss JIRA] (JBDS-2402) ensure BYOE feature provides URL from which to update, and cleans up URLs when uninstalled
[
https://issues.jboss.org/browse/JBDS-2402?page=com.atlassian.jira.plugin....
]
Nick Boldt edited comment on JBDS-2402 at 11/27/12 1:41 PM:
------------------------------------------------------------
Updated patches to remove everything added under the covers during JBDS BYOE installation
so the resulting uninstalled Eclipse looks the same as before.
* [^JBDS2402-JBDS2371.patch_v3.txt]
* [^JBDS2402-40x.patch_v3.txt]
These have been applied due to the fact that local tests passed. Spinning here so they can
be further QE'd:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio-6.0_stable...
>=140 --> install from
http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-6.0_stable...
then uninstall to verify Available Software Sites are cleaned while uninstalling
was (Author: nickboldt):
Updated patches to remove everything added under the covers during JBDS BYOE
installation so the resulting uninstalled Eclipse looks the same as before.
* [^JBDS2402-JBDS2371.patch_v3.txt]
* [^JBDS2402-40x.patch_v3.txt]
ensure BYOE feature provides URL from which to update, and cleans up
URLs when uninstalled
-------------------------------------------------------------------------------------------
Key: JBDS-2402
URL: https://issues.jboss.org/browse/JBDS-2402
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: updatesite
Affects Versions: 6.0.0.CR1
Reporter: Nick Boldt
Assignee: Nick Boldt
Labels: respin-b
Fix For: 6.0.0.CR1
Attachments: JBDS2402-40x.patch_v2.txt, JBDS2402-40x.patch_v3.txt,
JBDS2402-JBDS2371.patch_v2.txt, JBDS2402-JBDS2371.patch_v3.txt
We recently removed 'org.eclipse.equinox.p2.touchpoint.eclipse.addRepository'
touchpoints from *p2.inf files in JBDS, and the result is that until a user scans
Central's update site, there are no entries listed in the Available Software Sites
pref page.
So, we need to ensure that this is added back in.
Rather than putting it in the JBDS Branded Product feature, however, I would rather see
it put into the BYOE / Core Features feature, so that anyone who's installed from
Marketplace can also get updates from the site on devstudio.jboss.com. We can also use
this mechanism to replace the 6.0-staging site (currently in Marketplace) by the 6.0 site
(once we go GA) and clean the old site out of users' Eclipse installs so they only get
updates from the official site, not the staging one.
--
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
7:42 p.m.
New subject: [JBoss JIRA] (JBDS-2402) ensure BYOE feature provides URL from which to update, and cleans up URLs when uninstalled
[
https://issues.jboss.org/browse/JBDS-2402?page=com.atlassian.jira.plugin....
]
Nick Boldt resolved JBDS-2402.
------------------------------
Resolution: Done
Resolving. To be closed after QE verification as noted in previous comment.
ensure BYOE feature provides URL from which to update, and cleans up
URLs when uninstalled
-------------------------------------------------------------------------------------------
Key: JBDS-2402
URL: https://issues.jboss.org/browse/JBDS-2402
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: updatesite
Affects Versions: 6.0.0.CR1
Reporter: Nick Boldt
Assignee: Nick Boldt
Labels: respin-b
Fix For: 6.0.0.CR1, 6.0.0.GA
Attachments: JBDS2402-40x.patch_v2.txt, JBDS2402-40x.patch_v3.txt,
JBDS2402-JBDS2371.patch_v2.txt, JBDS2402-JBDS2371.patch_v3.txt
We recently removed 'org.eclipse.equinox.p2.touchpoint.eclipse.addRepository'
touchpoints from *p2.inf files in JBDS, and the result is that until a user scans
Central's update site, there are no entries listed in the Available Software Sites
pref page.
So, we need to ensure that this is added back in.
Rather than putting it in the JBDS Branded Product feature, however, I would rather see
it put into the BYOE / Core Features feature, so that anyone who's installed from
Marketplace can also get updates from the site on devstudio.jboss.com. We can also use
this mechanism to replace the 6.0-staging site (currently in Marketplace) by the 6.0 site
(once we go GA) and clean the old site out of users' Eclipse installs so they only get
updates from the official site, not the staging one.
--
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
7:42 p.m.
New subject: [JBoss JIRA] (JBDS-2402) ensure BYOE feature provides URL from which to update, and cleans up URLs when uninstalled
[
https://issues.jboss.org/browse/JBDS-2402?page=com.atlassian.jira.plugin....
]
Nick Boldt updated JBDS-2402:
-----------------------------
Fix Version/s: (was: 6.0.0.GA)
ensure BYOE feature provides URL from which to update, and cleans up
URLs when uninstalled
-------------------------------------------------------------------------------------------
Key: JBDS-2402
URL: https://issues.jboss.org/browse/JBDS-2402
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: updatesite
Affects Versions: 6.0.0.CR1
Reporter: Nick Boldt
Assignee: Nick Boldt
Labels: respin-b
Fix For: 6.0.0.CR1
Attachments: JBDS2402-40x.patch_v2.txt, JBDS2402-40x.patch_v3.txt,
JBDS2402-JBDS2371.patch_v2.txt, JBDS2402-JBDS2371.patch_v3.txt
We recently removed 'org.eclipse.equinox.p2.touchpoint.eclipse.addRepository'
touchpoints from *p2.inf files in JBDS, and the result is that until a user scans
Central's update site, there are no entries listed in the Available Software Sites
pref page.
So, we need to ensure that this is added back in.
Rather than putting it in the JBDS Branded Product feature, however, I would rather see
it put into the BYOE / Core Features feature, so that anyone who's installed from
Marketplace can also get updates from the site on devstudio.jboss.com. We can also use
this mechanism to replace the 6.0-staging site (currently in Marketplace) by the 6.0 site
(once we go GA) and clean the old site out of users' Eclipse installs so they only get
updates from the official site, not the staging one.
--
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
8:18 p.m.
New subject: [JBoss JIRA] (JBDS-2402) ensure BYOE feature provides URL from which to update, and cleans up URLs when uninstalled
[
https://issues.jboss.org/browse/JBDS-2402?page=com.atlassian.jira.plugin....
]
Nick Boldt edited comment on JBDS-2402 at 11/27/12 2:17 PM:
------------------------------------------------------------
Resolving. Verified by installing
http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-6.0_stable...
BYOE feature into Eclipse Juno SR1 on L64.
To be closed after QE verification as noted in previous comment.
was (Author: nickboldt):
Resolving. To be closed after QE verification as noted in previous comment.
ensure BYOE feature provides URL from which to update, and cleans up
URLs when uninstalled
-------------------------------------------------------------------------------------------
Key: JBDS-2402
URL: https://issues.jboss.org/browse/JBDS-2402
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: updatesite
Affects Versions: 6.0.0.CR1
Reporter: Nick Boldt
Assignee: Nick Boldt
Labels: respin-b
Fix For: 6.0.0.CR1
Attachments: JBDS2402-40x.patch_v2.txt, JBDS2402-40x.patch_v3.txt,
JBDS2402-JBDS2371.patch_v2.txt, JBDS2402-JBDS2371.patch_v3.txt
We recently removed 'org.eclipse.equinox.p2.touchpoint.eclipse.addRepository'
touchpoints from *p2.inf files in JBDS, and the result is that until a user scans
Central's update site, there are no entries listed in the Available Software Sites
pref page.
So, we need to ensure that this is added back in.
Rather than putting it in the JBDS Branded Product feature, however, I would rather see
it put into the BYOE / Core Features feature, so that anyone who's installed from
Marketplace can also get updates from the site on devstudio.jboss.com. We can also use
this mechanism to replace the 6.0-staging site (currently in Marketplace) by the 6.0 site
(once we go GA) and clean the old site out of users' Eclipse installs so they only get
updates from the official site, not the staging one.
--
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
4231
days inactive
4232
days old
jbosstools-issues@lists.jboss.org
25 comments
3 participants
participants (3)
-
Max Rydahl Andersen (JIRA) -
Mickael Istria (JIRA)
-
Nick Boldt (JIRA)