[JBoss JIRA] (JBIDE-23518) For JBIDE 4.4.2.Final: Prepare for 4.4.2.Final / 10.2.0.GA [aerogear-hybrid]
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23518?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-23518:
----------------------------------
Assignee: Gorkem Ercan
> For JBIDE 4.4.2.Final: Prepare for 4.4.2.Final / 10.2.0.GA [aerogear-hybrid]
> ----------------------------------------------------------------------------
>
> Key: JBIDE-23518
> URL: https://issues.jboss.org/browse/JBIDE-23518
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: aerogear-hybrid
> Reporter: Friendly Jira Robot
> Assignee: Gorkem Ercan
> Priority: Blocker
> Labels: task
> Fix For: 4.4.2.Final
>
>
> For JBIDE 4.4.2.Final [aerogear-hybrid]: Please perform the following tasks: 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.2.Final or 10.2.0.GA [Unresolved JIRAs with fixVersion = 4.4.2.Final, 10.2.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...] 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.2.Final-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.2.Final-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: all-tests cordova cordovasim feedhenry pom.xml pom.xml.orig README.md site *{color:orange}4.4.2.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.2.x{color}* branch: {code} git checkout master git pull origin master git checkout -b jbosstools-4.4.2.x git push origin jbosstools-4.4.2.x {code} Now, your root pom will use parent pom version: all-tests cordova cordovasim feedhenry pom.xml pom.xml.orig README.md site *{color:blue}4.4.2.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.2.x{color}* branch, too. 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for aerogear-hybrid task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23520) For JBIDE 4.4.2.Final: Prepare for 4.4.2.Final / 10.2.0.GA [foundation]
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23520?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-23520:
----------------------------------
Assignee: Jeff MAURY
> For JBIDE 4.4.2.Final: Prepare for 4.4.2.Final / 10.2.0.GA [foundation]
> -----------------------------------------------------------------------
>
> Key: JBIDE-23520
> URL: https://issues.jboss.org/browse/JBIDE-23520
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: foundation
> Reporter: Friendly Jira Robot
> Assignee: Jeff MAURY
> Priority: Blocker
> Labels: task
> Fix For: 4.4.2.Final
>
>
> For JBIDE 4.4.2.Final [foundation]: Please perform the following tasks: 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.2.Final or 10.2.0.GA [Unresolved JIRAs with fixVersion = 4.4.2.Final, 10.2.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...] 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.2.Final-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.2.Final-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: all-tests common foundation pom.xml pom.xml.orig README.md runtime site stacks tests usage *{color:orange}4.4.2.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.2.x{color}* branch: {code} git checkout master git pull origin master git checkout -b jbosstools-4.4.2.x git push origin jbosstools-4.4.2.x {code} Now, your root pom will use parent pom version: all-tests common foundation pom.xml pom.xml.orig README.md runtime site stacks tests usage *{color:blue}4.4.2.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.2.x{color}* branch, too. 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 4b. Ensure you've *run your tests using the latest *maximum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for foundation task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23521) For JBIDE 4.4.2.Final: Prepare for 4.4.2.Final / 10.2.0.GA [browsersim]
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23521?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-23521:
----------------------------------
Assignee: Ilya Buziuk
> For JBIDE 4.4.2.Final: Prepare for 4.4.2.Final / 10.2.0.GA [browsersim]
> -----------------------------------------------------------------------
>
> Key: JBIDE-23521
> URL: https://issues.jboss.org/browse/JBIDE-23521
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: browsersim
> Reporter: Friendly Jira Robot
> Assignee: Ilya Buziuk
> Priority: Blocker
> Labels: task
> Fix For: 4.4.2.Final
>
>
> For JBIDE 4.4.2.Final [browsersim]: Please perform the following tasks: 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.2.Final or 10.2.0.GA [Unresolved JIRAs with fixVersion = 4.4.2.Final, 10.2.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...] 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.2.Final-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.2.Final-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: features plugins pom.xml pom.xml.orig products README.md site tests *{color:orange}4.4.2.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.2.x{color}* branch: {code} git checkout master git pull origin master git checkout -b jbosstools-4.4.2.x git push origin jbosstools-4.4.2.x {code} Now, your root pom will use parent pom version: features plugins pom.xml pom.xml.orig products README.md site tests *{color:blue}4.4.2.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.2.x{color}* branch, too. 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 4b. Ensure you've *run your tests using the latest *maximum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for browsersim task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23524) For JBIDE 4.4.2.Final: Prepare for 4.4.2.Final / 10.2.0.GA [freemarker]
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23524?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-23524:
----------------------------------
Assignee: Daniel Dekany
> For JBIDE 4.4.2.Final: Prepare for 4.4.2.Final / 10.2.0.GA [freemarker]
> -----------------------------------------------------------------------
>
> Key: JBIDE-23524
> URL: https://issues.jboss.org/browse/JBIDE-23524
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: freemarker
> Reporter: Friendly Jira Robot
> Assignee: Daniel Dekany
> Priority: Blocker
> Labels: task
> Fix For: 4.4.2.Final
>
>
> For JBIDE 4.4.2.Final [freemarker]: Please perform the following tasks: 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.2.Final or 10.2.0.GA [Unresolved JIRAs with fixVersion = 4.4.2.Final, 10.2.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...] 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.2.Final-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.2.Final-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: features plugins pom.xml pom.xml.orig README.md site tests *{color:orange}4.4.2.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.2.x{color}* branch: {code} git checkout master git pull origin master git checkout -b jbosstools-4.4.2.x git push origin jbosstools-4.4.2.x {code} Now, your root pom will use parent pom version: features plugins pom.xml pom.xml.orig README.md site tests *{color:blue}4.4.2.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.2.x{color}* branch, too. 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 4b. Ensure you've *run your tests using the latest *maximum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for freemarker task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23522) For JBIDE 4.4.2.Final: Prepare for 4.4.2.Final / 10.2.0.GA [central]
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23522?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-23522:
----------------------------------
Assignee: Fred Bricon
> For JBIDE 4.4.2.Final: Prepare for 4.4.2.Final / 10.2.0.GA [central]
> --------------------------------------------------------------------
>
> Key: JBIDE-23522
> URL: https://issues.jboss.org/browse/JBIDE-23522
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: central
> Reporter: Friendly Jira Robot
> Assignee: Fred Bricon
> Priority: Blocker
> Labels: task
> Fix For: 4.4.2.Final
>
>
> For JBIDE 4.4.2.Final [central]: Please perform the following tasks: 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.2.Final or 10.2.0.GA [Unresolved JIRAs with fixVersion = 4.4.2.Final, 10.2.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...] 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.2.Final-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.2.Final-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: all-tests central discovery examples maven pom.xml pom.xml.orig README.md site *{color:orange}4.4.2.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.2.x{color}* branch: {code} git checkout master git pull origin master git checkout -b jbosstools-4.4.2.x git push origin jbosstools-4.4.2.x {code} Now, your root pom will use parent pom version: all-tests central discovery examples maven pom.xml pom.xml.orig README.md site *{color:blue}4.4.2.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.2.x{color}* branch, too. 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for central task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23527) For JBIDE 4.4.2.Final: Prepare for 4.4.2.Final / 10.2.0.GA [jst]
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23527?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-23527:
----------------------------------
Assignee: Alexey Kazakov
> For JBIDE 4.4.2.Final: Prepare for 4.4.2.Final / 10.2.0.GA [jst]
> ----------------------------------------------------------------
>
> Key: JBIDE-23527
> URL: https://issues.jboss.org/browse/JBIDE-23527
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: jst
> Reporter: Friendly Jira Robot
> Assignee: Alexey Kazakov
> Priority: Blocker
> Labels: task
> Fix For: 4.4.2.Final
>
>
> For JBIDE 4.4.2.Final [jst]: Please perform the following tasks: 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.2.Final or 10.2.0.GA [Unresolved JIRAs with fixVersion = 4.4.2.Final, 10.2.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...] 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.2.Final-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.2.Final-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: docs features plugins pom.xml pom.xml.orig README.md site tests *{color:orange}4.4.2.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.2.x{color}* branch: {code} git checkout master git pull origin master git checkout -b jbosstools-4.4.2.x git push origin jbosstools-4.4.2.x {code} Now, your root pom will use parent pom version: docs features plugins pom.xml pom.xml.orig README.md site tests *{color:blue}4.4.2.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.2.x{color}* branch, too. 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 4b. Ensure you've *run your tests using the latest *maximum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
> [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 was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23526) For JBIDE 4.4.2.Final: Prepare for 4.4.2.Final / 10.2.0.GA [jsf]
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23526?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-23526:
----------------------------------
Assignee: Alexey Kazakov
> For JBIDE 4.4.2.Final: Prepare for 4.4.2.Final / 10.2.0.GA [jsf]
> ----------------------------------------------------------------
>
> Key: JBIDE-23526
> URL: https://issues.jboss.org/browse/JBIDE-23526
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: jsf
> Reporter: Friendly Jira Robot
> Assignee: Alexey Kazakov
> Priority: Blocker
> Labels: task
> Fix For: 4.4.2.Final
>
>
> For JBIDE 4.4.2.Final [jsf]: Please perform the following tasks: 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.2.Final or 10.2.0.GA [Unresolved JIRAs with fixVersion = 4.4.2.Final, 10.2.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...] 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.2.Final-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.2.Final-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: all-tests batch cdi jsf pom.xml pom.xml.orig README.md seam site *{color:orange}4.4.2.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.2.x{color}* branch: {code} git checkout master git pull origin master git checkout -b jbosstools-4.4.2.x git push origin jbosstools-4.4.2.x {code} Now, your root pom will use parent pom version: all-tests batch cdi jsf pom.xml pom.xml.orig README.md seam site *{color:blue}4.4.2.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.2.x{color}* branch, too. 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for jsf task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23525) For JBIDE 4.4.2.Final: Prepare for 4.4.2.Final / 10.2.0.GA [hibernate]
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23525?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-23525:
----------------------------------
Assignee: Koen Aers
> For JBIDE 4.4.2.Final: Prepare for 4.4.2.Final / 10.2.0.GA [hibernate]
> ----------------------------------------------------------------------
>
> Key: JBIDE-23525
> URL: https://issues.jboss.org/browse/JBIDE-23525
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: hibernate
> Reporter: Friendly Jira Robot
> Assignee: Koen Aers
> Priority: Blocker
> Labels: task
> Fix For: 4.4.2.Final
>
>
> For JBIDE 4.4.2.Final [hibernate]: Please perform the following tasks: 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.2.Final or 10.2.0.GA [Unresolved JIRAs with fixVersion = 4.4.2.Final, 10.2.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...] 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.2.Final-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.2.Final-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: dependencies.psf docs features plugins pom.xml pom.xml.orig README.md sampleprojects site tests *{color:orange}4.4.2.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.2.x{color}* branch: {code} git checkout master git pull origin master git checkout -b jbosstools-4.4.2.x git push origin jbosstools-4.4.2.x {code} Now, your root pom will use parent pom version: dependencies.psf docs features plugins pom.xml pom.xml.orig README.md sampleprojects site tests *{color:blue}4.4.2.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.2.x{color}* branch, too. 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 4b. Ensure you've *run your tests using the latest *maximum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for hibernate task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23529) For JBIDE 4.4.2.Final: Prepare for 4.4.2.Final / 10.2.0.GA [openshift]
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23529?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-23529:
----------------------------------
Assignee: Jeff MAURY
> For JBIDE 4.4.2.Final: Prepare for 4.4.2.Final / 10.2.0.GA [openshift]
> ----------------------------------------------------------------------
>
> Key: JBIDE-23529
> URL: https://issues.jboss.org/browse/JBIDE-23529
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: openshift
> Reporter: Friendly Jira Robot
> Assignee: Jeff MAURY
> Priority: Blocker
> Labels: task
> Fix For: 4.4.2.Final
>
>
> For JBIDE 4.4.2.Final [openshift]: Please perform the following tasks: 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.2.Final or 10.2.0.GA [Unresolved JIRAs with fixVersion = 4.4.2.Final, 10.2.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...] 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.2.Final-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.2.Final-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: features plugins pom.xml pom.xml.orig README.md site tests *{color:orange}4.4.2.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.2.x{color}* branch: {code} git checkout master git pull origin master git checkout -b jbosstools-4.4.2.x git push origin jbosstools-4.4.2.x {code} Now, your root pom will use parent pom version: features plugins pom.xml pom.xml.orig README.md site tests *{color:blue}4.4.2.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.2.x{color}* branch, too. 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 4b. Ensure you've *run your tests using the latest *maximum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for openshift task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23530) For JBIDE 4.4.2.Final: Prepare for 4.4.2.Final / 10.2.0.GA [server]
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23530?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-23530:
----------------------------------
Assignee: Rob Stryker
> For JBIDE 4.4.2.Final: Prepare for 4.4.2.Final / 10.2.0.GA [server]
> -------------------------------------------------------------------
>
> Key: JBIDE-23530
> URL: https://issues.jboss.org/browse/JBIDE-23530
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: server
> Reporter: Friendly Jira Robot
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: task
> Fix For: 4.4.2.Final
>
>
> For JBIDE 4.4.2.Final [server]: Please perform the following tasks: 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.2.Final or 10.2.0.GA [Unresolved JIRAs with fixVersion = 4.4.2.Final, 10.2.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...] 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.2.Final-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.2.Final-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: all-tests archives as jmx pom.xml pom.xml.orig README.md site wtp *{color:orange}4.4.2.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.2.x{color}* branch: {code} git checkout master git pull origin master git checkout -b jbosstools-4.4.2.x git push origin jbosstools-4.4.2.x {code} Now, your root pom will use parent pom version: all-tests archives as jmx pom.xml pom.xml.orig README.md site wtp *{color:blue}4.4.2.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.2.x{color}* branch, too. 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
> [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 was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months