[JBoss JIRA] (JBIDE-15959) For JBIDE 4.1.1.CR1: Code Freeze + Branch [Forge]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-15959:
----------------------------------
Summary: For JBIDE 4.1.1.CR1: Code Freeze + Branch [Forge]
Key: JBIDE-15959
URL: https://issues.jboss.org/browse/JBIDE-15959
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: forge
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.1.1.CR1 [Forge]: Please perform the following tasks:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.CR1
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:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.1.1.CR1-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.1.CR1-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform versions;
{code}
mvn clean verify -Dtpc.version=4.31.0.Final
mvn clean verify -Dtpc.version=4.31.1.Alpha2-SNAPSHOT # (if still being staged)
{code}
or{code}
mvn clean verify -Dtpc.version=4.31.0.Final
mvn clean verify -Dtpc.version=4.31.1.Alpha2 # (if released)
{code}
4. Branch from your existing jbosstools-4.1.x branch into a new *jbosstools-4.1.1.x* (not CR1x) branch;
{code}
git checkout jbosstools-4.1.x
git pull origin jbosstools-4.1.x
git checkout -b jbosstools-4.1.1.x
git push origin jbosstools-4.1.1.x
{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 Forge 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, 7 months
[JBoss JIRA] (JBDS-2830) For JBDS 7.1.0.CR1: Code Freeze + Branch
by Nick Boldt (JIRA)
Nick Boldt created JBDS-2830:
--------------------------------
Summary: For JBDS 7.1.0.CR1: Code Freeze + Branch
Key: JBDS-2830
URL: https://issues.jboss.org/browse/JBDS-2830
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Task
Security Level: Public (Everyone can see)
Components: installer
Reporter: Nick Boldt
Priority: Blocker
Fix For: 7.1.0.CR1
For JBDS 7.1.0.CR1: Please perform the following tasks:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.CR1
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:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.1.1.CR1-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.1.CR1-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform versions;
{code}
mvn clean verify -Dtpc.version=4.31.0.Final
mvn clean verify -Dtpc.version=4.31.1.Alpha2-SNAPSHOT # (if still being staged)
{code}
or{code}
mvn clean verify -Dtpc.version=4.31.0.Final
mvn clean verify -Dtpc.version=4.31.1.Alpha2 # (if released)
{code}
4. Branch from your existing jbosstools-4.1.x branch into a new *jbosstools-4.1.1.x* (not CR1x) branch;
{code}
git checkout jbosstools-4.1.x
git pull origin jbosstools-4.1.x
git checkout -b jbosstools-4.1.1.x
git push origin jbosstools-4.1.1.x
{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...]
--
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, 7 months
[JBoss JIRA] (JBIDE-15947) For JBIDE 4.1.1.CR1: Code Freeze + Branch [Aerogear]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-15947:
----------------------------------
Summary: For JBIDE 4.1.1.CR1: Code Freeze + Branch [Aerogear]
Key: JBIDE-15947
URL: https://issues.jboss.org/browse/JBIDE-15947
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: aerogear-hybrid
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.1.1.CR1 [Aerogear]: Please perform the following tasks:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.CR1
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:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.1.1.CR1-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.1.CR1-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform versions;
{code}
mvn clean verify -Dtpc.version=4.31.0.Final
mvn clean verify -Dtpc.version=4.31.1.Alpha2-SNAPSHOT # (if still being staged)
{code}
or{code}
mvn clean verify -Dtpc.version=4.31.0.Final
mvn clean verify -Dtpc.version=4.31.1.Alpha2 # (if released)
{code}
4. Branch from your existing jbosstools-4.1.x branch into a new *jbosstools-4.1.1.x* (not CR1x) branch;
{code}
git checkout jbosstools-4.1.x
git pull origin jbosstools-4.1.x
git checkout -b jbosstools-4.1.1.x
git push origin jbosstools-4.1.1.x
{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 Aerogear 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, 7 months
[JBoss JIRA] (JBIDE-15946) For JBIDE 4.1.1.CR1: Code Freeze + Branch
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-15946:
----------------------------------
Summary: For JBIDE 4.1.1.CR1: Code Freeze + Branch
Key: JBIDE-15946
URL: https://issues.jboss.org/browse/JBIDE-15946
Project: Tools (JBoss Tools)
Issue Type: Task
Components: build
Reporter: Nick Boldt
Priority: Blocker
Fix For: 4.1.1.CR1
For JBIDE 4.1.1.CR1: Please perform the following tasks:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.CR1
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:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.1.1.CR1-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.1.CR1-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform versions;
{code}
mvn clean verify -Dtpc.version=4.31.0.Final
mvn clean verify -Dtpc.version=4.31.1.Alpha2-SNAPSHOT # (if still being staged)
{code}
or{code}
mvn clean verify -Dtpc.version=4.31.0.Final
mvn clean verify -Dtpc.version=4.31.1.Alpha2 # (if released)
{code}
4. Branch from your existing jbosstools-4.1.x branch into a new *jbosstools-4.1.1.x* (not CR1x) branch;
{code}
git checkout jbosstools-4.1.x
git pull origin jbosstools-4.1.x
git checkout -b jbosstools-4.1.1.x
git push origin jbosstools-4.1.1.x
{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-2830
--
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, 7 months
[JBoss JIRA] (JBIDE-15948) For JBIDE 4.1.1.CR1: Code Freeze + Branch [JST]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-15948:
----------------------------------
Summary: For JBIDE 4.1.1.CR1: Code Freeze + Branch [JST]
Key: JBIDE-15948
URL: https://issues.jboss.org/browse/JBIDE-15948
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: common/jst/core
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.1.1.CR1 [JST]: Please perform the following tasks:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.CR1
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:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.1.1.CR1-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.1.CR1-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform versions;
{code}
mvn clean verify -Dtpc.version=4.31.0.Final
mvn clean verify -Dtpc.version=4.31.1.Alpha2-SNAPSHOT # (if still being staged)
{code}
or{code}
mvn clean verify -Dtpc.version=4.31.0.Final
mvn clean verify -Dtpc.version=4.31.1.Alpha2 # (if released)
{code}
4. Branch from your existing jbosstools-4.1.x branch into a new *jbosstools-4.1.1.x* (not CR1x) branch;
{code}
git checkout jbosstools-4.1.x
git pull origin jbosstools-4.1.x
git checkout -b jbosstools-4.1.1.x
git push origin jbosstools-4.1.1.x
{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 JST 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, 7 months
[JBoss JIRA] (JBIDE-15949) For JBIDE 4.1.1.CR1: Code Freeze + Branch [VPE]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-15949:
----------------------------------
Summary: For JBIDE 4.1.1.CR1: Code Freeze + Branch [VPE]
Key: JBIDE-15949
URL: https://issues.jboss.org/browse/JBIDE-15949
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: visual-page-editor-core
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.1.1.CR1 [VPE]: Please perform the following tasks:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.CR1
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:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.1.1.CR1-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.1.CR1-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform versions;
{code}
mvn clean verify -Dtpc.version=4.31.0.Final
mvn clean verify -Dtpc.version=4.31.1.Alpha2-SNAPSHOT # (if still being staged)
{code}
or{code}
mvn clean verify -Dtpc.version=4.31.0.Final
mvn clean verify -Dtpc.version=4.31.1.Alpha2 # (if released)
{code}
4. Branch from your existing jbosstools-4.1.x branch into a new *jbosstools-4.1.1.x* (not CR1x) branch;
{code}
git checkout jbosstools-4.1.x
git pull origin jbosstools-4.1.x
git checkout -b jbosstools-4.1.1.x
git push origin jbosstools-4.1.1.x
{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, 7 months
[JBoss JIRA] (TOOLSDOC-426) Add info about JBDS Central TP zip
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-426?page=com.atlassian.jira.plug... ]
Michelle Murray commented on TOOLSDOC-426:
------------------------------------------
For JBDS, it needs to have a JBDS URL, like the update zip. So yes, a zip should be pulled from jbt site and pushed elsewhere.
Info I have about the update site is:
"You can download the update .zip from https://access.redhat.com on the Customer Portal website or https://devstudio.jboss.com/updates/7.0/ on the Red Hat JBoss Developer update website."
Can we duplicate this for central zip? so have it on access.redhat and devstudio.blah?
> Add info about JBDS Central TP zip
> ----------------------------------
>
> Key: TOOLSDOC-426
> URL: https://issues.jboss.org/browse/TOOLSDOC-426
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: User Guide - JBoss Central & JBoss Perspective
> Affects Versions: 4.1.1
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.1.1
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> JBDS Central TP (3rd party) zip enables user to install 3rd party plug-ins while offline.
> How is this implemented?
> * Do users initiate the install download of Central TP from within IDE (like JBoss Central examples offline)?
> * Or do users download the zip from access.redhat (+ other sites) like the update zip?
> * And once users have zip how do they install bits of it? Window > Install New Software and point to zip on system (like install from update zip)?
> Will require a new section in User Guide, Central chapter, probably in customization section.
--
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, 7 months
[JBoss JIRA] (TOOLSDOC-426) Add info about JBDS Central TP zip
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-426?page=com.atlassian.jira.plug... ]
Nick Boldt edited comment on TOOLSDOC-426 at 11/14/13 12:28 AM:
----------------------------------------------------------------
Latest version is here: http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.3...
But we'll have a new version soon as there's more stuff going into JBT 4.1.1 Central soon. See JBDS-2710 for the overall issue listing all the changes / updates / additions.
I guess really we should pull the latest zip off there and push it up onto devstudio.jboss.com for archival and ease-of-use purposes. WDYT?
was (Author: nickboldt):
Latest version is here: http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.3...
But we'll have a new version soon as there's more stuff going into JBT 4.1.1 Central soon. See JBDS-2710 for the overall issue listing all the changes / updates / additions.
> Add info about JBDS Central TP zip
> ----------------------------------
>
> Key: TOOLSDOC-426
> URL: https://issues.jboss.org/browse/TOOLSDOC-426
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: User Guide - JBoss Central & JBoss Perspective
> Affects Versions: 4.1.1
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.1.1
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> JBDS Central TP (3rd party) zip enables user to install 3rd party plug-ins while offline.
> How is this implemented?
> * Do users initiate the install download of Central TP from within IDE (like JBoss Central examples offline)?
> * Or do users download the zip from access.redhat (+ other sites) like the update zip?
> * And once users have zip how do they install bits of it? Window > Install New Software and point to zip on system (like install from update zip)?
> Will require a new section in User Guide, Central chapter, probably in customization section.
--
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, 7 months
[JBoss JIRA] (TOOLSDOC-426) Add info about JBDS Central TP zip
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-426?page=com.atlassian.jira.plug... ]
Nick Boldt commented on TOOLSDOC-426:
-------------------------------------
Latest version is here: http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.3...
But we'll have a new version soon as there's more stuff going into JBT 4.1.1 Central soon. See JBDS-2710 for the overall issue listing all the changes / updates / additions.
> Add info about JBDS Central TP zip
> ----------------------------------
>
> Key: TOOLSDOC-426
> URL: https://issues.jboss.org/browse/TOOLSDOC-426
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: User Guide - JBoss Central & JBoss Perspective
> Affects Versions: 4.1.1
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.1.1
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> JBDS Central TP (3rd party) zip enables user to install 3rd party plug-ins while offline.
> How is this implemented?
> * Do users initiate the install download of Central TP from within IDE (like JBoss Central examples offline)?
> * Or do users download the zip from access.redhat (+ other sites) like the update zip?
> * And once users have zip how do they install bits of it? Window > Install New Software and point to zip on system (like install from update zip)?
> Will require a new section in User Guide, Central chapter, probably in customization section.
--
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, 7 months
[JBoss JIRA] (TOOLSDOC-426) Add info about JBDS Central TP zip
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-426?page=com.atlassian.jira.plug... ]
Michelle Murray commented on TOOLSDOC-426:
------------------------------------------
[~nickboldt], url for the JBDS central tp zip?
> Add info about JBDS Central TP zip
> ----------------------------------
>
> Key: TOOLSDOC-426
> URL: https://issues.jboss.org/browse/TOOLSDOC-426
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: User Guide - JBoss Central & JBoss Perspective
> Affects Versions: 4.1.1
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.1.1
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> JBDS Central TP (3rd party) zip enables user to install 3rd party plug-ins while offline.
> How is this implemented?
> * Do users initiate the install download of Central TP from within IDE (like JBoss Central examples offline)?
> * Or do users download the zip from access.redhat (+ other sites) like the update zip?
> * And once users have zip how do they install bits of it? Window > Install New Software and point to zip on system (like install from update zip)?
> Will require a new section in User Guide, Central chapter, probably in customization section.
--
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, 7 months