[JBoss JIRA] (JBDS-4377) installer jar does not contain both the patched and unpatched version of org.eclipse.wst.common.modulecore
by Nick Boldt (JIRA)
Nick Boldt created JBDS-4377:
--------------------------------
Summary: installer jar does not contain both the patched and unpatched version of org.eclipse.wst.common.modulecore
Key: JBDS-4377
URL: https://issues.jboss.org/browse/JBDS-4377
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Feature Request
Reporter: Nick Boldt
Denis reports a problem using the installer jar in automated mode (using .xml script).
Works fine when run `java -jar *installer*.jar` and `echo 1 | java -jar *installer*.jar -console` but fails when run against an xml install script.
Seems to be caused by the fact that the installer only contains the patched version of org.eclipse.wst.common.modulecore 1.2.501, and not the 1.2.500 version that's in the TP as well.
So we need to figure out how to include BOTH versions in the installer jar.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBDS-4377) installer jar does not contain both the patched and unpatched version of org.eclipse.wst.common.modulecore
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4377?page=com.atlassian.jira.plugin.... ]
Nick Boldt reassigned JBDS-4377:
--------------------------------
Assignee: Nick Boldt
> installer jar does not contain both the patched and unpatched version of org.eclipse.wst.common.modulecore
> ----------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4377
> URL: https://issues.jboss.org/browse/JBDS-4377
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Affects Versions: 10.4.0.AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.4.0.GA
>
>
> Denis reports a problem using the installer jar in automated mode (using .xml script).
> Works fine when run `java -jar *installer*.jar` and `echo 1 | java -jar *installer*.jar -console` but fails when run against an xml install script.
> Seems to be caused by the fact that the installer only contains the patched version of org.eclipse.wst.common.modulecore 1.2.501, and not the 1.2.500 version that's in the TP as well.
> So we need to figure out how to include BOTH versions in the installer jar.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBDS-4377) installer jar does not contain both the patched and unpatched version of org.eclipse.wst.common.modulecore
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4377?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4377:
-----------------------------
Affects Version/s: 10.4.0.AM3
> installer jar does not contain both the patched and unpatched version of org.eclipse.wst.common.modulecore
> ----------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4377
> URL: https://issues.jboss.org/browse/JBDS-4377
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Affects Versions: 10.4.0.AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.4.0.GA
>
>
> Denis reports a problem using the installer jar in automated mode (using .xml script).
> Works fine when run `java -jar *installer*.jar` and `echo 1 | java -jar *installer*.jar -console` but fails when run against an xml install script.
> Seems to be caused by the fact that the installer only contains the patched version of org.eclipse.wst.common.modulecore 1.2.501, and not the 1.2.500 version that's in the TP as well.
> So we need to figure out how to include BOTH versions in the installer jar.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-21065) Server host name address should not be defaulted during server adapter creation
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21065?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-21065.
---------------------------------
Fix Version/s: 4.4.4.Final
(was: 4.4.4.AM3)
Resolution: Done
I think this is fixed finally.
> Server host name address should not be defaulted during server adapter creation
> -------------------------------------------------------------------------------
>
> Key: JBIDE-21065
> URL: https://issues.jboss.org/browse/JBIDE-21065
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server, upstream
> Affects Versions: 4.3.0.Final
> Reporter: Xavier Coulon
> Assignee: Rob Stryker
> Fix For: 4.4.4.Final
>
>
> I've noticed that when I create a server adapter and I give it an IP address as the hostname, the hostname remains the default value, ie, {{localhost}}.
> This is annoying in the case where I want to connect to a VM running on my own host (eg, a VM running Docker). In this particular case, I set the hostname at something like {{192.168.99.100}} but it is reverted as {{localhost}} which gives {{127.0.0.1}} as the primary IP address. As a consequence, the server adapter fails to connect to the server since it uses the wrong IP address.
> Note that the host name can be changed for good in the Server Configuration Editor _after_ its creation.
--
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 commented on JBIDE-24339:
------------------------------------
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 [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-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 closed JBIDE-24339.
------------------------------
Resolution: Done
> 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-24306) Cannot connect to JMX through OpenShift Server adapter to a FIS project
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24306?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-24306:
-------------------------------------
https://github.com/jbosstools/jbosstools-openshift/pull/1480
> Cannot connect to JMX through OpenShift Server adapter to a FIS project
> -----------------------------------------------------------------------
>
> Key: JBIDE-24306
> URL: https://issues.jboss.org/browse/JBIDE-24306
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.4.AM3
> Reporter: Aurélien Pupier
> Assignee: Rob Stryker
> Fix For: 4.4.4.Final
>
> Attachments: image-2017-04-25-14-48-51-427.png, screenshot-1.png
>
>
> !image-2017-04-25-14-48-51-427.png|thumbnail!
> in log:
> {noformat}
> eclipse.buildId=10.4.0.AM3-v20170406-1058-B390
> java.version=1.8.0_112
> java.vendor=Oracle Corporation
> BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -data file:/C:/ws-devsuite-1.4.0-170425/ -os win32 -ws win32 -arch x86_64 -product com.jboss.devstudio.core.product
> org.jboss.tools.jmx.core
> Error
> Tue Apr 25 14:47:14 CEST 2017
> An error occurred while opening the connection.
> java.io.IOException: org.jolokia.client.exception.J4pException: IO-Error while contacting the server: org.apache.http.client.ClientProtocolException: URI does not specify a valid host name: https:/api/v1/namespaces/test/pods/https:camel-ose-springboot-xml-1-oblwo:8778/proxy/jolokia/read/java.lang:type=Memory/HeapMemoryUsage
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:324)
> at org.jboss.tools.openshift.core.server.OpenshiftJMXConnectionProvider$1.verifyServerReachable(OpenshiftJMXConnectionProvider.java:80)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:113)
> at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29)
> at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: org.jolokia.client.exception.J4pException: IO-Error while contacting the server: org.apache.http.client.ClientProtocolException: URI does not specify a valid host name: https:/api/v1/namespaces/test/pods/https:camel-ose-springboot-xml-1-oblwo:8778/proxy/jolokia/read/java.lang:type=Memory/HeapMemoryUsage
> at org.jolokia.client.J4pClient.mapException(J4pClient.java:333)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:198)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:168)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:117)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:311)
> ... 5 more
> Caused by: org.apache.http.client.ClientProtocolException: URI does not specify a valid host name: https:/api/v1/namespaces/test/pods/https:camel-ose-springboot-xml-1-oblwo:8778/proxy/jolokia/read/java.lang:type=Memory/HeapMemoryUsage
> at org.apache.http.impl.client.CloseableHttpClient.determineTarget(CloseableHttpClient.java:94)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:107)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:55)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:190)
> ... 8 more
> {noformat}
--
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 commented on JBIDE-24336:
------------------------------------
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 [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-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 closed JBIDE-24336.
------------------------------
Resolution: Done
> 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-24337) For JBIDE 4.4.4.Final: Prepare for 4.4.4.Final / 10.4.0.GA [visual-page-editor-core]
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24337?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-24337:
------------------------------------
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 [visual-page-editor-core]
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-24337
> URL: https://issues.jboss.org/browse/JBIDE-24337
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: visual-page-editor-core
> Reporter: Jeff MAURY
> Assignee: Ilya Buziuk
> Priority: Blocker
> Labels: task
> Fix For: 4.4.4.Final
>
>
> For JBIDE 4.4.4.Final [visual-page-editor-core]: 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 visual-page-editor-core 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