May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22354) Remediation page showing up because of Mylyn Wikitext

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22354?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-22354: ----------------------------------- Priority: Blocker (was: Major) > Remediation page showing up because of Mylyn Wikitext > ----------------------------------------------------- > > Key: JBIDE-22354 > URL: https://issues.jboss.org/browse/JBIDE-22354 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Affects Versions: 4.4.0.Alpha2 > Reporter: Mickael Istria > Priority: Blocker > Fix For: 4.4.0.Alpha2 > > > Take an Eclipse JavaScript M7, and try to install all JBoss Tools from http://download.jboss.org/jbosstools/neon/snapshots/updates/ > It shows a remediation page because JBoss Tools ships an asciidoc feature which is in different version that the one upstream. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21657) set up jobs to handle building from PRs

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21657?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-21657: ---------------------------------------- We do not need to publish to a specific location for a given PR. Since the build-specific repo are not going to be widely used, just "archiving" the repository on a public jenkins instance (are wonka or Central CI public) would be enough to have anyone able to test it easily. Then the build just becomes "mvn clean verify" and "archive artifacts" and we can get rid of the wrapper around it. > set up jobs to handle building from PRs > --------------------------------------- > > Key: JBIDE-21657 > URL: https://issues.jboss.org/browse/JBIDE-21657 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.Beta2, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha2 > > > First experimental build: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... > Output: > http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui... > {code} > "revision" : { > "HEAD" : "bfe76fb3f3c34d68b873d0acf715e2145e4cb805", > "currentBranch" : "HEAD", > "knownReferences" : [{ > "name" : "origin", > "url" : "git://github.com/jbosstools/jbosstools-build-sites.git", > "ref" : "pr/221/merge" > }] > }, > {code} > http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui... > {code} > #Fri Feb 05 16:42:42 EST 2016 > null\:merge=bfe76fb3f3c34d68b873d0acf715e2145e4cb805 > HEAD=bfe76fb3f3c34d68b873d0acf715e2145e4cb805 > {code} > build log: > {code} > Started by upstream project "jbosstools-build-sites.aggregate.child-sites__pull-request_master" build number 1 > originally caused by: > GitHub pull request #221 of commit 50c10ad83d250d2b86f5697c4581ba8f9cb4937d, no merge conflicts. > ... > Fetching upstream changes from git://github.com/jbosstools/jbosstools-build-sites.git > > git -c core.askpass=true fetch --tags --progress git://github.com/jbosstools/jbosstools-build-sites.git +refs/heads/*:refs/remotes/origin/* +refs/pull/*:refs/remotes/origin/pr/* > Checking out Revision bfe76fb3f3c34d68b873d0acf715e2145e4cb805 (refs/remotes/origin/pr/221/merge) > > git config core.sparsecheckout # timeout=10 > > git checkout -f bfe76fb3f3c34d68b873d0acf715e2145e4cb805 > {code} > vars: > {code} > -DghprbActualCommit=50c10ad83d250d2b86f5697c4581ba8f9cb4937d > -DghprbPullId=221 > -Dsha1=origin/pr/221/merge > "-DghprbPullDescription=GitHub pull request #221 of commit 50c10ad83d250d2b86f5697c4581ba8f9cb4937d, no merge conflicts." > -DghprbActualCommit=50c10ad83d250d2b86f5697c4581ba8f9cb4937d > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3884) Define the version of EAP that we embed with next major version of devstudio

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3884?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBDS-3884: -------------------------------------- I created a trello card for that - https://trello.com/c/L5i8c0ff/142-devstudio-bundle-eap-7-0-0-instead-of-t... > Define the version of EAP that we embed with next major version of devstudio > ---------------------------------------------------------------------------- > > Key: JBDS-3884 > URL: https://issues.jboss.org/browse/JBDS-3884 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Task > Components: runtime > Affects Versions: 10.0.0.GA > Reporter: Len DiMaggio > Assignee: Todd Mancini > Fix For: 10.0.0.GA > > > Should it continue to be EAP 6.x or the new EAP 7.0 ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-192) JSON validator ignores duplicate key [EBZ#492469]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-192: --------------------------------------- Summary: JSON validator ignores duplicate key [EBZ#492469] Key: ERT-192 URL: https://issues.jboss.org/browse/ERT-192 Project: Eclipse Release Train Issue Type: Task Components: WTP Source Editing Reporter: Friendly Jira Robot Fix For: Neon (4.6) RC1 For example: { "name": 1, "name": 2 } -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-192) JSON validator ignores duplicate key [EBZ#492469]

by Friendly Jira Robot (JIRA)

[ https://issues.jboss.org/browse/ERT-192?page=com.atlassian.jira.plugin.sy... ] Friendly Jira Robot resolved ERT-192. ------------------------------------- Resolution: Done > JSON validator ignores duplicate key [EBZ#492469] > ------------------------------------------------- > > Key: ERT-192 > URL: https://issues.jboss.org/browse/ERT-192 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Labels: 3.8_RC1, bzira, wst.json > Fix For: Neon (4.6) RC1 > > > For example: > { > "name": 1, > "name": 2 > } -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-193) TypeHierarchy.getSuperclass() returns null [EBZ#493474]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-193: --------------------------------------- Summary: TypeHierarchy.getSuperclass() returns null [EBZ#493474] Key: ERT-193 URL: https://issues.jboss.org/browse/ERT-193 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Friendly Jira Robot Moving from org.eclipse.wst.jsdt.core_1.3.401 to org.eclipse.wst.jsdt.core_2.0.0, TypeHierarchy.getSuperclass() returns null now. Here my usage code snippet ... String[] baseTypeNames = new String[]{"dijit._WidgetBase", "dijit._Widget"}; //$NON-NLS-1$ //$NON-NLS-2$ SubMonitor sub = SubMonitor.convert(monitor, baseTypeNames.length); for (String baseTypeName : baseTypeNames) { SubMonitor typeMonitor = sub.newChild(1); IType[] baseTypes = jsproject.findTypes(baseTypeName); ITypeHierarchy hierarchy = baseTypes[0].newTypeHierarchy(jsproject, typeMonitor); IType type = hierarchy.getSuperclass(baseTypes[0]); //type.... ->NPE ... } -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-184) NPE when chromium feature is not present [EBZ#493234]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-184?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk reassigned ERT-184: ------------------------------- Assignee: Ilya Buziuk > NPE when chromium feature is not present [EBZ#493234] > ----------------------------------------------------- > > Key: ERT-184 > URL: https://issues.jboss.org/browse/ERT-184 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Ilya Buziuk > Priority: Critical > Labels: 3.8_RC1, Debug, bzira > Fix For: Neon (4.6) RC1 > > > Starting a debugging session without Chromium feature available causes an NPE. This can have 2 solutions (and maybe both of them are desirable). > * A better error message than a NPE when there is no debug support > * Include the chromium feature by default, as "included" by the main JSDT feature. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-184) NPE when chromium feature is not present [EBZ#493234]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-184?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk resolved ERT-184. ----------------------------- Resolution: Done > NPE when chromium feature is not present [EBZ#493234] > ----------------------------------------------------- > > Key: ERT-184 > URL: https://issues.jboss.org/browse/ERT-184 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Ilya Buziuk > Priority: Critical > Labels: 3.8_RC1, Debug, bzira > Fix For: Neon (4.6) RC1 > > > Starting a debugging session without Chromium feature available causes an NPE. This can have 2 solutions (and maybe both of them are desirable). > * A better error message than a NPE when there is no debug support > * Include the chromium feature by default, as "included" by the main JSDT feature. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22338) NullPointerException below SocketProposalComputer.computeCompletionProposals (thrown in BasicFeatureMap.contains)

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22338?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-22338: -------------------------------------- Assignee: Xavier Coulon > NullPointerException below SocketProposalComputer.computeCompletionProposals (thrown in BasicFeatureMap.contains) > ----------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22338 > URL: https://issues.jboss.org/browse/JBIDE-22338 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.3.1.Final > Reporter: Automated Error Reporting Bot > Assignee: Xavier Coulon > > The following problem was reported via the automated error reporting: > Message: HIDDEN > {noformat} > java.lang.NullPointerException: null > at org.eclipse.emf.ecore.util.BasicFeatureMap.contains(BasicFeatureMap.java:712) > at org.eclipse.emf.ecore.util.BasicFeatureMap.contains(BasicFeatureMap.java:684) > at org.eclipse.emf.ecore.util.BasicFeatureMap.add(BasicFeatureMap.java:1281) > at org.eclipse.emf.ecore.util.FeatureMapUtil$FeatureEList.add(FeatureMapUtil.java:744) > at org.eclipse.jst.jee.model.internal.EJBAnnotationReader.sessionBeanFound(EJBAnnotationReader.java:338) > at org.eclipse.jst.jee.model.internal.EJBAnnotationReader.processResult(EJBAnnotationReader.java:254) > at org.eclipse.jst.jee.model.internal.EJBAnnotationReader.processAddedCompilationUnit(EJBAnnotationReader.java:411) > at org.eclipse.jst.jee.model.internal.EJBAnnotationReader.processChangedCompilationUnit(EJBAnnotationReader.java:569) > at org.eclipse.jst.jee.model.internal.common.AbstractAnnotationModelProvider.recursevilyProcessCompilationUnits(AbstractAnnotationModelProvider.java:553) > at org.eclipse.jst.jee.model.internal.common.AbstractAnnotationModelProvider.internalPostReconcile(AbstractAnnotationModelProvider.java:466) > at org.eclipse.jst.jee.model.internal.common.AbstractAnnotationModelProvider.elementChanged(AbstractAnnotationModelProvider.java:446) > at org.eclipse.jdt.internal.core.DeltaProcessor$3.run(DeltaProcessor.java:1662) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.jdt.internal.core.DeltaProcessor.notifyListeners(DeltaProcessor.java:1652) > at org.eclipse.jdt.internal.core.DeltaProcessor.fireReconcileDelta(DeltaProcessor.java:1504) > at org.eclipse.jdt.internal.core.DeltaProcessor.fire(DeltaProcessor.java:1463) > at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:770) > at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:789) > at org.eclipse.jdt.internal.core.CompilationUnit.reconcile(CompilationUnit.java:1250) > at org.eclipse.jdt.internal.core.CompilationUnit.reconcile(CompilationUnit.java:1227) > at org.eclipse.jdt.internal.core.CompilationUnit.reconcile(CompilationUnit.java:1192) > at org.jboss.tools.websockets.ui.internal.ca.SocketProposalComputer.computeCompletionProposals(SocketProposalComputer.java:130) > at org.eclipse.jdt.internal.ui.text.java.CompletionProposalComputerDescriptor.computeCompletionProposals(CompletionProposalComputerDescriptor.java:333) > at org.eclipse.jdt.internal.ui.text.java.CompletionProposalCategory.computeCompletionProposals(CompletionProposalCategory.java:337) > at org.eclipse.jdt.internal.ui.text.java.ContentAssistProcessor.collectProposals(ContentAssistProcessor.java:322) > at org.eclipse.jdt.internal.ui.text.java.ContentAssistProcessor.computeCompletionProposals(ContentAssistProcessor.java:279) > at org.eclipse.jface.text.contentassist.ContentAssistant$5.run(ContentAssistant.java:1904) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.jface.text.contentassist.ContentAssistant.computeCompletionProposals(ContentAssistant.java:1902) > at org.eclipse.jface.text.contentassist.CompletionProposalPopup.computeProposals(CompletionProposalPopup.java:573) > at org.eclipse.jface.text.contentassist.CompletionProposalPopup.access$16(CompletionProposalPopup.java:570) > at org.eclipse.jface.text.contentassist.CompletionProposalPopup$2.run(CompletionProposalPopup.java:505) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at org.eclipse.jface.text.contentassist.CompletionProposalPopup.showProposals(CompletionProposalPopup.java:499) > at org.eclipse.jface.text.contentassist.ContentAssistant.showPossibleCompletions(ContentAssistant.java:1720) > at org.eclipse.jdt.internal.ui.javaeditor.CompilationUnitEditor$AdaptedSourceViewer.doOperation(CompilationUnitEditor.java:180) > at org.eclipse.ui.texteditor.ContentAssistAction$1.run(ContentAssistAction.java:82) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at org.eclipse.ui.texteditor.ContentAssistAction.run(ContentAssistAction.java:80) > at org.eclipse.jface.action.Action.runWithEvent(Action.java:473) > at org.eclipse.jface.commands.ActionHandler.execute(ActionHandler.java:122) > at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) > at sun.reflect.GeneratedMethodAccessor.invoke(null:-1) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(null:-1) > at java.lang.reflect.Method.invoke(null:-1) > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56) > {noformat} > Bundles: > | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.11.1.v20150903-1804 | > | org.eclipse.e4.core.di | 1.5.0.v20150421-2214 | 1.5.0.v20150421-2214 | > | org.eclipse.emf.ecore | 2.11.2.v20160208-0816 | 2.11.2.v20160208-0816 | > | org.eclipse.jdt.core | 3.11.2.v20160128-0629 | 3.11.2.v20160128-0629 | > | org.eclipse.jdt.ui | 3.11.2.v20151123-1510 | 3.11.2.v20151123-1510 | > | org.eclipse.jface | 3.11.1.v20160128-1644 | 3.11.1.v20160128-1644 | > | org.eclipse.jface.text | 3.10.0.v20150603-1752 | 3.10.0.v20150603-1752 | > | org.eclipse.jst.jee | 1.0.700.v201404092004 | 1.0.700.v201404092004 | > | org.eclipse.swt | 3.104.2.v20160212-1350 | 3.104.2.v20160212-1350 | > | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.107.0.v20150507-1945 | > | org.jboss.tools.websockets.ui | 1.8.1.Final-v20160331-0952-B76 | 1.8.1.Final-v20160331-0952-B76 | > Operating Systems: > | Windows | 6.3.0 | 10.0.0 | > The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/57279e32e4b0a54983...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22342) NullPointerException below SocketProposalComputer.computeCompletionProposals (thrown in WebAnnotationReader.analyzeCompilationUnit)

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22342?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-22342: -------------------------------------- Assignee: Xavier Coulon > NullPointerException below SocketProposalComputer.computeCompletionProposals (thrown in WebAnnotationReader.analyzeCompilationUnit) > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22342 > URL: https://issues.jboss.org/browse/JBIDE-22342 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Reporter: Automated Error Reporting Bot > Assignee: Xavier Coulon > > The following problem was reported via the automated error reporting: > Message: Problems occurred when invoking code from plug-in: "org.eclipse.jdt.core". > {noformat} > java.lang.NullPointerException: null > at org.eclipse.jst.jee.model.internal.WebAnnotationReader.analyzeCompilationUnit(WebAnnotationReader.java:144) > at org.eclipse.jst.jee.model.internal.WebAnnotationReader.processAddedCompilationUnit(WebAnnotationReader.java:257) > at org.eclipse.jst.jee.model.internal.WebAnnotationReader.processChangedCompilationUnit(WebAnnotationReader.java:270) > at org.eclipse.jst.jee.model.internal.common.AbstractAnnotationModelProvider.recursevilyProcessCompilationUnits(AbstractAnnotationModelProvider.java:553) > at org.eclipse.jst.jee.model.internal.common.AbstractAnnotationModelProvider.internalPostReconcile(AbstractAnnotationModelProvider.java:466) > at org.eclipse.jst.jee.model.internal.common.AbstractAnnotationModelProvider.elementChanged(AbstractAnnotationModelProvider.java:446) > at org.eclipse.jdt.internal.core.DeltaProcessor$3.run(DeltaProcessor.java:1662) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.jdt.internal.core.DeltaProcessor.notifyListeners(DeltaProcessor.java:1652) > at org.eclipse.jdt.internal.core.DeltaProcessor.fireReconcileDelta(DeltaProcessor.java:1504) > at org.eclipse.jdt.internal.core.DeltaProcessor.fire(DeltaProcessor.java:1463) > at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:770) > at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:789) > at org.eclipse.jdt.internal.core.CompilationUnit.reconcile(CompilationUnit.java:1250) > at org.eclipse.jdt.internal.core.CompilationUnit.reconcile(CompilationUnit.java:1227) > at org.eclipse.jdt.internal.core.CompilationUnit.reconcile(CompilationUnit.java:1192) > at org.jboss.tools.websockets.ui.internal.ca.SocketProposalComputer.computeCompletionProposals(SocketProposalComputer.java:130) > at org.eclipse.jdt.internal.ui.text.java.CompletionProposalComputerDescriptor.computeCompletionProposals(CompletionProposalComputerDescriptor.java:333) > at org.eclipse.jdt.internal.ui.text.java.CompletionProposalCategory.computeCompletionProposals(CompletionProposalCategory.java:337) > at org.eclipse.jdt.internal.ui.text.java.ContentAssistProcessor.collectProposals(ContentAssistProcessor.java:322) > at org.eclipse.jdt.internal.ui.text.java.ContentAssistProcessor.computeCompletionProposals(ContentAssistProcessor.java:279) > at org.eclipse.jface.text.contentassist.ContentAssistant$5.run(ContentAssistant.java:1904) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.jface.text.contentassist.ContentAssistant.computeCompletionProposals(ContentAssistant.java:1902) > at org.eclipse.jface.text.contentassist.CompletionProposalPopup.computeProposals(CompletionProposalPopup.java:573) > at org.eclipse.jface.text.contentassist.CompletionProposalPopup.access$16(CompletionProposalPopup.java:570) > at org.eclipse.jface.text.contentassist.CompletionProposalPopup$2.run(CompletionProposalPopup.java:505) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at org.eclipse.jface.text.contentassist.CompletionProposalPopup.showProposals(CompletionProposalPopup.java:499) > at org.eclipse.jface.text.contentassist.ContentAssistant$2.run(ContentAssistant.java:384) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4155) > {noformat} > Bundles: > | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.11.1.v20150903-1804 | > | org.eclipse.jdt.core | 3.11.2.v20160128-0629 | 3.11.2.v20160128-0629 | > | org.eclipse.jdt.ui | 3.11.2.v20151123-1510 | 3.11.2.v20151123-1510 | > | org.eclipse.jface.text | 3.10.0.v20150603-1752 | 3.10.0.v20150603-1752 | > | org.eclipse.jst.jee | 1.0.700.v201404092004 | 1.0.700.v201404092004 | > | org.eclipse.swt | 3.104.2.v20160212-1350 | 3.104.2.v20160212-1350 | > | org.jboss.tools.websockets.ui | 1.8.1.Final-v20160331-0952-B76 | 1.8.1.Final-v20160331-0952-B76 | > Operating Systems: > | Windows | 6.1.0 | 6.1.0 | > The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/572b697de4b0a54983...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- 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