[JBoss JIRA] (JBIDE-15536) For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [Base]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15536?page=com.atlassian.jira.plugi... ]
Alexey Kazakov closed JBIDE-15536.
----------------------------------
> For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [Base]
> ---------------------------------------------------
>
> Key: JBIDE-15536
> URL: https://issues.jboss.org/browse/JBIDE-15536
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: usage
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Priority: Blocker
> Labels: task
> Fix For: 4.1.1.Alpha2
>
>
> For JBIDE 4.1.1.Alpha2 [Base]: Please perform the following tasks:
> 0. If nothing has changed in your component since the last milestone or GA release on this branch, *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Alpha2
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1.
> *NOTE:* If you already did this for the previous milestone you do *not* need to do so again.
> {code}
> mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:set-version -DnewVersion=1.0.1-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.1.1.Alpha2-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.1.1.Alpha2-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha2;
> {code}
> mvn clean verify -Dtpc.version=4.31.0.Alpha2
> {code}
> 4. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha2x branch;
> {code}
> git checkout jbosstools-4.1.x
> git pull origin jbosstools-4.1.x
> git checkout -b jbosstools-4.1.1.Alpha2x
> git push origin jbosstools-4.1.1.Alpha2x
> {code}
> 5. Close (not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Base task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
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
12 years, 6 months
[JBoss JIRA] (JBIDE-15552) ensure JBDS 7.0.1 branded product feature is versioned 7.0.1, not 7.1.0
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15552?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-15552:
-------------------------------
Description:
Realized in testing the 7.1.0.CR1 build that the Branded Product feature (com.jboss.jbds.all) is incorrectly versioned 7.1.0 instead of 7.0.1, so when you update using the 7.0.1.CR1 site, you get this:
!https://issues.jboss.org/secure/attachment/12364790/12364790_15509_JBDS701.CR1.png!
{code}
$➔ find . -name com.jboss.jbds.all\*
./studio/p2/org.eclipse.equinox.p2.core/cache/binary/com.jboss.jbds.all.executable.gtk.linux.x86_64_7.1.0.GA-v20130924-0106-B4
./studio/p2/org.eclipse.equinox.p2.core/cache/binary/com.jboss.jbds.all.executable.gtk.linux.x86_64_7.0.0.GA-v20130720-0044-B364
{code}
was:
Realized in testing the 7.1.0.CR1 build that the Branded Product feature (com.jboss.jbds.all) is incorrectly versioned 7.1.0 instead of 7.0.1:
{code}
$➔ find . -name com.jboss.jbds.all\*
./studio/p2/org.eclipse.equinox.p2.core/cache/binary/com.jboss.jbds.all.executable.gtk.linux.x86_64_7.1.0.GA-v20130924-0106-B4
./studio/p2/org.eclipse.equinox.p2.core/cache/binary/com.jboss.jbds.all.executable.gtk.linux.x86_64_7.0.0.GA-v20130720-0044-B364
{code}
> ensure JBDS 7.0.1 branded product feature is versioned 7.0.1, not 7.1.0
> -----------------------------------------------------------------------
>
> Key: JBIDE-15552
> URL: https://issues.jboss.org/browse/JBIDE-15552
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build
> Affects Versions: 4.1.0.1.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.1.0.1.Final
>
>
> Realized in testing the 7.1.0.CR1 build that the Branded Product feature (com.jboss.jbds.all) is incorrectly versioned 7.1.0 instead of 7.0.1, so when you update using the 7.0.1.CR1 site, you get this:
> !https://issues.jboss.org/secure/attachment/12364790/12364790_15509_JBDS701.CR1.png!
> {code}
> $➔ find . -name com.jboss.jbds.all\*
> ./studio/p2/org.eclipse.equinox.p2.core/cache/binary/com.jboss.jbds.all.executable.gtk.linux.x86_64_7.1.0.GA-v20130924-0106-B4
> ./studio/p2/org.eclipse.equinox.p2.core/cache/binary/com.jboss.jbds.all.executable.gtk.linux.x86_64_7.0.0.GA-v20130720-0044-B364
> {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
12 years, 6 months
[JBoss JIRA] (JBIDE-15552) ensure JBDS 7.0.1 branded product feature is versioned 7.0.1, not 7.1.0
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-15552:
----------------------------------
Summary: ensure JBDS 7.0.1 branded product feature is versioned 7.0.1, not 7.1.0
Key: JBIDE-15552
URL: https://issues.jboss.org/browse/JBIDE-15552
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: build
Affects Versions: 4.1.0.1.Final
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 4.1.0.1.Final
Realized in testing the 7.1.0.CR1 build that the Branded Product feature (com.jboss.jbds.all) is incorrectly versioned 7.1.0 instead of 7.0.1:
{code}
$➔ find . -name com.jboss.jbds.all\*
./studio/p2/org.eclipse.equinox.p2.core/cache/binary/com.jboss.jbds.all.executable.gtk.linux.x86_64_7.1.0.GA-v20130924-0106-B4
./studio/p2/org.eclipse.equinox.p2.core/cache/binary/com.jboss.jbds.all.executable.gtk.linux.x86_64_7.0.0.GA-v20130720-0044-B364
{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
12 years, 6 months
[JBoss JIRA] (JBIDE-15509) prepare for JBDS 7.0.1 patch release
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15509?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-15509 at 9/26/13 2:11 PM:
-------------------------------------------------------------
Testing update paths:
* JBDS 7.0.1
1. Install JBDS from jbdevstudio-product-universal-7.0.0.GA-v20130720-0044-B364.jar
2. Launch JBDS.
3. Window > Preferences > Install/Update > Available Software Sites > Add... > http://www.qa.jboss.com/binaries/RHDS/discovery/development/7.0.1.CR1/ > OK > OK
4. Help > Check for Updates > Install com.jboss.jbds.all 7.0.1. Restart when prompted.
!15509_JBDS701.CR1.png!
{code}
$➔ find . -maxdepth 2 -name org.jboss.tools.project.examples\* | sort
./features/org.jboss.tools.project.examples.feature_1.5.1.Final-v20130923-2322-B9
./plugins/org.jboss.tools.project.examples_1.5.0.Final-v20130719-2050-B70.jar
./plugins/org.jboss.tools.project.examples_1.5.1.Final-v20130923-2322-B9.jar
./plugins/org.jboss.tools.project.examples.cheatsheet_1.5.0.Final-v20130719-2050-B70.jar
./plugins/org.jboss.tools.project.examples.cheatsheet_1.5.1.Final-v20130923-2322-B9.jar
{code}
* JBT 4.1.0.1
1. Install Eclipse from eclipse-jee-kepler-R-linux-gtk-x86_64.tar.gz
2. Launch Eclipse, then Help > Install new software > http://download.jboss.org/jbosstools/updates/stable/kepler/
(or use downloaded update site zip jar:file:/home/nboldt/tmp/JBossTools/jbosstools-Update-4.1.0.Final_2013-07-19_19-47-52-B380.zip!/ ). Select the "Abridged JBoss Tools" category and install. Restart when prompted.
3. Window > Preferences > Install/Update > Available Software Sites > Add... > http://download.jboss.org/jbosstools/updates/JBossTools-4.1.0.1.CR1.core/ > OK > OK
4. Help > Check for Updates > Install project.examples.feature 1.5.1. Restart when prompted.
!15509_JBT4101.CR1.png!
{code}
$➔ find . -maxdepth 2 -name org.jboss.tools.project.examples\* | sort
./features/org.jboss.tools.project.examples.feature_1.5.1.Final-v20130923-2322-B9
./plugins/org.jboss.tools.project.examples_1.5.0.Final-v20130719-2050-B70.jar
./plugins/org.jboss.tools.project.examples_1.5.1.Final-v20130923-2322-B9.jar
./plugins/org.jboss.tools.project.examples.cheatsheet_1.5.0.Final-v20130719-2050-B70.jar
./plugins/org.jboss.tools.project.examples.cheatsheet_1.5.1.Final-v20130923-2322-B9.jar
{code}
was (Author: nickboldt):
Testing update paths:
* JBDS 7.0.1
1. Install JBDS from jbdevstudio-product-universal-7.0.0.GA-v20130720-0044-B364.jar
2. Launch JBDS.
3. Window > Preferences > Install/Update > Available Software Sites > Add... > http://www.qa.jboss.com/binaries/RHDS/discovery/development/7.0.1.CR1/ > OK > OK
4. Help > Check for Updates > Install com.jboss.jbds.all 7.0.1. Restart when prompted.
!15509_JBDS701.CR1.png!
* JBT 4.1.0.1
1. Install Eclipse from eclipse-jee-kepler-R-linux-gtk-x86_64.tar.gz
2. Launch Eclipse, then Help > Install new software > http://download.jboss.org/jbosstools/updates/stable/kepler/
(or use downloaded update site zip jar:file:/home/nboldt/tmp/JBossTools/jbosstools-Update-4.1.0.Final_2013-07-19_19-47-52-B380.zip!/ ). Select the "Abridged JBoss Tools" category and install. Restart when prompted.
3. Window > Preferences > Install/Update > Available Software Sites > Add... > http://download.jboss.org/jbosstools/updates/JBossTools-4.1.0.1.CR1.core/ > OK > OK
4. Help > Check for Updates > Install project.examples.feature 1.5.1. Restart when prompted.
!15509_JBT4101.CR1.png!
> 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
12 years, 6 months
[JBoss JIRA] (JBIDE-15509) prepare for JBDS 7.0.1 patch release
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15509?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-15509:
-------------------------------
Attachment: 15509_JBT4101.CR1.png
15509_JBDS701.CR1.png
Testing update paths:
* JBDS 7.0.1
1. Install JBDS from jbdevstudio-product-universal-7.0.0.GA-v20130720-0044-B364.jar
2. Launch JBDS.
3. Window > Preferences > Install/Update > Available Software Sites > Add... > http://www.qa.jboss.com/binaries/RHDS/discovery/development/7.0.1.CR1/ > OK > OK
4. Help > Check for Updates > Install com.jboss.jbds.all 7.0.1. Restart when prompted.
!15509_JBDS701.CR1.png!
* JBT 4.1.0.1
1. Install Eclipse from eclipse-jee-kepler-R-linux-gtk-x86_64.tar.gz
2. Launch Eclipse, then Help > Install new software > http://download.jboss.org/jbosstools/updates/stable/kepler/
(or use downloaded update site zip jar:file:/home/nboldt/tmp/JBossTools/jbosstools-Update-4.1.0.Final_2013-07-19_19-47-52-B380.zip!/ ). Select the "Abridged JBoss Tools" category and install. Restart when prompted.
3. Window > Preferences > Install/Update > Available Software Sites > Add... > http://download.jboss.org/jbosstools/updates/JBossTools-4.1.0.1.CR1.core/ > OK > OK
4. Help > Check for Updates > Install project.examples.feature 1.5.1. Restart when prompted.
!15509_JBT4101.CR1.png!
> 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
12 years, 6 months
[JBoss JIRA] (JBIDE-15534) For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [Server]
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15534?page=com.atlassian.jira.plugi... ]
Rob Stryker closed JBIDE-15534.
-------------------------------
Assignee: Rob Stryker
Resolution: Done
Done
> For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [Server]
> -----------------------------------------------------
>
> Key: JBIDE-15534
> URL: https://issues.jboss.org/browse/JBIDE-15534
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: server
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: task
> Fix For: 4.1.1.Alpha2
>
>
> For JBIDE 4.1.1.Alpha2 [Server]: Please perform the following tasks:
> 0. If nothing has changed in your component since the last milestone or GA release on this branch, *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Alpha2
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1.
> *NOTE:* If you already did this for the previous milestone you do *not* need to do so again.
> {code}
> mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:set-version -DnewVersion=1.0.1-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.1.1.Alpha2-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.1.1.Alpha2-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha2;
> {code}
> mvn clean verify -Dtpc.version=4.31.0.Alpha2
> {code}
> *{color:orange}If the above target platform does not yet exist, try 4.31.0.Alpha2-SNAPSHOT or 4.31.0.Alpha1.{color}*
> 4. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha2x branch;
> {code}
> git checkout jbosstools-4.1.x
> git pull origin jbosstools-4.1.x
> git checkout -b jbosstools-4.1.1.Alpha2x
> git push origin jbosstools-4.1.1.Alpha2x
> {code}
> 5. Close (not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Server task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
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
12 years, 6 months
[JBoss JIRA] (JBIDE-15534) For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [Server]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15534?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-15534:
-------------------------------
Description:
For JBIDE 4.1.1.Alpha2 [Server]: Please perform the following tasks:
0. If nothing has changed in your component since the last milestone or GA release on this branch, *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Alpha2
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1.
*NOTE:* If you already did this for the previous milestone you do *not* need to do so again.
{code}
mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:set-version -DnewVersion=1.0.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.1.1.Alpha2-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.1.Alpha2-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha2;
{code}
mvn clean verify -Dtpc.version=4.31.0.Alpha2
{code}
*{color:orange}If the above target platform does not yet exist, try 4.31.0.Alpha2-SNAPSHOT or 4.31.0.Alpha1.{color}*
4. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha2x branch;
{code}
git checkout jbosstools-4.1.x
git pull origin jbosstools-4.1.x
git checkout -b jbosstools-4.1.1.Alpha2x
git push origin jbosstools-4.1.1.Alpha2x
{code}
5. Close (not resolve) this JIRA when done.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Server task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
was:
For JBIDE 4.1.1.Alpha2 [Server]: Please perform the following tasks:
0. If nothing has changed in your component since the last milestone or GA release on this branch, *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Alpha2
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1.
*NOTE:* If you already did this for the previous milestone you do *not* need to do so again.
{code}
mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:set-version -DnewVersion=1.0.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.1.1.Alpha2-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.1.Alpha2-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha2;
{code}
mvn clean verify -Dtpc.version=4.31.0.Alpha2
{code}
4. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha2x branch;
{code}
git checkout jbosstools-4.1.x
git pull origin jbosstools-4.1.x
git checkout -b jbosstools-4.1.1.Alpha2x
git push origin jbosstools-4.1.1.Alpha2x
{code}
5. Close (not resolve) this JIRA when done.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Server task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
> For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [Server]
> -----------------------------------------------------
>
> Key: JBIDE-15534
> URL: https://issues.jboss.org/browse/JBIDE-15534
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: server
> Reporter: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.1.1.Alpha2
>
>
> For JBIDE 4.1.1.Alpha2 [Server]: Please perform the following tasks:
> 0. If nothing has changed in your component since the last milestone or GA release on this branch, *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Alpha2
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1.
> *NOTE:* If you already did this for the previous milestone you do *not* need to do so again.
> {code}
> mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:set-version -DnewVersion=1.0.1-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.1.1.Alpha2-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.1.1.Alpha2-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha2;
> {code}
> mvn clean verify -Dtpc.version=4.31.0.Alpha2
> {code}
> *{color:orange}If the above target platform does not yet exist, try 4.31.0.Alpha2-SNAPSHOT or 4.31.0.Alpha1.{color}*
> 4. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha2x branch;
> {code}
> git checkout jbosstools-4.1.x
> git pull origin jbosstools-4.1.x
> git checkout -b jbosstools-4.1.1.Alpha2x
> git push origin jbosstools-4.1.1.Alpha2x
> {code}
> 5. Close (not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Server task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
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
12 years, 6 months
[JBoss JIRA] (JBIDE-15527) For JBIDE 4.1.1.Alpha2: Code Freeze + Branch
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15527?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-15527:
-------------------------------
Description:
For JBIDE 4.1.1.Alpha2: Please perform the following tasks:
0. If nothing has changed in your component since the last milestone or GA release on this branch, *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Alpha2
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1.
*NOTE:* If you already did this for the previous milestone you do *not* need to do so again.
{code}
mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:set-version -DnewVersion=1.0.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.1.1.Alpha2-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.1.Alpha2-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha2;
{code}
mvn clean verify -Dtpc.version=4.31.0.Alpha2
{code}
*{color:orange}If the above target platform does not yet exist, try 4.31.0.Alpha2-SNAPSHOT or 4.31.0.Alpha1.{color}*
4. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha2x branch;
{code}
git checkout jbosstools-4.1.x
git pull origin jbosstools-4.1.x
git checkout -b jbosstools-4.1.1.Alpha2x
git push origin jbosstools-4.1.1.Alpha2x
{code}
5. Close (not resolve) this JIRA when done.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
See also: JBDS-2773
was:
For JBIDE 4.1.1.Alpha2: Please perform the following tasks:
0. If nothing has changed in your component since the last milestone or GA release on this branch, *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Alpha2
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1.
*NOTE:* If you already did this for the previous milestone you do *not* need to do so again.
{code}
mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:set-version -DnewVersion=1.0.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.1.1.Alpha2-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.1.Alpha2-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha2;
{code}
mvn clean verify -Dtpc.version=4.31.0.Alpha2
{code}
4. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha2x branch;
{code}
git checkout jbosstools-4.1.x
git pull origin jbosstools-4.1.x
git checkout -b jbosstools-4.1.1.Alpha2x
git push origin jbosstools-4.1.1.Alpha2x
{code}
5. Close (not resolve) this JIRA when done.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
See also: JBDS-2773
> For JBIDE 4.1.1.Alpha2: Code Freeze + Branch
> --------------------------------------------
>
> Key: JBIDE-15527
> URL: https://issues.jboss.org/browse/JBIDE-15527
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Reporter: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.1.1.Alpha2
>
>
> For JBIDE 4.1.1.Alpha2: Please perform the following tasks:
> 0. If nothing has changed in your component since the last milestone or GA release on this branch, *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Alpha2
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1.
> *NOTE:* If you already did this for the previous milestone you do *not* need to do so again.
> {code}
> mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:set-version -DnewVersion=1.0.1-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.1.1.Alpha2-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.1.1.Alpha2-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha2;
> {code}
> mvn clean verify -Dtpc.version=4.31.0.Alpha2
> {code}
> *{color:orange}If the above target platform does not yet exist, try 4.31.0.Alpha2-SNAPSHOT or 4.31.0.Alpha1.{color}*
> 4. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha2x branch;
> {code}
> git checkout jbosstools-4.1.x
> git pull origin jbosstools-4.1.x
> git checkout -b jbosstools-4.1.1.Alpha2x
> git push origin jbosstools-4.1.1.Alpha2x
> {code}
> 5. Close (not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
> See also: JBDS-2773
--
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
12 years, 6 months
[JBoss JIRA] (JBIDE-15530) For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [VPE]
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15530?page=com.atlassian.jira.plugi... ]
Denis Golovin edited comment on JBIDE-15530 at 9/26/13 1:51 PM:
----------------------------------------------------------------
reopened because of https://github.com/jbosstools/jbosstools-vpe/compare/jbosstools-4.1.1.Alp...
was (Author: dgolovin):
reopened because of [JBIDE-15362 Page is just simply rendered in VPE editor] was fixed in 4.1.x branch
> For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [VPE]
> --------------------------------------------------
>
> Key: JBIDE-15530
> URL: https://issues.jboss.org/browse/JBIDE-15530
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: visual-page-editor-core
> Reporter: Nick Boldt
> Assignee: Yahor Radtsevich
> Priority: Blocker
> Labels: task
> Fix For: 4.1.1.Alpha2
>
>
> For JBIDE 4.1.1.Alpha2 [VPE]: Please perform the following tasks:
> 0. If nothing has changed in your component since the last milestone or GA release on this branch, *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Alpha2
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1.
> *NOTE:* If you already did this for the previous milestone you do *not* need to do so again.
> {code}
> mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:set-version -DnewVersion=1.0.1-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.1.1.Alpha2-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.1.1.Alpha2-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha2;
> {code}
> mvn clean verify -Dtpc.version=4.31.0.Alpha2
> {code}
> 4. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha2x branch;
> {code}
> git checkout jbosstools-4.1.x
> git pull origin jbosstools-4.1.x
> git checkout -b jbosstools-4.1.1.Alpha2x
> git push origin jbosstools-4.1.1.Alpha2x
> {code}
> 5. Close (not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for VPE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
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
12 years, 6 months
[JBoss JIRA] (JBIDE-15509) prepare for JBDS 7.0.1 patch release
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15509?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-15509:
------------------------------------
Initial JBoss Tools build results have been published here for QE to review:
http://download.jboss.org/jbosstools/updates/JBossTools-4.1.0.1.CR1.core/
http://download.jboss.org/jbosstools/discovery/development/4.1.0.1.CR1/
> 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
>
>
> 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
12 years, 6 months