[JBoss JIRA] (JBIDE-24328) For JBIDE 4.4.4.Final: Prepare for 4.4.4.Final / 10.4.0.GA [browsersim]
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24328?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-24328:
------------------------------------
bump up to parent pom version = 4.4.4.Final-SNAPSHOT
> For JBIDE 4.4.4.Final: Prepare for 4.4.4.Final / 10.4.0.GA [browsersim]
> -----------------------------------------------------------------------
>
> Key: JBIDE-24328
> URL: https://issues.jboss.org/browse/JBIDE-24328
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: browsersim
> Reporter: Jeff MAURY
> Assignee: Ilya Buziuk
> Priority: Blocker
> Labels: task
> Fix For: 4.4.4.Final
>
>
> For JBIDE 4.4.4.Final [browsersim]: Please perform the following tasks:
>
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.4.Final or 10.4.0.GA
>
> [Unresolved JIRAs with fixVersion = 4.4.4.Final, 10.4.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.4.Final-SNAPSHOT{color}*:
>
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.4.4.Final-SNAPSHOT</version>
> </parent>
> {code}
>
> Now, your root pom will use parent pom version:
>
> * *{color:orange}4.4.4.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.x{color}* branch:
>
> {code}
> git checkout master;
> git pull origin master;
> git checkout -b jbosstools-4.4.x;
> git push origin jbosstools-4.4.x
> {code}
>
> Now, your root pom will use parent pom version:
>
> * *{color:blue}4.4.4.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.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.63.0.Final-SNAPSHOT
>
> {code}
> mvn clean verify -Dtpc.version=4.63.0.Final-SNAPSHOT
> {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)
8 years, 11 months
[JBoss JIRA] (JBIDE-24328) For JBIDE 4.4.4.Final: Prepare for 4.4.4.Final / 10.4.0.GA [browsersim]
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24328?page=com.atlassian.jira.plugi... ]
Jeff MAURY closed JBIDE-24328.
------------------------------
Resolution: Done
> For JBIDE 4.4.4.Final: Prepare for 4.4.4.Final / 10.4.0.GA [browsersim]
> -----------------------------------------------------------------------
>
> Key: JBIDE-24328
> URL: https://issues.jboss.org/browse/JBIDE-24328
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: browsersim
> Reporter: Jeff MAURY
> Assignee: Ilya Buziuk
> Priority: Blocker
> Labels: task
> Fix For: 4.4.4.Final
>
>
> For JBIDE 4.4.4.Final [browsersim]: Please perform the following tasks:
>
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.4.Final or 10.4.0.GA
>
> [Unresolved JIRAs with fixVersion = 4.4.4.Final, 10.4.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.4.Final-SNAPSHOT{color}*:
>
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.4.4.Final-SNAPSHOT</version>
> </parent>
> {code}
>
> Now, your root pom will use parent pom version:
>
> * *{color:orange}4.4.4.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.x{color}* branch:
>
> {code}
> git checkout master;
> git pull origin master;
> git checkout -b jbosstools-4.4.x;
> git push origin jbosstools-4.4.x
> {code}
>
> Now, your root pom will use parent pom version:
>
> * *{color:blue}4.4.4.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.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.63.0.Final-SNAPSHOT
>
> {code}
> mvn clean verify -Dtpc.version=4.63.0.Final-SNAPSHOT
> {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)
8 years, 11 months
[JBoss JIRA] (JBIDE-24325) For JBIDE 4.4.4.Final: Prepare for 4.4.4.Final / 10.4.0.GA [aerogear-hybrid]
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24325?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-24325:
------------------------------------
bump up to parent pom version = 4.4.4.Final-SNAPSHOT
> For JBIDE 4.4.4.Final: Prepare for 4.4.4.Final / 10.4.0.GA [aerogear-hybrid]
> ----------------------------------------------------------------------------
>
> Key: JBIDE-24325
> URL: https://issues.jboss.org/browse/JBIDE-24325
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: aerogear-hybrid
> Reporter: Jeff MAURY
> Assignee: Gorkem Ercan
> Priority: Blocker
> Labels: task
> Fix For: 4.4.4.Final
>
>
> For JBIDE 4.4.4.Final [aerogear-hybrid]: Please perform the following tasks:
>
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.4.Final or 10.4.0.GA
>
> [Unresolved JIRAs with fixVersion = 4.4.4.Final, 10.4.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.4.Final-SNAPSHOT{color}*:
>
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.4.4.Final-SNAPSHOT</version>
> </parent>
> {code}
>
> Now, your root pom will use parent pom version:
>
> * *{color:orange}4.4.4.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.x{color}* branch:
>
> {code}
> git checkout master;
> git pull origin master;
> git checkout -b jbosstools-4.4.x;
> git push origin jbosstools-4.4.x
> {code}
>
> Now, your root pom will use parent pom version:
>
> * *{color:blue}4.4.4.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.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.63.0.Final-SNAPSHOT
>
> {code}
> mvn clean verify -Dtpc.version=4.63.0.Final-SNAPSHOT
> {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)
8 years, 11 months
[JBoss JIRA] (JBIDE-24325) For JBIDE 4.4.4.Final: Prepare for 4.4.4.Final / 10.4.0.GA [aerogear-hybrid]
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24325?page=com.atlassian.jira.plugi... ]
Jeff MAURY closed JBIDE-24325.
------------------------------
Resolution: Done
> For JBIDE 4.4.4.Final: Prepare for 4.4.4.Final / 10.4.0.GA [aerogear-hybrid]
> ----------------------------------------------------------------------------
>
> Key: JBIDE-24325
> URL: https://issues.jboss.org/browse/JBIDE-24325
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: aerogear-hybrid
> Reporter: Jeff MAURY
> Assignee: Gorkem Ercan
> Priority: Blocker
> Labels: task
> Fix For: 4.4.4.Final
>
>
> For JBIDE 4.4.4.Final [aerogear-hybrid]: Please perform the following tasks:
>
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.4.Final or 10.4.0.GA
>
> [Unresolved JIRAs with fixVersion = 4.4.4.Final, 10.4.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.4.Final-SNAPSHOT{color}*:
>
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.4.4.Final-SNAPSHOT</version>
> </parent>
> {code}
>
> Now, your root pom will use parent pom version:
>
> * *{color:orange}4.4.4.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.x{color}* branch:
>
> {code}
> git checkout master;
> git pull origin master;
> git checkout -b jbosstools-4.4.x;
> git push origin jbosstools-4.4.x
> {code}
>
> Now, your root pom will use parent pom version:
>
> * *{color:blue}4.4.4.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.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.63.0.Final-SNAPSHOT
>
> {code}
> mvn clean verify -Dtpc.version=4.63.0.Final-SNAPSHOT
> {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)
8 years, 11 months
[JBoss JIRA] (JBIDE-24340) CDK3 tools works behind proxy - Test case
by Ondrej Dockal (JIRA)
Ondrej Dockal created JBIDE-24340:
-------------------------------------
Summary: CDK3 tools works behind proxy - Test case
Key: JBIDE-24340
URL: https://issues.jboss.org/browse/JBIDE-24340
Project: Tools (JBoss Tools)
Issue Type: Task
Components: cdk, docker, openshift
Affects Versions: 4.4.4.Final
Environment: Linux (Fedora), Mac OS, Windows
Reporter: Ondrej Dockal
Assignee: Ondrej Dockal
Priority: Critical
Fix For: 4.4.4.Final
It is still impossible to test CDK 3 on central-ci and so, it is willing to test CDK 3 tools operated from devstudio via usage of proxy system settings on local machines.
Steps to follow:
1. Setup local firewall/network rules to simulate that machine resides in restricted network and requires proxy to utilize CDK3 features. (script)
2. Download/install devstudio
3. Download CDK3 minishift binary and prepare the environemnt (run minishift setup-cdk)
4. Set env. variable MINISHIFT_HTTP(S)_PROXY
5. Start devstudio, add new Container Development Environement server
6. Start server adapter
7. Assert that cdk tools are working properly (cdk started, openshift can be operated, docker can pull image, etc...)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24339) For JBIDE 4.4.4.Final: Prepare for 4.4.4.Final / 10.4.0.GA [integration-tests]
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24339?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-24339:
----------------------------------
Assignee: Pavol Srna
> For JBIDE 4.4.4.Final: Prepare for 4.4.4.Final / 10.4.0.GA [integration-tests]
> ------------------------------------------------------------------------------
>
> Key: JBIDE-24339
> URL: https://issues.jboss.org/browse/JBIDE-24339
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: integration-tests
> Reporter: Jeff MAURY
> Assignee: Pavol Srna
> Priority: Blocker
> Labels: task
> Fix For: 4.4.4.Final
>
>
> For JBIDE 4.4.4.Final [integration-tests]: Please perform the following tasks:
>
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.4.Final or 10.4.0.GA
>
> [Unresolved JIRAs with fixVersion = 4.4.4.Final, 10.4.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.4.Final-SNAPSHOT{color}*:
>
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.4.4.Final-SNAPSHOT</version>
> </parent>
> {code}
>
> Now, your root pom will use parent pom version:
>
> * *{color:orange}4.4.4.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.x{color}* branch:
>
> {code}
> git checkout master;
> git pull origin master;
> git checkout -b jbosstools-4.4.x;
> git push origin jbosstools-4.4.x
> {code}
>
> Now, your root pom will use parent pom version:
>
> * *{color:blue}4.4.4.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.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.63.0.Final-SNAPSHOT
>
> {code}
> mvn clean verify -Dtpc.version=4.63.0.Final-SNAPSHOT
> {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 integration-tests 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)
8 years, 11 months
[JBoss JIRA] (JBIDE-24336) For JBIDE 4.4.4.Final: Prepare for 4.4.4.Final / 10.4.0.GA [server]
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24336?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-24336:
----------------------------------
Assignee: Rob Stryker
> For JBIDE 4.4.4.Final: Prepare for 4.4.4.Final / 10.4.0.GA [server]
> -------------------------------------------------------------------
>
> Key: JBIDE-24336
> URL: https://issues.jboss.org/browse/JBIDE-24336
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: server
> Reporter: Jeff MAURY
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: task
> Fix For: 4.4.4.Final
>
>
> For JBIDE 4.4.4.Final [server]: Please perform the following tasks:
>
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.4.Final or 10.4.0.GA
>
> [Unresolved JIRAs with fixVersion = 4.4.4.Final, 10.4.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.4.Final-SNAPSHOT{color}*:
>
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.4.4.Final-SNAPSHOT</version>
> </parent>
> {code}
>
> Now, your root pom will use parent pom version:
>
> * *{color:orange}4.4.4.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.x{color}* branch:
>
> {code}
> git checkout master;
> git pull origin master;
> git checkout -b jbosstools-4.4.x;
> git push origin jbosstools-4.4.x
> {code}
>
> Now, your root pom will use parent pom version:
>
> * *{color:blue}4.4.4.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.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.63.0.Final-SNAPSHOT
>
> {code}
> mvn clean verify -Dtpc.version=4.63.0.Final-SNAPSHOT
> {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)
8 years, 11 months
[JBoss JIRA] (JBIDE-24338) For JBIDE 4.4.4.Final: Prepare for 4.4.4.Final / 10.4.0.GA [webservices]
by Jeff MAURY (JIRA)
Jeff MAURY created JBIDE-24338:
----------------------------------
Summary: For JBIDE 4.4.4.Final: Prepare for 4.4.4.Final / 10.4.0.GA [webservices]
Key: JBIDE-24338
URL: https://issues.jboss.org/browse/JBIDE-24338
Project: Tools (JBoss Tools)
Issue Type: Task
Components: webservices
Reporter: Jeff MAURY
Priority: Blocker
Fix For: 4.4.4.Final
For JBIDE 4.4.4.Final [webservices]: Please perform the following tasks:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.4.Final or 10.4.0.GA
[Unresolved JIRAs with fixVersion = 4.4.4.Final, 10.4.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.4.Final-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.4.4.Final-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:orange}4.4.4.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.x{color}* branch:
{code}
git checkout master;
git pull origin master;
git checkout -b jbosstools-4.4.x;
git push origin jbosstools-4.4.x
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.4.4.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.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.63.0.Final-SNAPSHOT
{code}
mvn clean verify -Dtpc.version=4.63.0.Final-SNAPSHOT
{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 webservices 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)
8 years, 11 months
[JBoss JIRA] (JBIDE-24335) For JBIDE 4.4.4.Final: Prepare for 4.4.4.Final / 10.4.0.GA [openshift]
by Jeff MAURY (JIRA)
Jeff MAURY created JBIDE-24335:
----------------------------------
Summary: For JBIDE 4.4.4.Final: Prepare for 4.4.4.Final / 10.4.0.GA [openshift]
Key: JBIDE-24335
URL: https://issues.jboss.org/browse/JBIDE-24335
Project: Tools (JBoss Tools)
Issue Type: Task
Components: openshift
Reporter: Jeff MAURY
Priority: Blocker
Fix For: 4.4.4.Final
For JBIDE 4.4.4.Final [openshift]: Please perform the following tasks:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.4.Final or 10.4.0.GA
[Unresolved JIRAs with fixVersion = 4.4.4.Final, 10.4.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.4.Final-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.4.4.Final-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:orange}4.4.4.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.x{color}* branch:
{code}
git checkout master;
git pull origin master;
git checkout -b jbosstools-4.4.x;
git push origin jbosstools-4.4.x
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.4.4.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.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.63.0.Final-SNAPSHOT
{code}
mvn clean verify -Dtpc.version=4.63.0.Final-SNAPSHOT
{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)
8 years, 11 months