[jbosstools-issues] [JBoss JIRA] (JBIDE-16657) handle the case where development = stable
[
https://issues.jboss.org/browse/JBIDE-16657?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-16657:
------------------------------------
In this scenario, the same metadata exists in BOTH sites. So... what's the problem if
you hit http://download.jboss.org/jbosstools/updates/development/kepler/ or
http://download.jboss.org/jbosstools/updates/stable/kepler/ and get the same 4.1.1.Final
release bits?
handle the case where development = stable
-------------------------------------------
Key: JBIDE-16657
URL: https://issues.jboss.org/browse/JBIDE-16657
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: website
Reporter: Max Rydahl Andersen
Fix For: 4.2.0.Beta1
once we release Final, the development updatesite actually contains final and not the
latest CR1 so there is a mismatch between website and reality ;)
Suggestion:
Add "marker" to latest_development in products.yml that will add an alert
to the latest active development download that the updatesite actually has stable.
actualcontent: 4.1.0.Final
Would give something like:
Info: 4.1.0.Final have been released and is what you will get when installing from the
development update site.
--
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