[jbosstools-issues] [JBoss JIRA] (JBIDE-10654) software/update tab - how do handle differences for jboss tools/JBDS and different versions
[
https://issues.jboss.org/browse/JBIDE-10654?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-10654:
------------------------------------
solution is to change the code in the plugin to point at the correct URL *where the site
will be* after it's published, and use a commandline flag to override that value
during testing.
This is no different than what we do today for the SOA Tooling site being associated w/
its upstream JBT Core site -- in both cases [Update site vs. Central] a properties file
needs to be updated when we move from trunk to the stable_branch.
http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/soa-site/...
software/update tab - how do handle differences for jboss tools/JBDS
and different versions
-------------------------------------------------------------------------------------------
Key: JBIDE-10654
URL: https://issues.jboss.org/browse/JBIDE-10654
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: central
Reporter: Max Rydahl Andersen
Assignee: Snjezana Peco
Priority: Critical
Fix For: 3.3.0.Beta1
currently we hand update a hardcoded value inside central on release to separate
milestone from dev.
but how do we handle different release cycles of jbds, jbt and milestones/full
releases/dev ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira