[
https://issues.jboss.org/browse/JBIDE-15509?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-15509:
------------------------------------
After much debate it's been decided that in addition to the actual reason for this
patch release, JBIDE-15494, we ought to also update the JBDS update site to include the
Kepler SR1 bits, since they were released just last week.
Respinning third candidate release now:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
>=7
Will push to QE when done.
prepare for JBDS 7.0.1 patch release
------------------------------------
Key: JBIDE-15509
URL:
https://issues.jboss.org/browse/JBIDE-15509
Project: Tools (JBoss Tools)
Issue Type: Task
Components: updatesite
Affects Versions: 4.1.0.Final
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 4.1.0.1.Final
Attachments: 15509_JBDS701.CR1.png, 15509_JBT4101.CR1.png
Placeholder JIRA to contain work needed to do to release JBDS 7.0.1.GA:
1. branch jbosstools-central from 4.1.x to 4.1.0.x
2. adjust jbosstools-central/site/category.xml so it only contains the affected features
(and feature.sources)
3. build Central using a new job, eg.,
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-central_410/ which gets
its sources from the correct fork/branch
4. create new composite staging site containing the last stable release + the new staging
site for jbosstools-central, eg.,
http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.1....
5. branch jbdevstudio-product from 4.1.x to 4.1.0.x
6. ensure that JBDS sources are correctly versioned (eg., 7.0.1 not 7.1.0)
7. build JBDS using a new job, eg.,
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.product_70/ which sets
-DBUILD_ALIAS=GA, pulls from the correct branch origin/jbosstools-4.1.0.x, and sets these
overrides in the maven configuration:
{code}
jbosstools-nightly-staging-composite=http://download.jboss.org/jbosstools...
jbosstools-nightly=http://download.jboss.org/jbosstools/updates/nightly/c...
{code}
--
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