[jbosstools-issues] [JBoss JIRA] (JBIDE-15271) update default Central discovery URLs in JBT to point to Final / GA URLs instead of last dev milestone

[Nick Boldt (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-15271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Boldt updated JBIDE-15271:
-------------------------------

    Git Pull Request: https://github.com/jbosstools/jbosstools-central/pull/142, https://github.com/jbosstools/jbosstools-central/pull/144  (was: https://github.com/jbdevstudio/jbdevstudio-product/pull/38, https://github.com/jbosstools/jbosstools-central/pull/141, https://github.com/jbosstools/jbosstools-central/pull/142, https://github.com/jbosstools/jbosstools-central/pull/144)

    
> update default Central discovery URLs in JBT  to point to Final / GA URLs instead of last dev milestone 
> --------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-15271
>                 URL: https://issues.jboss.org/browse/JBIDE-15271
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: central, Discovery
>    Affects Versions: 4.1.0.Final
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>            Priority: Blocker
>             Fix For: 4.1.1.Final
>
>
> 3 files need to be updated:
> * jbdevstudio-product/features/com.jboss.jbds.product.feature/p2.inf
> * jbdevstudio-product/site/associate.properties
> >> https://github.com/jbdevstudio/jbdevstudio-product/pull/38
> and 
> * jbosstools-central/examples/plugins/org.jboss.tools.project.examples/src/org/jboss/tools/project/examples/configurators/DefaultJBossCentralConfigurator.java
> >> https://github.com/jbosstools/jbosstools-central/pull/141
> I can fix the JBDS files, but don't have push rights for the JBT one, sadly. However, since we put the same bits in /stable/kepler/ as in /development/kepler/ this doesn't technically block us for JBT. It's just uncool to have a Final release pointing at the "best development milestone" instead of the "best stable release" site.
> If we GA without changing this, then subsequent new dev milestone builds for Central content will become available to end users, rather than just subsequent stable releases. And should a requirement change within intermediate builds (as m2e or m2e-wtp is wont to do), this might cause problems we can avoid by simply ensuring that there are different URLs for milestone vs. release.
> Therefore, this is an urgent blocker.

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