[JBoss JIRA] (JBIDE-10654) software/update tab - how do handle differences for jboss tools/JBDS and different versions
3:30 a.m.
Max Rydahl Andersen created JBIDE-10654:
-------------------------------------------
Summary: 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
1:57 p.m.
[
https://issues.jboss.org/browse/JBIDE-10654?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-10654:
------------------------------------
Please elaborate. And consider that SOA Tooling sites (for JBT and JBDS) won't be
releasing at the same time as Core.
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
4:58 p.m.
[
https://issues.jboss.org/browse/JBIDE-10654?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-10654:
---------------------------------------------
The discovery.xml should not be tied to neither core nor SOA.
The problem here how to handle different setups for at least full releases and
milestones.
nightly builds we could handle with a system property.
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
4:58 p.m.
[
https://issues.jboss.org/browse/JBIDE-10654?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-10654:
---------------------------------------------
The discovery.xml should not be tied to neither core nor SOA.
The problem here how to handle different setups for at least full releases and
milestones.
nightly builds we could handle with a system property.
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
12:06 a.m.
[
https://issues.jboss.org/browse/JBIDE-10654?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-10654:
-------------------------------
Comment: was deleted
(was: The discovery.xml should not be tied to neither core nor SOA.
The problem here how to handle different setups for at least full releases and
milestones.
nightly builds we could handle with a system property.
)
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
12:08 a.m.
[
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
3:21 p.m.
[
https://issues.jboss.org/browse/JBIDE-10654?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen updated JBIDE-10654:
----------------------------------------
Fix Version/s: 3.3.0.Beta2
(was: 3.3.0.Beta1)
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: Nick Boldt
Priority: Critical
Fix For: 3.3.0.Beta2
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
3:21 p.m.
[
https://issues.jboss.org/browse/JBIDE-10654?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-10654:
---------------------------------------------
I believe most of this is handled but putting to b2 for review.
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: Nick Boldt
Priority: Critical
Fix For: 3.3.0.Beta2
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
4:12 p.m.
[
https://issues.jboss.org/browse/JBIDE-10654?page=com.atlassian.jira.plugi...
]
Nick Boldt closed JBIDE-10654.
------------------------------
Resolution: Done
We can only provide a single URL for the directory.xml file for a release stream (JBT
3.3.x, JBDS 5.x), but we can change the content to which that xml file refers (a
different/updated discovery plugin).
This allows us to "out of band" add/remove stuff to Central.
Being limited to a single URL is essentially the same as being limited to a single update
site (/development/ or /stable/) so this is no great loss.
We just need to make sure we remember to set the default URL to the /stable/ URL just
before GA so that it will point at the correct target URL.
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: Nick Boldt
Priority: Critical
Fix For: 3.3.0.Beta3
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
6:59 a.m.
[
https://issues.jboss.org/browse/JBIDE-10654?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-10654:
---------------------------------------------
Works for me.
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: Nick Boldt
Priority: Critical
Fix For: 3.3.0.Beta3
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
5074
days inactive
5173
days old
jbosstools-issues@lists.jboss.org
9 comments
2 participants
participants (2)
-
Max Rydahl Andersen (JIRA) -
Nick Boldt (JIRA)