October 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25137) externalize the Eclipse platform and JEE bundles used for running jbt builds/tests

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25137?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25137: ------------------------------------ File pushed here: https://raw.githubusercontent.com/jbosstools/jbosstools-build-ci/master/u... Script to fetch and include it in env vars in Jenkins: {code} + <hudson.tasks.Shell> + <command># fetch eclipse tarball from jbosstools-jenkins.properties +curl -s -S -k https://raw.githubusercontent.com/jbosstools/jbosstools-build-ci/master/u... > jbosstools-jenkins.properties +</command> + </hudson.tasks.Shell> + <EnvInjectBuilder plugin="envinject(a)1.93.1"> + <info> + <propertiesFilePath>jbosstools-jenkins.properties</propertiesFilePath> + </info> + </EnvInjectBuilder> {code} then later... {code} -downloadURL=${downloadURL}</properties> +downloadURL=${downloadPhpURL}${eclipsePlatformURL}</properties> {code} Example of it working: {code} [jbosstools-composite-install_master] $ /qa/tools/opt/groovy-2.4.3/bin/groovy -DeclipseCacheDirectory=/home/hudson/static_build_env/jbds/tools/sources -DdownloadURL=${downloadPhpURL}${eclipsePlatformURL} /mnt/hudson_workspace/workspace/jbosstools-composite-install_master/getAndInstallEclipse.groovy Downloading: eclipse-platform-4.7.1a-linux-gtk-x86_64.tar.gz from http://www.eclipse.org/downloads/download.php?r=1&file=/eclipse/downloads... (x86_64) [untar] Expanding: /home/hudson/static_build_env/jbds/tools/sources/eclipse-platform-4.7.1a-linux-gtk-x86_64.tar.gz into /mnt/hudson_workspace/workspace/jbosstools-composite-install_master{code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > externalize the Eclipse platform and JEE bundles used for running jbt builds/tests > ---------------------------------------------------------------------------------- > > Key: JBIDE-25137 > URL: https://issues.jboss.org/browse/JBIDE-25137 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, install-tests, integration-tests > Affects Versions: 4.5.1.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.Final > > > Currently, we have a number of Eclipse URLs in jobs and they're inconsistently applied, plus are scattered across a lot of jobs / variations. > Instead, we should externalize these URLs as variables we can control from some other global properties file, perhaps located in https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/ and called *jbosstools-jenkins.properties*. This would make the jobs easier to maintain and I'd forget to update stuff less often. :D > Affected jobs: > * devstudio_master/job/jbosstools-composite-install_master/config.xml > * devstudio_master/job/jbosstools-install-p2director.install-tests.matrix_master/config.xml > * devstudio_target_platforms/job/jbosstoolstargetplatform-4.70.x/config.xml > * devstudio_target_platforms/job/jbosstoolstargetplatform-4.71.x/config.xml > * devstudio_target_platforms/job/jbosstoolstargetplatform-4.71.x-experimental/config.xml > * devstudio_target_platforms/job/jbosstoolstargetplatformrequirements-mirror-matrix/config.xml > * jbosstools-releng/job/jbosstools-cleanup/config.xml > * ...? > URL patterns: > * /eclipse/downloads/drops4/R-4.7.1-201709061700/eclipse-platform-4.7.1-linux-gtk.tar.gz > * /eclipse/downloads/drops4/M-4.7.1RC4-201709061700/eclipse-platform-4.7.1RC4-linux-gtk.tar.gz > * /eclipse/downloads/drops4/S-4.7RC4a-201706120950/eclipse-platform-4.7RC4a-linux-gtk.tar.gz > * http://www.eclipse.org/downloads/download.php?r=1&file=/eclipse/downl... > * http://download.eclipse.org/eclipse/downloads/drops4/S-4.7RC4a-2017061209... > * eclipse_downloads_drops4_R-4.7.1-201709061700_eclipse-platform-4.7.1-linux-gtk.tar.gz > * eclipse-platform-4.7.1-linux-gtk.tar.gz > * ... more? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24868) Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24868?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-24868: ------------------------------------- I just tested and it doesn't seem fixed to me. Inspecting the route shows the expected: "annotations" : { "haproxy.router.openshift.io/timeout" : "42h", "openshift.io/host.generated" : "true", "template.openshift.io/expose-uri" : "http://{.spec.host}{.spec.path}" } But the debug session is terminated after 30 seconds, the debugger terminates, and I get a 502 Bad Gateway in the web browser. > Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24868 > URL: https://issues.jboss.org/browse/JBIDE-24868 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.0.Final > Reporter: Aurélien Pupier > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.1.Final > > Attachments: application-is-not-available.png, breakpoint-suspend-thread.png, webui_edit-add-service.png > > > it will avoid to have "debug connections always killed after 30s staying in a breakpoint" > see https://twitter.com/ro14nd/status/895886024387067904 for source of suggestion > k8 documentations on the matter are here: https://kubernetes.io/docs/tasks/configure-pod-container/configure-livene... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25235) Forge New and Noteworthy for 4.5.1.Final

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25235?page=com.atlassian.jira.plugi... ] George Gastaldi closed JBIDE-25235. ----------------------------------- Resolution: Rejected > Forge New and Noteworthy for 4.5.1.Final > ----------------------------------------------------- > > Key: JBIDE-25235 > URL: https://issues.jboss.org/browse/JBIDE-25235 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Jeff MAURY > Assignee: George Gastaldi > Priority: Critical > Labels: task > Fix For: 4.5.1.Final > > > George Gastaldi, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Forge JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Forge, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Forge by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-25230 #comment Create N&N for Forge 4.5.1.Final #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Forge for this milestone, please *reject* and *close* this issue. > ---- > If there is nothing new or noteworthy for 4.5.1.Final since the AM3 release of Forge, please *reject* and *close* this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to _add a comment to the final document_ then submit a PR to create a separate <component>-news-4.5.1.Final.adoc file here: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > However, if you want to _replace all previous N&Ns by a *new* document_, then submit a PR to create a *new* <component>-news-4.5.1.Final.adoc file, adding: {code}page-include-previous: false{code}. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24845) [regression] unable to open the Maven Repositories wizard

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24845?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-24845: ------------------------------------- [~dbocharov] m2e doesn't use external maven installations to work in Eclipse, those are for running Maven launch configurations. The problem occurs in m2e 1.9 that uses the Maven 3.5.0 embedder. Try installing it from http://download.eclipse.org/technology/m2e/snapshots/1.9.0/latest/ > [regression] unable to open the Maven Repositories wizard > --------------------------------------------------------- > > Key: JBIDE-24845 > URL: https://issues.jboss.org/browse/JBIDE-24845 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.4.4.Final > Reporter: Fred Bricon > Assignee: Dmitrii Bocharov > Fix For: 4.5.1.Final > > > 1 - open Preferences > JBoss Tools > JBoss Maven Integration > 2 - click on the Configure Maven Repositories... button > expected: the Maven repositories wizard open > actual: Unhandled event loop exception: > {noformat} > java.lang.NoSuchFieldError: DEFAULT_USER_SETTINGS_FILE > at org.jboss.tools.maven.ui.wizard.ConfigureMavenRepositoriesWizardPage.getUserSettings(ConfigureMavenRepositoriesWizardPage.java:988) > at org.jboss.tools.maven.ui.wizard.ConfigureMavenRepositoriesWizardPage.createControl(ConfigureMavenRepositoriesWizardPage.java:242) > at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:176) > at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:688) > at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:580) > at org.eclipse.jface.window.Window.create(Window.java:426) > at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1096) > at org.jboss.tools.maven.ui.preferences.ConfiguratorPreferencePage$2.widgetSelected(ConfiguratorPreferencePage.java:155) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4257) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1502) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1525) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1510) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1314) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4081) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:818) > at org.eclipse.jface.window.Window.open(Window.java:794) > at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:211) > at org.eclipse.ui.internal.handlers.ShowPreferencePageHandler.execute(ShowPreferencePageHandler.java:59) > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1182) JBTIS Target Platform - sync with JBT 4.5.1.Final

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-1182: --------------------------------- Summary: JBTIS Target Platform - sync with JBT 4.5.1.Final Key: JBTIS-1182 URL: https://issues.jboss.org/browse/JBTIS-1182 Project: JBoss Tools Integration Stack Issue Type: Task Reporter: Paul Leacu *Reason:* Sync w/ JBT 4.5.1.Final/ 4.71.0.Final *Project page/sources:* *Version:* 4.5.1.Final *License and owner:* ... *Original p2 repo:* *JBoss mirror:* *Include Sources:* Yes *Affected JBoss Tools components:* Integration Stack *Include in JBDS:* Yes (IS) *Type of dependency:* testing|central-only|distribution *List of bundles added/removed:* {code} {code} First sync with the latest .Final-SNAPSHOT versions and create JBTIS TP 4.5.1.Beta1a -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25228) target platform fix-version and targetToRepoMojo no longer able to find multiple IU versions

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25228?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25228: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.1.Final) > target platform fix-version and targetToRepoMojo no longer able to find multiple IU versions > -------------------------------------------------------------------------------------------- > > Key: JBIDE-25228 > URL: https://issues.jboss.org/browse/JBIDE-25228 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.5.1.Final > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.5.x > > > With these recent changes [0], [1], target platform resolution is no longer able to fetch more than one version of an IU. > We need apache.commons.codec 1.6.0.v201305230611, per the .target file [2], but only org.apache.commons.codec_1.9.0.v20170208-1614.jar is found in the update site [3], so the job [4] cannot perform an installation and validation of the TP fails. > Is there a setting I can pass in to make TargetToRepo more greedy about pulling multiple versions of IUs? > Note too that I was having problems last night getting the fix-version mojo to properly find and update the versions of WTP in the new 3.9.1a site, even when explicitly setting 0.0.0 to force it to search and update. Seems the target platform resolver will only pull the latest version of an IU, rather than an older one (a few WTP features have gone backwards in their timestamp). But it could also not resolve a version change from 3.3.600 [5] to 3.3.601 [6], so I had to update the version manually. > [0] https://github.com/jbosstools/jbosstools-maven-plugins/commit/2b724eceadb... > [1] https://github.com/jbosstools/jbosstools-maven-plugins/commit/ac4e492fab4... > [2] https://github.com/jbosstools/jbosstools-target-platforms/blob/4.71.x/jbo... > [3] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.7... > [4] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... > [5] https://github.com/jbosstools/jbosstools-target-platforms/blob/14ec465a9b... > [6] https://github.com/jbosstools/jbosstools-target-platforms/blob/4.71.x/jbo... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25228) target platform fix-version and targetToRepoMojo no longer able to find multiple IU versions

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25228?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25228: ------------------------------------ I did manage to fix [1] this compilation problem ... {code} 18:20:58 [ERROR] COMPILATION ERROR : 18:20:58 [INFO] ------------------------------------------------------------- 18:20:58 [ERROR] /mnt/hudson_workspace/workspace/jbosstools-maven-plugins.tycho-plugins_master/tycho-plugins/repository-utils/src/main/java/org/jboss/tools/tycho/sitegenerator/GenerateRepositoryFacadeMojo.java:[651,37] multi-catch statement is not supported in -source 1.5 18:20:58 (use -source 7 or higher to enable multi-catch statement){code} [2] which I assume you didn't see because you built with m2e and mvn 3.3.9, rather than commandline mvn 3.5.0: [1] https://github.com/jbosstools/jbosstools-maven-plugins/commit/52ed36041c3... [2] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... > target platform fix-version and targetToRepoMojo no longer able to find multiple IU versions > -------------------------------------------------------------------------------------------- > > Key: JBIDE-25228 > URL: https://issues.jboss.org/browse/JBIDE-25228 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.5.1.Final > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.5.1.Final > > > With these recent changes [0], [1], target platform resolution is no longer able to fetch more than one version of an IU. > We need apache.commons.codec 1.6.0.v201305230611, per the .target file [2], but only org.apache.commons.codec_1.9.0.v20170208-1614.jar is found in the update site [3], so the job [4] cannot perform an installation and validation of the TP fails. > Is there a setting I can pass in to make TargetToRepo more greedy about pulling multiple versions of IUs? > Note too that I was having problems last night getting the fix-version mojo to properly find and update the versions of WTP in the new 3.9.1a site, even when explicitly setting 0.0.0 to force it to search and update. Seems the target platform resolver will only pull the latest version of an IU, rather than an older one (a few WTP features have gone backwards in their timestamp). But it could also not resolve a version change from 3.3.600 [5] to 3.3.601 [6], so I had to update the version manually. > [0] https://github.com/jbosstools/jbosstools-maven-plugins/commit/2b724eceadb... > [1] https://github.com/jbosstools/jbosstools-maven-plugins/commit/ac4e492fab4... > [2] https://github.com/jbosstools/jbosstools-target-platforms/blob/4.71.x/jbo... > [3] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.7... > [4] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... > [5] https://github.com/jbosstools/jbosstools-target-platforms/blob/14ec465a9b... > [6] https://github.com/jbosstools/jbosstools-target-platforms/blob/4.71.x/jbo... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1179) List of fixed issues in BPMN2 1.4.1

by Paul Leacu (JIRA)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1181) Fix unstable bpmn2 message tests

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1181?page=com.atlassian.jira.plugin... ] Andrej Podhradsky updated JBTIS-1181: ------------------------------------- Component/s: QE > Fix unstable bpmn2 message tests > -------------------------------- > > Key: JBTIS-1181 > URL: https://issues.jboss.org/browse/JBTIS-1181 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: BPMN2, QE > Affects Versions: 11.1.0.Beta1 > Reporter: Dominik Hanak > Assignee: Dominik Hanak > Fix For: 11.1.0.GA > > > Tests that needs fixing: > ComplexReceiveTaskTest > ComplexSendTaskTest > ComplexMessageStartTest -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4595) Unresolved Bundles after install all the stuff from RH Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4595?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-4595 at 10/25/17 12:21 PM: ------------------------------------------------------------- Looking at your ALL_EXCEPT files, I see lots of duplicate IUs but many in ~/.eclipse are older than the ones from the RPM. Possible reasons for httpclient 4.5.2 conflict: * o.j.t.openshift.io.core require-bundles httpclient 4.0 - NOT A PROBLEM as any 4.x version would be allowed here * jmx.jolokia plugin in jbt-server includes 4.5.2 inside a lib/ folder - NOT A PROBLEM, nested jar within a plugin * o.e.ecf.filetransfer.httpclient4.feature includes org.apache.httpcomponents.httpclient 4.5.2.v20170210-0925 ** this is then required by c.j.ds.core.rpmdeps.feature ** but we exclude org.apache.httpcomponents.httpclient from the RPM, so that it can be resolved via symlink: {code} #➔ find /opt/rh/rh-eclipse47/root/usr/share/eclipse/droplets/devstudio/ -name "*httpclient*jar" -exec ls -l {} \; /opt/rh/rh-eclipse47/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.apache.httpcomponents.httpclient_4.3.6.jar -> /opt/rh/rh-java-common/root/usr/share/java/httpcomponents/httpclient.jar /opt/rh/rh-eclipse47/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.apache.httpcomponents.httpclient.cache_4.3.6.jar -> /opt/rh/rh-java-common/root/usr/share/java/httpcomponents/httpclient-cache.jar {code} If you delete your ~/.eclipse folder and install everything from Central again (minus Spring boot wizard, which we know has a bug upstream), one connector at a time, can you determine which connector is causing the conflict? was (Author: nickboldt): Looking at your ALL_EXCEPT files, I see lots of duplicate IUs but many in ~/.eclipse are older than the ones from the RPM. If you delete your ~/.eclipse folder and install everything from Central again (minus Spring boot wizard, which we know has a bug upstream), one connector at a time, can you determine which connector is causing the conflict? > Unresolved Bundles after install all the stuff from RH Central > -------------------------------------------------------------- > > Key: JBDS-4595 > URL: https://issues.jboss.org/browse/JBDS-4595 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: central, central-update, rpm > Affects Versions: 11.1.0.GA > Reporter: Lukáš Valach > Assignee: Nick Boldt > Fix For: 11.1.0.GA > > Attachments: findPackages.sh, p2browser_org.apache.httpcomponents.httpclient.png, rh-eclipse47-devstudio11.1-0.20171024.0823.el7.log.20171025-0935_strict-ONLY_SPRING_IDE.txt, rh-eclipse47-devstudio11.1-0.20171024.0823.el7.log.20171025-0935_strict-ONLY_SPRING_IDE_packages.txt, rh-eclipse47-devstudio11.1-0.20171024.0823.el7.log.20171025-1005_strict-ALL_EXCEPT_SPRING_IDE.txt, rh-eclipse47-devstudio11.1-0.20171024.0823.el7.log.20171025-1005_strict-ALL_EXCEPT_SPRING_IDE_packages.txt, rh-eclipse47-devstudio4.7.1-5.2.el7.log.20171024-1353_strict.txt, rh-eclipse47-devstudio4.7.1-5.2.el7.log.20171025-1040_strict.txt, rh-eclipse47-devstudio4.7.1-5.2.el7.log.20171025-1105_strict.txt, rh-eclipse47-devstudio4.7.1-5.2.el7.log.20171025-1105_strict.txt > > > Our "Install all from Central" test found some BundleExceptions in the log, see \[1\]. > \[1\] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/user/lvalach... > It seems that there are some plugins which are not compatible with each others. The "install one by one" test passed as green \[2\]. So individual plugins work fine. > \[2\] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/user/lvalach... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 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 October 2017