[jbosstools-issues] [JBoss JIRA] (JBDS-2702) update default Central discovery URLs in JBDS to point to Final / GA URLs instead of last dev milestone
Nick Boldt (JIRA)
jira-events at lists.jboss.org
Mon Jul 22 11:05:26 EDT 2013
[ https://issues.jboss.org/browse/JBDS-2702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nick Boldt updated JBDS-2702:
-----------------------------
Comment: was deleted
(was: PRs for fixing the pom in the 4.1.x branch and adding more reminders so we don't forget to update in BOTH places next time:
https://github.com/jbosstools/jbosstools-central/pull/142 (41x)
https://github.com/jbosstools/jbosstools-central/pull/144 (master)
These do not block Final/GA release.
---
Effect of this bug is that users of JBT 4.1.0.Final will (at some point, if we release a dev milestone of 4.1.1.x) see 4.1.1.x discovery content rather waiting until 4.1.1.Final is released to see an update to their Discovery content.
But, since we duplicate the content in http://download.jboss.org/jbosstools/updates/stable/kepler/jbosstools-directory.xml to http://download.jboss.org/jbosstools/updates/development/kepler/jbosstools-directory.xml this should not affect anyone adversely, and we can fix this for 4.1.1 (if there's to be a 4.1.1).
)
> update default Central discovery URLs in 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
> >> 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
More information about the jbosstools-issues
mailing list