October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23404) ClassCastException below ArquillianBuilder.storeProblem (thrown in PackageExplorerContentProvider.handleAffectedChildren)

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23404?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-23404: ---------------------------------- Affects Version/s: 4.4.2.AM2 > ClassCastException below ArquillianBuilder.storeProblem (thrown in PackageExplorerContentProvider.handleAffectedChildren) > ------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23404 > URL: https://issues.jboss.org/browse/JBIDE-23404 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: arquillian > Affects Versions: 4.4.2.AM2 > Reporter: Automated Error Reporting Bot > Fix For: 4.4.2.AM3 > > > The following problem was reported via the automated error reporting: > Message: HIDDEN > java.lang.ClassCastException: HIDDEN > at org.eclipse.wst.jsdt.internal.ui.packageview.PackageExplorerContentProvider.handleAffectedChildren(PackageExplorerContentProvider.java:1275) > at org.eclipse.wst.jsdt.internal.ui.packageview.PackageExplorerContentProvider.processDelta(PackageExplorerContentProvider.java:1118) > at org.eclipse.wst.jsdt.internal.ui.packageview.PackageExplorerContentProvider.handleAffectedChildren(PackageExplorerContentProvider.java:1299) > at org.eclipse.wst.jsdt.internal.ui.packageview.PackageExplorerContentProvider.processDelta(PackageExplorerContentProvider.java:1242) > at org.eclipse.wst.jsdt.internal.ui.packageview.PackageExplorerContentProvider.handleAffectedChildren(PackageExplorerContentProvider.java:1299) > at org.eclipse.wst.jsdt.internal.ui.packageview.PackageExplorerContentProvider.processDelta(PackageExplorerContentProvider.java:1242) > at org.eclipse.wst.jsdt.internal.ui.packageview.PackageExplorerContentProvider.handleAffectedChildren(PackageExplorerContentProvider.java:1299) > at org.eclipse.wst.jsdt.internal.ui.packageview.PackageExplorerContentProvider.processDelta(PackageExplorerContentProvider.java:1242) > at org.eclipse.wst.jsdt.internal.ui.packageview.PackageExplorerContentProvider.elementChanged(PackageExplorerContentProvider.java:131) > at org.eclipse.wst.jsdt.internal.core.DeltaProcessor$3.run(DeltaProcessor.java:1594) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.wst.jsdt.internal.core.DeltaProcessor.notifyListeners(DeltaProcessor.java:1584) > at org.eclipse.wst.jsdt.internal.core.DeltaProcessor.firePostChangeDelta(DeltaProcessor.java:1419) > at org.eclipse.wst.jsdt.internal.core.DeltaProcessor.fire(DeltaProcessor.java:1395) > at org.eclipse.wst.jsdt.internal.core.DeltaProcessor.resourceChanged(DeltaProcessor.java:1948) > at org.eclipse.wst.jsdt.internal.core.DeltaProcessingState.resourceChanged(DeltaProcessingState.java:389) > at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:299) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:289) > at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:152) > at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:374) > at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1469) > at org.eclipse.core.internal.resources.Resource.createMarker(Resource.java:724) > at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.storeProblem(ArquillianBuilder.java:566) > at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.build(ArquillianBuilder.java:386) > at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.buildDelta(ArquillianBuilder.java:222) > at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.build(ArquillianBuilder.java:112) > at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:735) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246) > at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:301) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:304) > at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:360) > at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:383) > at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144) > at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Bundles: > | org.eclipse.core.jobs | 3.8.0.v20160509-0411 | 3.8.0.v20160509-0411 | > | org.eclipse.core.resources | 3.11.0.v20160503-1608 | 3.11.0.v20160503-1608 | > | org.eclipse.core.runtime | 3.12.0.v20160606-1342 | 3.12.0.v20160606-1342 | > | org.eclipse.wst.jsdt.core | 2.0.0.v201605251700 | 2.0.0.v201605251700 | > | org.eclipse.wst.jsdt.ui | 2.0.0.v201605262108 | 2.0.0.v201605262108 | > | org.jboss.tools.arquillian.core | 1.2.100.Final-v20160610-0313-B2 | 1.2.100.Final-v20160610-0313-B2 | > Operating Systems: > | Linux | 4.4.0 | 4.4.0 | > The above information is a snapshot of the collected data. Visit https://aer.ctrlflow.com/redhat/reviewers/#!/problems/580dd560e4b0380483e... 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23404) ClassCastException below ArquillianBuilder.storeProblem (thrown in PackageExplorerContentProvider.handleAffectedChildren)

by Automated Error Reporting Bot (JIRA)

Automated Error Reporting Bot created JBIDE-23404: ----------------------------------------------------- Summary: ClassCastException below ArquillianBuilder.storeProblem (thrown in PackageExplorerContentProvider.handleAffectedChildren) Key: JBIDE-23404 URL: https://issues.jboss.org/browse/JBIDE-23404 Project: Tools (JBoss Tools) Issue Type: Bug Components: arquillian Reporter: Automated Error Reporting Bot The following problem was reported via the automated error reporting: Message: HIDDEN java.lang.ClassCastException: HIDDEN at org.eclipse.wst.jsdt.internal.ui.packageview.PackageExplorerContentProvider.handleAffectedChildren(PackageExplorerContentProvider.java:1275) at org.eclipse.wst.jsdt.internal.ui.packageview.PackageExplorerContentProvider.processDelta(PackageExplorerContentProvider.java:1118) at org.eclipse.wst.jsdt.internal.ui.packageview.PackageExplorerContentProvider.handleAffectedChildren(PackageExplorerContentProvider.java:1299) at org.eclipse.wst.jsdt.internal.ui.packageview.PackageExplorerContentProvider.processDelta(PackageExplorerContentProvider.java:1242) at org.eclipse.wst.jsdt.internal.ui.packageview.PackageExplorerContentProvider.handleAffectedChildren(PackageExplorerContentProvider.java:1299) at org.eclipse.wst.jsdt.internal.ui.packageview.PackageExplorerContentProvider.processDelta(PackageExplorerContentProvider.java:1242) at org.eclipse.wst.jsdt.internal.ui.packageview.PackageExplorerContentProvider.handleAffectedChildren(PackageExplorerContentProvider.java:1299) at org.eclipse.wst.jsdt.internal.ui.packageview.PackageExplorerContentProvider.processDelta(PackageExplorerContentProvider.java:1242) at org.eclipse.wst.jsdt.internal.ui.packageview.PackageExplorerContentProvider.elementChanged(PackageExplorerContentProvider.java:131) at org.eclipse.wst.jsdt.internal.core.DeltaProcessor$3.run(DeltaProcessor.java:1594) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.wst.jsdt.internal.core.DeltaProcessor.notifyListeners(DeltaProcessor.java:1584) at org.eclipse.wst.jsdt.internal.core.DeltaProcessor.firePostChangeDelta(DeltaProcessor.java:1419) at org.eclipse.wst.jsdt.internal.core.DeltaProcessor.fire(DeltaProcessor.java:1395) at org.eclipse.wst.jsdt.internal.core.DeltaProcessor.resourceChanged(DeltaProcessor.java:1948) at org.eclipse.wst.jsdt.internal.core.DeltaProcessingState.resourceChanged(DeltaProcessingState.java:389) at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:299) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:289) at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:152) at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:374) at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1469) at org.eclipse.core.internal.resources.Resource.createMarker(Resource.java:724) at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.storeProblem(ArquillianBuilder.java:566) at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.build(ArquillianBuilder.java:386) at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.buildDelta(ArquillianBuilder.java:222) at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.build(ArquillianBuilder.java:112) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:735) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:301) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:304) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:360) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:383) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Bundles: | org.eclipse.core.jobs | 3.8.0.v20160509-0411 | 3.8.0.v20160509-0411 | | org.eclipse.core.resources | 3.11.0.v20160503-1608 | 3.11.0.v20160503-1608 | | org.eclipse.core.runtime | 3.12.0.v20160606-1342 | 3.12.0.v20160606-1342 | | org.eclipse.wst.jsdt.core | 2.0.0.v201605251700 | 2.0.0.v201605251700 | | org.eclipse.wst.jsdt.ui | 2.0.0.v201605262108 | 2.0.0.v201605262108 | | org.jboss.tools.arquillian.core | 1.2.100.Final-v20160610-0313-B2 | 1.2.100.Final-v20160610-0313-B2 | Operating Systems: | Linux | 4.4.0 | 4.4.0 | The above information is a snapshot of the collected data. Visit https://aer.ctrlflow.com/redhat/reviewers/#!/problems/580dd560e4b0380483e... 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-799) Fuse: Check availability of component/attributes according to Camel version

by Dominik Jelinek (JIRA)

[ https://issues.jboss.org/browse/JBTIS-799?page=com.atlassian.jira.plugin.... ] Dominik Jelinek commented on JBTIS-799: --------------------------------------- Yes, I'm working at this part of test right now > Fuse: Check availability of component/attributes according to Camel version > --------------------------------------------------------------------------- > > Key: JBTIS-799 > URL: https://issues.jboss.org/browse/JBTIS-799 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.3.1.Final > Reporter: Tomáš Sedmík > Assignee: Dominik Jelinek > Priority: Critical > > # create a Fuse project with Camel version set to _2.15.1.redhat-621084_ > # create a Fuse project with Camel version set to _2.17.0.redhat-630077_ > # check whether in Camel editor of both projects are available components/attributes supported by selected Camel version > Example: > XSLT component should have attribute _uriResolverFactory_ in _2.17_ but not in _2.15_ (see http://camel.apache.org/xslt.html) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-799) Fuse: Check availability of component/attributes according to Camel version

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-799?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík commented on JBTIS-799: ------------------------------------ [~djelinek] I presume this will be a part of your tests. Am I right? > Fuse: Check availability of component/attributes according to Camel version > --------------------------------------------------------------------------- > > Key: JBTIS-799 > URL: https://issues.jboss.org/browse/JBTIS-799 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.3.1.Final > Reporter: Tomáš Sedmík > Assignee: Dominik Jelinek > Priority: Critical > > # create a Fuse project with Camel version set to _2.15.1.redhat-621084_ > # create a Fuse project with Camel version set to _2.17.0.redhat-630077_ > # check whether in Camel editor of both projects are available components/attributes supported by selected Camel version > Example: > XSLT component should have attribute _uriResolverFactory_ in _2.17_ but not in _2.15_ (see http://camel.apache.org/xslt.html) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-799) Fuse: Check availability of component/attributes according to Camel version

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-799?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík reassigned JBTIS-799: ---------------------------------- Assignee: Dominik Jelinek (was: Tomáš Sedmík) > Fuse: Check availability of component/attributes according to Camel version > --------------------------------------------------------------------------- > > Key: JBTIS-799 > URL: https://issues.jboss.org/browse/JBTIS-799 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.3.1.Final > Reporter: Tomáš Sedmík > Assignee: Dominik Jelinek > Priority: Critical > > # create a Fuse project with Camel version set to _2.15.1.redhat-621084_ > # create a Fuse project with Camel version set to _2.17.0.redhat-630077_ > # check whether in Camel editor of both projects are available components/attributes supported by selected Camel version > Example: > XSLT component should have attribute _uriResolverFactory_ in _2.17_ but not in _2.15_ (see http://camel.apache.org/xslt.html) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-739) Fuse: Add test for space and special characters in the path

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-739?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík updated JBTIS-739: ------------------------------- Original Estimate: 1 hour Remaining Estimate: 1 hour > Fuse: Add test for space and special characters in the path > ----------------------------------------------------------- > > Key: JBTIS-739 > URL: https://issues.jboss.org/browse/JBTIS-739 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.3.0.Final > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Priority: Critical > Fix For: 4.3.1.Final > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > https://issues.jboss.org/browse/FUSETOOLS-1647 > https://issues.jboss.org/browse/FUSETOOLS-1668 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23402) [WATCHER] Explorer: can "Deploy Latest" even if the build failed

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23402?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23402: ------------------------------------------ [~rob.stryker] dare to file an issue again origin since you have the most infos? > [WATCHER] Explorer: can "Deploy Latest" even if the build failed > ---------------------------------------------------------------- > > Key: JBIDE-23402 > URL: https://issues.jboss.org/browse/JBIDE-23402 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.4.2.AM2 > Reporter: Andre Dietisheim > Fix For: 4.4.x > > Attachments: JBIDE-23402-a.png, JBIDE-23402-b.png > > > When right-clicking on an application, we can select "Deploy Latest". This will start both a build and a deploy pod. The deploy pod will wait for the build pod to complete. > In this case, due to github being unavailable, the build pod will fail very quickly. The deploy pod will then continue waiting up to 10 minutes even though what it is waiting for has already failed. This 10 minutes is wasted. It should fail quickly. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4070) DevStudio / external OpenShift fails deployment

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-4070?page=com.atlassian.jira.plugin.... ] Andre Dietisheim closed JBDS-4070. ---------------------------------- Nothing for QE to verify, we dont have enough infos. > DevStudio / external OpenShift fails deployment > ----------------------------------------------- > > Key: JBDS-4070 > URL: https://issues.jboss.org/browse/JBDS-4070 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: openshift > Affects Versions: 10.1.0.GA > Environment: DevStudio as used with an external OpenShift > Reporter: Rick Wagner > Assignee: Jeff MAURY > Labels: openshift_v3 > Fix For: 10.2.0.AM3 > > Attachments: eap-app-server-adapter-publish.png, eap-app-server-adapter-settings.png, kitchensink-ear-deployed-succcessfully.png, kitchensink-ear-projects.png, new-openshift-server-adapter.png > > > If DevStudio (with Server Adapter configured for external OpenShift) is used to deploy an application developed in DevStudio, errors result. > The reporting user shows indications additional 'deploy' directories are being synthesized as the binary target location. The log reports: > 15:59:41,588 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) WFLYDS0010: Scan found incompletely copied file content for deployment /opt/eap/standalone/deployments/deploy/deploy/deploy/deploy/deploy/deploy/activemq-rar.rar. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4070) DevStudio / external OpenShift fails deployment

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-4070?page=com.atlassian.jira.plugin.... ] Andre Dietisheim resolved JBDS-4070. ------------------------------------ Resolution: Rejected Rejecting this issue since I cant replicate it and dont have enough infos. [~rick_wagner] please feel free to reopen this if you have more infos. > DevStudio / external OpenShift fails deployment > ----------------------------------------------- > > Key: JBDS-4070 > URL: https://issues.jboss.org/browse/JBDS-4070 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: openshift > Affects Versions: 10.1.0.GA > Environment: DevStudio as used with an external OpenShift > Reporter: Rick Wagner > Assignee: Jeff MAURY > Labels: openshift_v3 > Fix For: 10.2.0.AM3 > > Attachments: eap-app-server-adapter-publish.png, eap-app-server-adapter-settings.png, kitchensink-ear-deployed-succcessfully.png, kitchensink-ear-projects.png, new-openshift-server-adapter.png > > > If DevStudio (with Server Adapter configured for external OpenShift) is used to deploy an application developed in DevStudio, errors result. > The reporting user shows indications additional 'deploy' directories are being synthesized as the binary target location. The log reports: > 15:59:41,588 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) WFLYDS0010: Scan found incompletely copied file content for deployment /opt/eap/standalone/deployments/deploy/deploy/deploy/deploy/deploy/deploy/activemq-rar.rar. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4070) DevStudio / external OpenShift fails deployment

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-4070?page=com.atlassian.jira.plugin.... ] Andre Dietisheim edited comment on JBDS-4070 at 10/24/16 6:15 AM: ------------------------------------------------------------------ [~rick_wagner] no probs, I'm just trying to figure we're talking of the same thing. But it's not an app-server, it's the server adapter in Eclipse, which is nothing but a tool to publish local code to some server, the pod in OpenShift in this particular case. We really need more and more precise info to be able to replicate, identify and fix issues. In my current guesswork I'm stuck. I cant replicate this and thus have no idea what really happens. I searched in the OpenShift bugzila (and googled for such problems in plain rsync) but couldnt find any such report. [~jcantrill] Can you please chime and tell us if such thing is known to the openshift team? was (Author: adietish): I searched in the OpenShift bugzila (and googled for such problems in plain rsync) but couldnt find any such report. [~jcantrill] Can you please chime and tell us if such thing is known to the openshift team? > DevStudio / external OpenShift fails deployment > ----------------------------------------------- > > Key: JBDS-4070 > URL: https://issues.jboss.org/browse/JBDS-4070 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: openshift > Affects Versions: 10.1.0.GA > Environment: DevStudio as used with an external OpenShift > Reporter: Rick Wagner > Assignee: Jeff MAURY > Labels: openshift_v3 > Fix For: 10.2.0.AM3 > > Attachments: eap-app-server-adapter-publish.png, eap-app-server-adapter-settings.png, kitchensink-ear-deployed-succcessfully.png, kitchensink-ear-projects.png, new-openshift-server-adapter.png > > > If DevStudio (with Server Adapter configured for external OpenShift) is used to deploy an application developed in DevStudio, errors result. > The reporting user shows indications additional 'deploy' directories are being synthesized as the binary target location. The log reports: > 15:59:41,588 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) WFLYDS0010: Scan found incompletely copied file content for deployment /opt/eap/standalone/deployments/deploy/deploy/deploy/deploy/deploy/deploy/activemq-rar.rar. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 2016