May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-493) replace devstudio.jboss.com in all URLs with devstudio.redhat.com; remove links to www.qa.jboss server

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-493?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBTIS-493: ---------------------------------- [~pleacu] please fix all refs to devstudio.jboss.com. Should be devstudio.redhat.com. > replace devstudio.jboss.com in all URLs with devstudio.redhat.com; remove links to www.qa.jboss server > ------------------------------------------------------------------------------------------------------ > > Key: JBTIS-493 > URL: https://issues.jboss.org/browse/JBTIS-493 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2, 9.0.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Priority: Blocker > Fix For: 9.0.0.Alpha2 > > > There should be no references to devstudio.jboss.com anywhere in composite or aggregate update sites. > But today I found this: > {code:title=https://devstudio.redhat.com/9.0/staging/updates/integration-stack/discovery/9.0.0.Alpha1/compositeContent.xml} > <child location='https://devstudio.jboss.com/9.0/development/updates/'/> > <child location='https://devstudio.redhat.com/9.0/development/updates/core/9.0.0.Beta2/'/> > <child location='https://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.50.0.CR1...'/> > <child location='http://www.qa.jboss.com/binaries/RHDS/mars/development/updates/integratio...'/> > <child location='http://www.qa.jboss.com/binaries/RHDS/mars/development/updates/integratio...'/> > <child location='https://devstudio.jboss.com/targetplatforms/jbdsistarget/9.0.0.Beta1.jbds...'/> > <child location='https://devstudio.jboss.com/targetplatforms/jbdsistarget/9.0.0.Beta1.jbds...'/> > {code} > You should also not be linking to www.qa.jboss since that's an internal-facing server and devstudio.redhat.com is external facing. So anyone from outside the VPN will get errors when testing this site. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20208) For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [Arqullian, Birt, Portlet]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20208?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20208: ------------------------------- Fix Version/s: (was: 4.3.1.Final) > For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [Arqullian, Birt, Portlet] > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-20208 > URL: https://issues.jboss.org/browse/JBIDE-20208 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: birt > Affects Versions: 4.3.0.Beta2 > Reporter: Nick Boldt > Assignee: Snjezana Peco > Priority: Blocker > Labels: task > Fix For: 4.3.0.CR1 > > Attachments: birt-no-license.png > > > For JBIDE 4.3.0.CR1 [Birt]: Please perform the following tasks: > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100. > 2. Switch to using the new o.j.t.foundation.license.feature. Instructions here: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... > 2. Resolve this JIRA when done. QE can then verify and close it later. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Birt task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20208) For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [Arqullian, Birt, Portlet]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20208?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-20208. -------------------------------- Fix Version/s: 4.3.1.Final Resolution: Done That's because we included the old Portlet, 1.6.0.Final-v20141209-0339-B20, in JBT 4.3.1. This is because there are no actual changes in the code, so it was decided to not bother rebuilding it simply for a copyright update. https://github.com/jbosstools/jbosstools-portlet/commits (there's not even a 4.3.x branch). > For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [Arqullian, Birt, Portlet] > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-20208 > URL: https://issues.jboss.org/browse/JBIDE-20208 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: birt > Affects Versions: 4.3.0.Beta2 > Reporter: Nick Boldt > Assignee: Snjezana Peco > Priority: Blocker > Labels: task > Fix For: 4.3.1.Final, 4.3.0.CR1 > > Attachments: birt-no-license.png > > > For JBIDE 4.3.0.CR1 [Birt]: Please perform the following tasks: > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100. > 2. Switch to using the new o.j.t.foundation.license.feature. Instructions here: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... > 2. Resolve this JIRA when done. QE can then verify and close it later. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Birt task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22228) NPE when deploying to Openshift EAP

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22228?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-22228: ----------------------------------------------- [~adietish], method OpenShiftServerUtils.getDeploymentConfig() after getting getConnection(attributes) checks it for null and just return null without much ado. So, the general logic of this method may be silently return null if connection is not found. But before that it calls getService(attributes) - and this method does not check connection for null which causes NPE, because getConnection(attributes) does return null when fails. Should we add that check for null even if this issue is not reproduced any more? New issue may appear in future. Check connection == null should be consistent - either at every place in the chain of calls, or nowhere. > NPE when deploying to Openshift EAP > ----------------------------------- > > Key: JBIDE-22228 > URL: https://issues.jboss.org/browse/JBIDE-22228 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Environment: Windows 10 > Reporter: Thomas Mäder > Assignee: Max Rydahl Andersen > Fix For: 4.4.x > > > When I try to publish to an EAP in the CDK, I get a NullPointerException: > {code} > java.lang.NullPointerException > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getService(OpenShiftServerUtils.java:309) > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getService(OpenShiftServerUtils.java:298) > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getDeploymentConfig(OpenShiftServerUtils.java:390) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:87) > 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:3556) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3492) > at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:311) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22228) NPE when deploying to Openshift EAP

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22228?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich edited comment on JBIDE-22228 at 5/6/16 10:26 AM: ------------------------------------------------------------------------ OpenShiftServerUtils.getService() method got connection addressed in line 309 after PR https://github.com/jbosstools/jbosstools-openshift/pull/1041 merged on March 24, and the call got out of this line after PR https://github.com/jbosstools/jbosstools-openshift/pull/1071 merged on March 31. Only that connection instance might be null to cause the issue. [~tmader], could you please test several builds back to the period between the build that got PR 1041 and the build that got PR 1071? Pinpointing the build that 'accidentally' fixed this issue will let close it. was (Author: scabanovich): OpenShiftServerUtils.getService() method could have null connection addressed in line 309 only in master. [~tmader], could you please test several builds back to the moment you got the issue? Pinpointing the build that 'accidentally' fixed this issue will let close it. > NPE when deploying to Openshift EAP > ----------------------------------- > > Key: JBIDE-22228 > URL: https://issues.jboss.org/browse/JBIDE-22228 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Environment: Windows 10 > Reporter: Thomas Mäder > Assignee: Max Rydahl Andersen > Fix For: 4.4.x > > > When I try to publish to an EAP in the CDK, I get a NullPointerException: > {code} > java.lang.NullPointerException > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getService(OpenShiftServerUtils.java:309) > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getService(OpenShiftServerUtils.java:298) > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getDeploymentConfig(OpenShiftServerUtils.java:390) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:87) > 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:3556) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3492) > at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:311) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-468) Cannot resolve Teiid Designer dependencies in JBT IS at install-time

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-468?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-468. ----------------------------------- Verified with JBTIS 4.3.0.Final and JBDSIS 9.0.0.GA > Cannot resolve Teiid Designer dependencies in JBT IS at install-time > -------------------------------------------------------------------- > > Key: JBTIS-468 > URL: https://issues.jboss.org/browse/JBTIS-468 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution, target-platform, teiid > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.3.0.Alpha2 > > > Steps to repro: > 1. install eclipse-jee-mars-R-linux-gtk-x86_64.tar.gz and launch with sun-java2-8.0 (1.8.0-b132) > 2. Help > Install new > Add these URLs: > * http://download.jboss.org/jbosstools/mars/development/updates/ > * http://download.jboss.org/jbosstools/mars/staging/builds/integration-stac... > 3. select all features on the JBTIS site. Install all. Restart when prompted. > 4. Help > Install new > Add this URL: > * http://download.jboss.org/jbosstools/mars/staging/builds/integration-stac... > 5. Install everything but Teiid Designer 9.0.2, due to missing dependency on *org.jboss.tools.locus.sf.saxon [9.2.1,9.3.0)*: > {code} > Cannot complete the install because one or more required items could not be found. > Software being installed: Teiid Designer 9.0.2.Final-v20150615-1425-B1128 (org.teiid.designer.feature.feature.group 9.0.2.Final-v20150615-1425-B1128) > Missing requirement: Teiid DataTools Connectivity 9.0.2.Final-v20150615-1425-B1128 (org.teiid.datatools.connectivity.feature.feature.group 9.0.2.Final-v20150615-1425-B1128) requires 'org.jboss.tools.locus.sf.saxon [9.2.1,9.3.0)' but it could not be found > Cannot satisfy dependency: > From: Teiid Designer 9.0.2.Final-v20150615-1425-B1128 (org.teiid.designer.feature.feature.group 9.0.2.Final-v20150615-1425-B1128) > To: org.teiid.datatools.connectivity.feature.feature.group [9.0.2.Final-v20150615-1425-B1128]{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-469) wrong description on update site

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-469?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-469. ----------------------------------- Closed as obsolete. Now, there exists Final / GA update site for the Integration Stack. > wrong description on update site > -------------------------------- > > Key: JBTIS-469 > URL: https://issues.jboss.org/browse/JBTIS-469 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.3.0.Alpha2 > > Attachments: JBDS-IS-update-site-descriptions.png, JBT-IS-update-site-descriptions-wrong.png > > > When I load up the JBT IS 4.3.0.Alpha1 update site [1] in Eclipse, I see this title: "JBDS Integration Stack Aggregate - Final" > [1] http://download.jboss.org/jbosstools/mars/staging/builds/integration-stac... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20474) Cleanup last CI builds more aggressively

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20474?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20474: ------------------------------------ OK, will do. Note to self, should set up the # of builds to composite to a different default number for pull requests... namely, only 1. Test by rebuilding this site, which will retain last 7 builds but should only composite 1. http://download.jboss.org/jbosstools/neon/snapshots/pulls/jbosstools-buil... > Cleanup last CI builds more aggressively > ---------------------------------------- > > Key: JBIDE-20474 > URL: https://issues.jboss.org/browse/JBIDE-20474 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Nick Boldt > Priority: Optional > Fix For: 4.4.0.Alpha2 > > > [18/08/2015 15:29:34] Fred Bricon: when building central, I see > [18/08/2015 15:29:36] Fred Bricon: [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 14,58kB at 0B/s) > [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 14,18kB at 0B/s) > [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 14,93kB at 0B/s) > [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 13,88kB at 0B/s) > [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 14,25kB at 0B/s) > [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 14,77kB at 0B/s) > [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 14,43kB at 0B/s) > [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 13,94kB at 0B/s) > [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 14,74kB at 0B/s) > [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 13,7kB at 0B/s) > [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 13,58kB at 0B/s) > [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 13,95kB at 0B/s) > [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 13,11kB at 0B/s) > [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 13,86kB at 0B/s) > Nick sez: > {quote} > somethign something "store fewer instances of /snapshots/builds /JOB_NAME/TIMESTAMP; more aggressive cleanup required; suggest only keeping 5 builds max" > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-473) Update bpel, bpmn2 components for Mars

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-473?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-473. ----------------------------------- Verified with JBDS-IS 9.0.0.GA which contains - BPEL 1.0.5.Final-v20160115-1558 - BPMN2 1.2.1.Final-v20160218-1950-B212 > Update bpel, bpmn2 components for Mars > -------------------------------------- > > Key: JBTIS-473 > URL: https://issues.jboss.org/browse/JBTIS-473 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: BPEL, BPMN2 > Affects Versions: 4.3.0.Alpha2 > Reporter: Paul Leacu > Assignee: Paul Leacu > > Mirror and use the latest Mars bpel, bpmn2 plugins. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21785) enable hybrid jobs which can handle both commits and PRs with different publishing patterns

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21785?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-21785 at 5/6/16 10:10 AM: ------------------------------------------------------------- Seems as though PR jobs won't also build commits automatically: {code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Master/job/jbosstools-server__pull-request_master/5/} GitHub pull request #412 of commit ce964c7d9c30d8732a9627d8e3b37997eb9c6d5f, no merge conflicts. 734e1c3a03355c0a57e21bb723241e98f2286751 refs/remotes/origin/pr/412/merge Test Result (69 failures / ±0) {code} vs. {code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Master/job/jbosstools-server_master/966/} JBIDE-22157 - per-module zip settings (commit: ce964c7d9c30d8732a9627d8e3b37997eb9c6d5f) Revision: ce964c7d9c30d8732a9627d8e3b37997eb9c6d5f refs/remotes/origin/master Test Result (3 failures / ±0) {code} So, perhaps the solution is to have a buildflow job triggered every 3 hours to poke the projects into building anything they haven't already built. was (Author: nickboldt): Seems as though PR jobs won't also build commits: {code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Master/job/jbosstools-server__pull-request_master/5/} GitHub pull request #412 of commit ce964c7d9c30d8732a9627d8e3b37997eb9c6d5f, no merge conflicts. 734e1c3a03355c0a57e21bb723241e98f2286751 refs/remotes/origin/pr/412/merge Test Result (69 failures / ±0) {code} vs. {code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Master/job/jbosstools-server_master/966/} JBIDE-22157 - per-module zip settings (commit: ce964c7d9c30d8732a9627d8e3b37997eb9c6d5f) Revision: ce964c7d9c30d8732a9627d8e3b37997eb9c6d5f refs/remotes/origin/master Test Result (3 failures / ±0) {code} So, perhaps the solution is to have a buildflow job triggered every 3 hours to poke the projects into building anything they haven't already built. > enable hybrid jobs which can handle both commits and PRs with different publishing patterns > ------------------------------------------------------------------------------------------- > > Key: JBIDE-21785 > URL: https://issues.jboss.org/browse/JBIDE-21785 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Affects Versions: 4.3.1.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.0.Alpha2 > > > Currently we have jobs which handle building from commits, then publishing to a builds/ folder. > And I've prototyped a couple jobs [1], [2] which can handle building from PRs, then publishing to a pulls/ folder. > [1] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-site... > [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-site... > Now we need to combine the jobs so that we can do both deployments from the same job, eg., > {code} > if [[ ! ${ghprbPullId} ]]; then > mvnStep1="clean install -DskipTests" # build without tests > mvnStep2="deploy -Pdeploy-to-jboss.org" # deploy if p2diff or SHA check shows difference into /builds/ folder > mvnStep3="verify" # run tests & fail job if problems found > else > mvnStep1="clean deploy -Pdeploy-pr" # build and test, then deploy to /pulls/ folder if successful or fail if tests fail > mvnStep2="NONE" > mvnStep3="NONE" > fi > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 May 2016