January 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4664) Update copyright year in DevStudio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4664?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4664: ---------------------------------- New splash: https://github.com/jbdevstudio/jbdevstudio-product/commit/8621ee6677ff3b6... Building: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... >=1892 > Update copyright year in DevStudio > ---------------------------------- > > Key: JBDS-4664 > URL: https://issues.jboss.org/browse/JBDS-4664 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: legal, ui/branding > Affects Versions: 11.2.0.AM3 > Environment: Red Hat JBoss Developer Studio > Version: 11.2.0.AM3 > Reporter: Josef Kopriva > Assignee: Nick Boldt > Fix For: 11.3.0.AM1 > > Attachments: splash.bmp > > > Update copyright year on splash screen and in about dialog of devstudio to 2018(it is now 2017). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4664) Update copyright year in DevStudio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4664?page=com.atlassian.jira.plugin.... ] Nick Boldt resolved JBDS-4664. ------------------------------ Resolution: Done > Update copyright year in DevStudio > ---------------------------------- > > Key: JBDS-4664 > URL: https://issues.jboss.org/browse/JBDS-4664 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: legal, ui/branding > Affects Versions: 11.2.0.AM3 > Environment: Red Hat JBoss Developer Studio > Version: 11.2.0.AM3 > Reporter: Josef Kopriva > Assignee: Nick Boldt > Fix For: 11.3.0.AM1 > > Attachments: splash.bmp > > > Update copyright year on splash screen and in about dialog of devstudio to 2018(it is now 2017). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25611) Server adapter: timeouts when starting into "Debug" on OpenShift Online

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25611?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25611: ------------------------------------- Attachment: port-missing.png > Server adapter: timeouts when starting into "Debug" on OpenShift Online > ----------------------------------------------------------------------- > > Key: JBIDE-25611 > URL: https://issues.jboss.org/browse/JBIDE-25611 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.5.3.AM1 > > Attachments: error-waiting-for-new-pod.png, port-missing.png > > > # ASSERT: have an account on OpenShift Online > # EXEC: create a new application via template nodejs-mongo-persistent > # EXEC: have the project imported into the workspace and the server adapter for it created > # ASSERT: you have a new server adapter for your app in state [stopped] > # EXEC: start the adapter into "Debug" > Result: > The adapter takes a lot of time to start but wont succeed eventually. You get the following error dialog: > !error-waiting-for-new-pod.png! > In the Eclipse log you'll find the following: > {code} > org.eclipse.core.runtime.CoreException: Failed to detect new deployed Pod for nodejs-mongo-persistent > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.waitFor(OpenShiftDebugMode.java:403) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.waitForNewPod(OpenShiftDebugMode.java:395) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.getPod(OpenShiftDebugMode.java:226) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:170) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:100) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52) > 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.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25662) For JBIDE 4.5.3.AM1: Prepare for 4.5.3.AM1 / 11.3.0.AM1 [updatesite]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25662?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-25662. ------------------------------ Resolution: Done > For JBIDE 4.5.3.AM1: Prepare for 4.5.3.AM1 / 11.3.0.AM1 [updatesite] > -------------------------------------------------------------------- > > Key: JBIDE-25662 > URL: https://issues.jboss.org/browse/JBIDE-25662 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: updatesite > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.5.3.AM1 > > > For JBIDE 4.5.3.AM1 [updatesite]: 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.5.3.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.3.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.3.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.71.1.Final > > {code} > mvn clean verify -Dtpc.version=4.71.1.Final > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.72.0.Final > > {code} > mvn clean verify -Dtpc.version=4.72.0.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 updatesite task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25662) For JBIDE 4.5.3.AM1: Prepare for 4.5.3.AM1 / 11.3.0.AM1 [updatesite]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25662?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25662: ------------------------------------ bump up to parent pom version = 4.5.3.AM1-SNAPSHOT > For JBIDE 4.5.3.AM1: Prepare for 4.5.3.AM1 / 11.3.0.AM1 [updatesite] > -------------------------------------------------------------------- > > Key: JBIDE-25662 > URL: https://issues.jboss.org/browse/JBIDE-25662 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: updatesite > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.5.3.AM1 > > > For JBIDE 4.5.3.AM1 [updatesite]: 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.5.3.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.3.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.3.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.71.1.Final > > {code} > mvn clean verify -Dtpc.version=4.71.1.Final > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.72.0.Final > > {code} > mvn clean verify -Dtpc.version=4.72.0.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 updatesite task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25663) For JBIDE 4.5.3.AM1: Prepare for 4.5.3.AM1 / 11.3.0.AM1 [central-update]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25663?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-25663: ---------------------------------- Assignee: Nick Boldt > For JBIDE 4.5.3.AM1: Prepare for 4.5.3.AM1 / 11.3.0.AM1 [central-update] > ------------------------------------------------------------------------ > > Key: JBIDE-25663 > URL: https://issues.jboss.org/browse/JBIDE-25663 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central-update > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.5.3.AM1 > > > For JBIDE 4.5.3.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.5.3.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.3.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.3.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.71.1.Final > > {code} > mvn clean verify -Dtpc.version=4.71.1.Final > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.72.0.Final > > {code} > mvn clean verify -Dtpc.version=4.72.0.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-update task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25663) For JBIDE 4.5.3.AM1: Prepare for 4.5.3.AM1 / 11.3.0.AM1 [central-update]

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-25663: ---------------------------------- Summary: For JBIDE 4.5.3.AM1: Prepare for 4.5.3.AM1 / 11.3.0.AM1 [central-update] Key: JBIDE-25663 URL: https://issues.jboss.org/browse/JBIDE-25663 Project: Tools (JBoss Tools) Issue Type: Task Components: central-update Reporter: Nick Boldt Priority: Blocker Fix For: 4.5.3.AM1 For JBIDE 4.5.3.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.5.3.AM1-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.5.3.AM1-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.5.3.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.71.1.Final {code} mvn clean verify -Dtpc.version=4.71.1.Final {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.72.0.Final {code} mvn clean verify -Dtpc.version=4.72.0.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-update task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25663) For JBIDE 4.5.3.AM1: Prepare for 4.5.3.AM1 / 11.3.0.AM1 [central-update]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25663?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-25663. ------------------------------ Resolution: Done > For JBIDE 4.5.3.AM1: Prepare for 4.5.3.AM1 / 11.3.0.AM1 [central-update] > ------------------------------------------------------------------------ > > Key: JBIDE-25663 > URL: https://issues.jboss.org/browse/JBIDE-25663 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central-update > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.5.3.AM1 > > > For JBIDE 4.5.3.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.5.3.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.3.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.3.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.71.1.Final > > {code} > mvn clean verify -Dtpc.version=4.71.1.Final > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.72.0.Final > > {code} > mvn clean verify -Dtpc.version=4.72.0.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-update task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25663) For JBIDE 4.5.3.AM1: Prepare for 4.5.3.AM1 / 11.3.0.AM1 [central-update]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25663?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25663: ------------------------------------ bump up to parent pom version = 4.5.3.AM1-SNAPSHOT > For JBIDE 4.5.3.AM1: Prepare for 4.5.3.AM1 / 11.3.0.AM1 [central-update] > ------------------------------------------------------------------------ > > Key: JBIDE-25663 > URL: https://issues.jboss.org/browse/JBIDE-25663 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central-update > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.5.3.AM1 > > > For JBIDE 4.5.3.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.5.3.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.3.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.3.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.71.1.Final > > {code} > mvn clean verify -Dtpc.version=4.71.1.Final > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.72.0.Final > > {code} > mvn clean verify -Dtpc.version=4.72.0.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-update task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4670) For JBDS 11.3.0.AM1: Prepare for 4.5.3.AM1 / 11.3.0.AM1 [installer]

by Nick Boldt (JIRA)

Nick Boldt created JBDS-4670: -------------------------------- Summary: For JBDS 11.3.0.AM1: Prepare for 4.5.3.AM1 / 11.3.0.AM1 [installer] Key: JBDS-4670 URL: https://issues.jboss.org/browse/JBDS-4670 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Task Components: installer Reporter: Nick Boldt Priority: Blocker Fix For: 11.3.0.AM1 For JBDS 11.3.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.5.3.AM1-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.5.3.AM1-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.5.3.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.71.1.Final {code} mvn clean verify -Dtpc.version=4.71.1.Final {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.72.0.Final {code} mvn clean verify -Dtpc.version=4.72.0.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 installer task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2018