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

[ https://issues.jboss.org/browse/JBDS-2702?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2702: ----------------------------- Description: 3 files need to be updated: * jbdevstudio-product/features/com.jboss.jbds.product.feature/p2.inf * jbdevstudio-product/site/associate.properties and * jbosstools-central/examples/plugins/org.jboss.tools.project.examples/src/org/jboss/tools/project/examples/configurators/DefaultJBossCentralConfigurator.java 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. was: 3 files need to be updated: * jbdevstudio-product/features/com.jboss.jbds.product.feature/p2.inf * jbdevstudio-product/site/associate.properties and * jbosstools-central/examples/plugins/org.jboss.tools.project.examples/src/org/jboss/tools/project/examples/configurators/DefaultJBossCentralConfigurator.java 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. > update default Central discovery URLs in JBT and JBDS to point to Final / GA URLs instead of last dev milestone > ---------------------------------------------------------------------------------------------------------------- > > Key: JBDS-2702 > URL: https://issues.jboss.org/browse/JBDS-2702 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Central, installer, P2 Enabled Product > Affects Versions: 7.0.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: respin-c > Fix For: 7.0.0.GA > > > 3 files need to be updated: > * jbdevstudio-product/features/com.jboss.jbds.product.feature/p2.inf > * jbdevstudio-product/site/associate.properties > > and > * jbosstools-central/examples/plugins/org.jboss.tools.project.examples/src/org/jboss/tools/project/examples/configurators/DefaultJBossCentralConfigurator.java > > 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