[jbosstools-issues] [JBoss JIRA] (JBIDE-13288) discovery URLs should use major/minor/service/milestone convention

Mon Apr 22 10:07:54 EDT 2013

    [ https://issues.jboss.org/browse/JBIDE-13288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12769147#comment-12769147 ] 

Nick Boldt edited comment on JBIDE-13288 at 4/22/13 10:07 AM:
--------------------------------------------------------------

Sure, but if we release: 

* https://devstudio.jboss.com/discovery/7/0/0/Alpha1/devstudio-directory.xml
* https://devstudio.jboss.com/discovery/7/0/0/Alpha2/devstudio-directory.xml
* https://devstudio.jboss.com/discovery/7/0/0/Beta1/devstudio-directory.xml
* https://devstudio.jboss.com/discovery/7/0/0/Beta2/devstudio-directory.xml
* https://devstudio.jboss.com/discovery/7/0/0/CR1/devstudio-directory.xml
* https://devstudio.jboss.com/discovery/7/0/0/CR2/devstudio-directory.xml
* https://devstudio.jboss.com/discovery/7/0/0/GA/devstudio-directory.xml

The only one that an end user (not QE, but a customer) will see is 

* https://devstudio.jboss.com/discovery/7/0/0/GA/devstudio-directory.xml

And then when we roll out JBDS 7.0.1.GA, we would need to either change the URL embedded in the user's jbdevstudio.ini to point to 

* https://devstudio.jboss.com/discovery/7/0/1/GA/devstudio-directory.xml

Or we'd have to replace the contents in 

* https://devstudio.jboss.com/discovery/7/0/0/GA/devstudio-directory.xml

to include the new 7.0.1 discovery plugin.

Changing their .ini file requires they install the new JBDS 7.0.1. Simply updating the static URL to add a new plugin doesn't require that they update. And since one of the goals of Central is to be able to release 3rd party updates without making users update JBDS itself, we need a STATIC URL, not one that changes w/ every release.

Therefore, the only benefit to having these snapshot URLs which change w/ every milestone & GA release is to be able to see what we had for past JBDS releases.

IMHO the benefit to having a stable URL like https://devstudio.jboss.com/updates/7.0/devstudio-directory.xml for all JBDS 7.0.x releases outweighs the benefit we get from having unique URLs for each milestone's directory.xml file.

---

So, bottom line, I don't see the value in this. We can always rollback a Central update simply by updating https://devstudio.jboss.com/discovery/7.0/devstudio-directory.xml to point to an older plugin jar.

      was (Author: nickboldt):
    Sure, but if we release: 

* https://devstudio.jboss.com/discovery/7/0/0/Alpha1/devstudio-directory.xml
* https://devstudio.jboss.com/discovery/7/0/0/Alpha2/devstudio-directory.xml
* https://devstudio.jboss.com/discovery/7/0/0/Beta1/devstudio-directory.xml
* https://devstudio.jboss.com/discovery/7/0/0/Beta2/devstudio-directory.xml
* https://devstudio.jboss.com/discovery/7/0/0/CR1/devstudio-directory.xml
* https://devstudio.jboss.com/discovery/7/0/0/CR2/devstudio-directory.xml
* https://devstudio.jboss.com/discovery/7/0/0/GA/devstudio-directory.xml

The only one that an end user will see is 

* https://devstudio.jboss.com/discovery/7/0/0/GA/devstudio-directory.xml

And then when we roll out JBDS 7.0.1.GA, we would need to either change the URL embedded in the user's jbdevstudio.ini to point to 

* https://devstudio.jboss.com/discovery/7/0/1/GA/devstudio-directory.xml

Or we'd have to replace the contents in 

* https://devstudio.jboss.com/discovery/7/0/0/GA/devstudio-directory.xml

to include the new 7.0.1 discovery plugin.

Changing their .ini file requires they install the new JBDS 7.0.1. Simply updating the static URL to add a new plugin doesn't require that they update. And since one of the goals of Central is to be able to release 3rd party updates without making users update JBDS itself, we need a STATIC URL, not one that changes w/ every release.

Therefore, the only benefit to having these snapshot URLs which change w/ every milestone & GA release is to be able to see what we had for past JBDS releases.

IMHO the benefit to having a stable URL like https://devstudio.jboss.com/updates/7.0/devstudio-directory.xml for all JBDS 7.0.x releases outweighs the benefit we get from having unique URLs for each milestone's directory.xml file.

---

So, bottom line, I don't see the value in this. We can always rollback a Central update simply by updating https://devstudio.jboss.com/discovery/7.0/devstudio-directory.xml to point to an older plugin jar.

> discovery URLs should use major/minor/service/milestone convention 
> -------------------------------------------------------------------
>
>                 Key: JBIDE-13288
>                 URL: https://issues.jboss.org/browse/JBIDE-13288
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: central
>    Affects Versions: 4.1.0.Alpha1
>            Reporter: Nick Boldt
>            Assignee: Max Rydahl Andersen
>            Priority: Minor
>             Fix For: 4.1.0.Beta1
>
>
> Instead of 
> https://devstudio.jboss.com/updates/6.0/devstudio-directory.xml
> We should consider using something like
> https://devstudio.jboss.com/discovery/6/1/0/Alpha1/devstudio-directory.xml

--
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