[jbosstools-issues] [JBoss JIRA] (JBDS-2787) prepare for JBDS 7.0.1 patch release
Nick Boldt (JIRA)
jira-events at lists.jboss.org
Wed Oct 9 12:00:04 EDT 2013
[ https://issues.jboss.org/browse/JBDS-2787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12809526#comment-12809526 ]
Nick Boldt edited comment on JBDS-2787 at 10/9/13 11:59 AM:
------------------------------------------------------------
TODO:
Probably want to update these pages:
https://www.jboss.org/tools/download/stable/4_1
https://www.jboss.org/tools/download/dev/4_1_x
with a note about:
{quote}
The createTempFile issue has been fixed in Java 8 and is set to be included in Java 7 update 45: https://bugs.openjdk.java.net/browse/JDK-8025128 and the Backports section.
Recommendation is to use a version of Oracle JDK 7 up to and including 1.7.0_39 or 1.7.0_45 and after.
{quote}
Matching Oracle issue: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=8025128 (same ID number)
was (Author: nickboldt):
TODO:
Probably want to update these pages:
https://www.jboss.org/tools/download/stable/4_1
https://www.jboss.org/tools/download/dev/4_1_x
with a note about:
{quote}
The createTempFile issue has been fixed in Java 8 and is set to be included in Java 7 update 45: https://bugs.openjdk.java.net/browse/JDK-8025128 and the Backports section.
Recommendation is to use a version of Oracle JDK 7 up to and including 1.7.0_39 or 1.7.0_45 and after.
{quote}
> prepare for JBDS 7.0.1 patch release
> ------------------------------------
>
> Key: JBDS-2787
> URL: https://issues.jboss.org/browse/JBDS-2787
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: updatesite
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 7.0.1.GA
>
> Attachments: 15509_JBDS701.CR1.png, 15509_JBT4101.CR1.png, jbds701ga-updates-avail.png, note-jdk7u40.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.0.kepler/
> 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/builds/staging/_composite_/core/4.1.0.kepler/
> jbosstools-nightly=http://download.jboss.org/jbosstools/updates/nightly/core/4.1.0.kepler/
> {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
More information about the jbosstools-issues
mailing list