December 2018 - jbosstools-issues

[JBoss JIRA] (JBIDE-24442) Import wizard: does nothing if server is not reachable

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-24442?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24442: ------------------------------- Sprint: devex #156 October 2018, devex #157 November 2019, devex #158 November 2018, devex #159 December 2018 (was: devex #156 October 2018, devex #157 November 2019, devex #158 November 2018) > Import wizard: does nothing if server is not reachable > ------------------------------------------------------ > > Key: JBIDE-24442 > URL: https://issues.jboss.org/browse/JBIDE-24442 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.Final > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Priority: Major > Fix For: 4.11.x > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24646) Import application: doesnt check if local branch match

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-24646?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24646: ------------------------------- Sprint: devex #156 October 2018, devex #157 November 2019, devex #158 November 2018, devex #159 December 2018 (was: devex #156 October 2018, devex #157 November 2019, devex #158 November 2018) > Import application: doesnt check if local branch match > ------------------------------------------------------ > > Key: JBIDE-24646 > URL: https://issues.jboss.org/browse/JBIDE-24646 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.0.AM1 > Reporter: Jan Novak > Assignee: Dmitrii Bocharov > Priority: Major > Labels: import_app, openshift_v3 > Fix For: 4.11.x > > > Importing project from Openshift > * use existing repo > * local repo uses different branch than Openshift > * remote branch isnt locally fetched > * import finishes succesfully > * in local repo is *stil checkouted wrong branch*, without any warnings -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26330) Server adapter: shutting down Eclipse won't reset the maven profile that the adapter activated in the project

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26330?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26330: ------------------------------- Sprint: devex #156 October 2018, devex #157 November 2019, devex #158 November 2018, devex #159 December 2018 (was: devex #156 October 2018, devex #157 November 2019, devex #158 November 2018) > Server adapter: shutting down Eclipse won't reset the maven profile that the adapter activated in the project > ------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26330 > URL: https://issues.jboss.org/browse/JBIDE-26330 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.9.0.AM2 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Priority: Major > Fix For: 4.11.x > > > steps: > # EXEC: create the "hello" application in OpenShift as outlined in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello... > # EXEC: import the "hello" maven project into your Eclipse > # EXEC: create a server adapter and start it > # ASSERT: server adapter for project "hello" is *[Started, Synchronized]* > # EXEC: in the Project Explorer: pick Maven > Select Maven Profiles... > # ASSERT: *"openshift"* maven profile is selected > # EXEC: Restart Eclipse > # ASSERT: server adapter for project "hello" is *[Stopped, Republish]* > # EXEC: in the Project Explorer: pick Maven > Select Maven Profiles... > Result: > Project "hello" still has *"openshift"* profile selected > Expected result: > Project "hello" still has *no profile* selected (starting the server adapter selects the "openshift" profile, while stopping it unselects it.) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26160) Server Adapter: erroneously stays in [Debugging] when you kill the pod

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26160?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26160: ------------------------------- Sprint: devex #154 September 2018, devex #155 September 2018, devex #156 October 2018, devex #157 November 2019, devex #158 November 2018, devex #159 December 2018 (was: devex #154 September 2018, devex #155 September 2018, devex #156 October 2018, devex #157 November 2019, devex #158 November 2018) > Server Adapter: erroneously stays in [Debugging] when you kill the pod > ---------------------------------------------------------------------- > > Key: JBIDE-26160 > URL: https://issues.jboss.org/browse/JBIDE-26160 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.6.0.AM3 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Priority: Major > Labels: server_adapter > Fix For: 4.11.x > > > steps: > # EXEC: create an application (via ex. nodejs-mongo-persistent template), import the project and create a server adapter for it > # ASSERT: server adapter is created > # EXEC: start the server adapter in Debugging > # ASSERT: sever adapter is in *[Debugging, Synchronized]* state > # ASSERT: select pod and pick "Port Forwarding..." and it states that the forwarding is started > # EXEC: in Explorer: select the pod for your service and pick "Delete" > # ASSERT: pod gets deleted and recreated > # ASSERT: select pod and pick "Port Forwarding..." and it states that the forwarding is stopped > Result: > The server adapter still says that is is *[Debugging, Synchronized]*, but debugging is not working any more. Debugging doesn't work any more because the port forwarding was stopped. To have it running again you need to restart the port forwarding for the new pod. > Expected result: > Server adapter should get out of debugging and back into normal run mode *[Started, Synchronized]*. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25000) Server adapter: starting into debugging fails initially (succeeds on a latter try)

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-25000?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25000: ------------------------------- Sprint: devex #138 September 2017, devex #152 July 2018, devex #153 August 2018, devex #154 September 2018, devex #155 September 2018, devex #156 October 2018, devex #157 November 2019, devex #158 November 2018, devex #159 December 2018 (was: devex #138 September 2017, devex #152 July 2018, devex #153 August 2018, devex #154 September 2018, devex #155 September 2018, devex #156 October 2018, devex #157 November 2019, devex #158 November 2018) > Server adapter: starting into debugging fails initially (succeeds on a latter try) > ---------------------------------------------------------------------------------- > > Key: JBIDE-25000 > URL: https://issues.jboss.org/browse/JBIDE-25000 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.0.AM2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Major > Labels: openshift_v3, server_adapter > Fix For: 4.11.x > > Attachments: failed-to-connect-v8-vm.png > > > # ASSERT: have an application running in *[OpenShift Online|https://console.starter-us-east-2.openshift.com/]* based on the "nodejs-mongo-persistent" template > # ASSERT: have a server adapter for it > # EXEC/ASSERT: have the adapter started in non-debugging/normal mode > # EXEC: restart the adapter debugging > Result: > !failed-to-connect-v8-vm.png! > {code} > java.io.IOException: Failed to get version > at org.eclipse.wst.jsdt.chromium.internal.v8native.JavascriptVmImpl.newIOException(JavascriptVmImpl.java:114) > at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:132) > at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attach(StandaloneVmImpl.java:79) > at org.eclipse.wst.jsdt.chromium.debug.core.model.JavascriptVmEmbedderFactory$4$1.attach(JavascriptVmEmbedderFactory.java:207) > at org.eclipse.wst.jsdt.chromium.debug.core.model.DebugTargetImpl.attach(DebugTargetImpl.java:74) > at org.eclipse.wst.jsdt.chromium.debug.ui.launcher.LaunchTypeBase.launch(LaunchTypeBase.java:101) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039) > at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) > Caused by: java.util.concurrent.ExecutionException: java.io.IOException: End of stream > at java.util.concurrent.FutureTask.report(FutureTask.java:122) > at java.util.concurrent.FutureTask.get(FutureTask.java:206) > at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:127) > ... 9 more > Caused by: java.io.IOException: End of stream > at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:127) > at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl.perform(Handshaker.java:104) > at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection$ReaderThread.run(SocketConnection.java:158) > {code} > ps. this can be simulated in the CDK, by having everything set and once the pod is up and ithe adapter is in debug, stopping the port forwarding. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26497) For JBIDE 4.11.0.AM1: Prepare for 4.11.0.AM1 / 12.11.0.AM1 [central-update]

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26497?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-26497: ------------------------------------ bump up to parent pom version = 4.11.0.AM1-SNAPSHOT > For JBIDE 4.11.0.AM1: Prepare for 4.11.0.AM1 / 12.11.0.AM1 [central-update] > --------------------------------------------------------------------------- > > Key: JBIDE-26497 > URL: https://issues.jboss.org/browse/JBIDE-26497 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central-update > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.11.0.AM1 > > > For JBIDE 4.11.0.AM1 [central-update]: Please perform the following tasks: > > 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.11.0.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.11.0.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.11.0.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.10.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.10.0.AM1-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.10.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.10.0.AM1-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 central-update task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26497) For JBIDE 4.11.0.AM1: Prepare for 4.11.0.AM1 / 12.11.0.AM1 [central-update]

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26497?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-26497. ------------------------------ Resolution: Done > For JBIDE 4.11.0.AM1: Prepare for 4.11.0.AM1 / 12.11.0.AM1 [central-update] > --------------------------------------------------------------------------- > > Key: JBIDE-26497 > URL: https://issues.jboss.org/browse/JBIDE-26497 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central-update > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.11.0.AM1 > > > For JBIDE 4.11.0.AM1 [central-update]: Please perform the following tasks: > > 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.11.0.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.11.0.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.11.0.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.10.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.10.0.AM1-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.10.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.10.0.AM1-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 central-update task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4749) For JBDS 12.11.0.AM1: Prepare for 4.11.0.AM1 / 12.11.0.AM1 [installer]

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBDS-4749?page=com.atlassian.jira.plugin.... ] Jeff MAURY reassigned JBDS-4749: -------------------------------- Assignee: Jeff MAURY > For JBDS 12.11.0.AM1: Prepare for 4.11.0.AM1 / 12.11.0.AM1 [installer] > ---------------------------------------------------------------------- > > Key: JBDS-4749 > URL: https://issues.jboss.org/browse/JBDS-4749 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: installer > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 12.11.0.AM1 > > > For JBDS 12.11.0.AM1 [installer]: Please perform the following tasks: > > 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.11.0.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.11.0.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.11.0.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.10.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.10.0.AM1-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.10.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.10.0.AM1-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 installer task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4749) For JBDS 12.11.0.AM1: Prepare for 4.11.0.AM1 / 12.11.0.AM1 [installer]

by Jeff MAURY (Jira)

Jeff MAURY created JBDS-4749: -------------------------------- Summary: For JBDS 12.11.0.AM1: Prepare for 4.11.0.AM1 / 12.11.0.AM1 [installer] Key: JBDS-4749 URL: https://issues.jboss.org/browse/JBDS-4749 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Task Components: installer Reporter: Jeff MAURY Fix For: 12.11.0.AM1 For JBDS 12.11.0.AM1 [installer]: Please perform the following tasks: 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.11.0.AM1-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.11.0.AM1-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.11.0.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. {code} mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT {code} 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.10.0.AM1-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.10.0.AM1-SNAPSHOT {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.10.0.AM1-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.10.0.AM1-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 installer task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4749) For JBDS 12.11.0.AM1: Prepare for 4.11.0.AM1 / 12.11.0.AM1 [installer]

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBDS-4749?page=com.atlassian.jira.plugin.... ] Jeff MAURY commented on JBDS-4749: ---------------------------------- bump up to parent pom version = 4.11.0.AM1-SNAPSHOT > For JBDS 12.11.0.AM1: Prepare for 4.11.0.AM1 / 12.11.0.AM1 [installer] > ---------------------------------------------------------------------- > > Key: JBDS-4749 > URL: https://issues.jboss.org/browse/JBDS-4749 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: installer > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 12.11.0.AM1 > > > For JBDS 12.11.0.AM1 [installer]: Please perform the following tasks: > > 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.11.0.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.11.0.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.11.0.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.10.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.10.0.AM1-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.10.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.10.0.AM1-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 installer task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues December 2018