May 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24244) add fuse tools features to JBT core, coretests, integration-tests update sites (as appropriate)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24244?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24244: ------------------------------------ I'll add the latest Fuse CI build [0] to the list of composite sites [1] to merge into JBoss Tools aggregate site [2]. [0] http://download.jboss.org/jbosstools/oxygen/snapshots/builds/jbosstools-f... [1] http://download.jboss.org/jbosstools/oxygen/snapshots/builds/_composite_/... [2] https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... > add fuse tools features to JBT core, coretests, integration-tests update sites (as appropriate) > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-24244 > URL: https://issues.jboss.org/browse/JBIDE-24244 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, fuse-tooling, updatesite > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Lars Heinemann > Fix For: 4.5.0.AM1 > > > Need a list of features to include in JBT, and how to categorize them. > See: > * See https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... for Core site > * See https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... for Core tests site > * See https://github.com/jbosstools/jbosstools-integration-tests/blob/master/si... for integration tests site -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4416) Update description on RPM download site

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4416?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4416: ---------------------------------- PR replaced by https://github.com/jbdevstudio/jbdevstudio-product/commit/79d667931e6aab0... and https://github.com/jbdevstudio/jbdevstudio-product/commit/fc2504f3ca91f93... > Update description on RPM download site > --------------------------------------- > > Key: JBDS-4416 > URL: https://issues.jboss.org/browse/JBDS-4416 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: rpm > Affects Versions: 11.0.0.AM1 > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 11.0.0.AM1 > > > Need to update description at RPM download site \[1\] for 11.x. > \[1\] https://devstudio.jboss.com/11/snapshots/rpms/11.0.0/x86_64/ > cc: [~nickboldt] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21857) Hot code replacement doesn't work on OpenShift

by Thomas Mäder (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ] Thomas Mäder commented on JBIDE-21857: -------------------------------------- After looking at this, I believe that this is not a problem with the behavior of our tooling, but in EAP. Here's what I did: 1. I was able to verify that Runtime.gc() is reliably called twice after the reload of the module 2. I can reproduce the problem by running the jboss-kitchensink example and by putting a breakpoint in MemberRepository.findAllOrderedByName both locally (eap 6.4 and 7.0) and on openshift (eap 7.0). Therefore it's likely NOT openshift tooling specific. 3. When I look at heap dumps from after a couple of times reproducing the problem, I see that there are references to an instance of MemberController in a ThreadLocal for each time I try to do HCR. 4. When I let the request I am in run to completion and then suspend the request thread, the thread local still references the MemberController instance. I suspect that the HCR leads to an exception and that the ThreadLocal is not properly cleaned up. I don't stand a chance of debugging the apparent EAP problem in a reasonable time. I suggest involving an expert on EAP/Wildfly. > Hot code replacement doesn't work on OpenShift > ---------------------------------------------- > > Key: JBIDE-21857 > URL: https://issues.jboss.org/browse/JBIDE-21857 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Rob Stryker > Fix For: 4.5.0.AM1 > > Attachments: HCRFailure.zip, code-out-of-sync.png, hot-code-replace-failed.png, jmx-connected-adapter-synchronized.png > > > When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will : > - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync > - will always fail if a method signature changed, the debugger saying JDK is out of sync > Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server) > This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24381) jbosstools aggregate update site being deployed to nexus

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24381?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24381: ------------------------------------ Yes, there's no need for these artifacts to be in there. Won't they be auto-cleaned at some point anyway? > jbosstools aggregate update site being deployed to nexus > -------------------------------------------------------- > > Key: JBIDE-24381 > URL: https://issues.jboss.org/browse/JBIDE-24381 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM1 > > > Despite setting maven.deploy.skip=true, the JBT aggregate update site is being pushed to Nexus, which wastes 4 mins an a bunch of space in Nexus: > {code} > 10:28:46 [INFO] Deploying remotely... > 10:28:46 [INFO] Bulk deploying locally gathered artifacts from directory: > 10:28:46 [INFO] * Bulk deploying locally gathered snapshot artifacts > 10:28:46 [INFO] Downloading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > 10:28:47 [INFO] Downloaded: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... (2 KB at 3.7 KB/sec) > 10:28:47 [INFO] Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > 10:32:42 [INFO] Uploaded: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... (522353 KB at 2215.2 KB/sec) > 10:32:42 [INFO] Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > 10:32:43 [INFO] Uploaded: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... (10 KB at 28.7 KB/sec) > 10:32:43 [INFO] Downloading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > 10:32:43 [INFO] Downloaded: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... (400 B at 0.9 KB/sec) > 10:32:43 [INFO] Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > 10:32:44 [INFO] Uploaded: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... (2 KB at 2.8 KB/sec) > 10:32:44 [INFO] Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > 10:32:44 [INFO] Uploaded: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... (400 B at 1.0 KB/sec) > 10:32:44 [INFO] Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > 10:32:44 [INFO] Uploaded: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... (48 KB at 105.8 KB/sec) > 10:32:44 [INFO] Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > 10:32:45 [INFO] Uploaded: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... (2 KB at 3.0 KB/sec) > 10:32:45 [INFO] Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > 10:32:45 [INFO] Uploaded: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... (100 B at 0.3 KB/sec) > 10:32:45 [INFO] Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > 10:32:46 [INFO] Uploaded: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... (2 KB at 3.0 KB/sec) > 10:32:46 [INFO] * Bulk deploy of locally gathered snapshot artifacts finished. > 10:32:46 [INFO] Remote deploy finished with success.{code} > -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4403) An error when installing Devstudio 10.4.0.GA from Marketplace

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4403?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4403: ---------------------------------- +1, looks great. > An error when installing Devstudio 10.4.0.GA from Marketplace > ------------------------------------------------------------- > > Key: JBDS-4403 > URL: https://issues.jboss.org/browse/JBDS-4403 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: marketplace > Affects Versions: 10.4.0.GA > Environment: Eclipse Neon.3 for JavaEE Developers > Reporter: Andrej Podhradsky > Assignee: Nick Boldt > Fix For: 10.4.0.GA > > > The following error occurs when installing Devstudio 10.4.0.GA from Marketplace > {code} > Cannot complete the install because of a conflicting dependency. > Software being installed: Red Hat JBoss Developer Studio (Core Features) 10.4.0.v20170511-1748 (com.jboss.devstudio.core.feature.feature.group 10.4.0.v20170511-1748) > Software currently installed: m2e - Maven Integration for Eclipse (includes Incubating components) 1.7.0.20160603-1933 (org.eclipse.m2e.feature.feature.group 1.7.0.20160603-1933) > Only one of the following can be installed at once: > Maven Project Model Edit Bundle 1.7.0.20160603-1933 (org.eclipse.m2e.model.edit 1.7.0.20160603-1933) > Maven Project Model Edit Bundle 1.7.1.20161104-1805 (org.eclipse.m2e.model.edit 1.7.1.20161104-1805) > Cannot satisfy dependency: > From: Red Hat JBoss Developer Studio (Core Features) 10.4.0.v20170511-1748 (com.jboss.devstudio.core.feature.feature.group 10.4.0.v20170511-1748) > To: com.jboss.devstudio.core.rpmdeps.feature.feature.group [10.4.0.v20170504-1343] > Cannot satisfy dependency: > From: Red Hat JBoss Developer Studio (Feature Dependencies) 10.4.0.v20170504-1343 (com.jboss.devstudio.core.rpmdeps.feature.feature.group 10.4.0.v20170504-1343) > To: org.eclipse.m2e.feature.feature.group 1.7.1.20161104-1805 > Cannot satisfy dependency: > From: m2e - Maven Integration for Eclipse (includes Incubating components) 1.7.0.20160603-1933 (org.eclipse.m2e.feature.feature.group 1.7.0.20160603-1933) > To: org.eclipse.m2e.model.edit [1.7.0.20160603-1933] > Cannot satisfy dependency: > From: m2e - Maven Integration for Eclipse (includes Incubating components) 1.7.1.20161104-1805 (org.eclipse.m2e.feature.feature.group 1.7.1.20161104-1805) > To: org.eclipse.m2e.model.edit [1.7.1.20161104-1805] > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4237) Generate CVE vulnerability report for devstudio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4237?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4237: ----------------------------- Fix Version/s: 11.0.0.AM2 (was: 11.0.0.AM1) > Generate CVE vulnerability report for devstudio > ----------------------------------------------- > > Key: JBDS-4237 > URL: https://issues.jboss.org/browse/JBDS-4237 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, versionwatch > Affects Versions: 10.3.0.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 11.0.0.AM2 > > Attachments: CVE-report.png, Screenshot_2017-01-10_18-58-03.png, Screenshot_2017-01-10_19-04-45.png > > > 0. download http://dl.bintray.com/jeremy-long/owasp/dependency-check-1.4.4-release.zip > 1. download latest CI build update site zip, target platform zip, central zip, etc. > 2. unpack update site zips > 3. unpack dep-check zip > 4. generate CVE report for each fetched zip: > {code} > ./dependency-check.sh --disableAssembly -s /path/to/update-site/plugins/ --project devstudio_check -o WORKSPACE/path/to/report/folder/ > {code} > Should use https://wiki.jenkins-ci.org/display/JENKINS/OWASP+Dependency-Check+Plugin for better reporting and maybe even enable this on every project job (once moved to CCI Jenkins). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4237) Generate CVE vulnerability report for devstudio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4237?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4237: ----------------------------- Attachment: CVE-report.png > Generate CVE vulnerability report for devstudio > ----------------------------------------------- > > Key: JBDS-4237 > URL: https://issues.jboss.org/browse/JBDS-4237 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, versionwatch > Affects Versions: 10.3.0.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 11.0.0.AM1 > > Attachments: CVE-report.png, Screenshot_2017-01-10_18-58-03.png, Screenshot_2017-01-10_19-04-45.png > > > 0. download http://dl.bintray.com/jeremy-long/owasp/dependency-check-1.4.4-release.zip > 1. download latest CI build update site zip, target platform zip, central zip, etc. > 2. unpack update site zips > 3. unpack dep-check zip > 4. generate CVE report for each fetched zip: > {code} > ./dependency-check.sh --disableAssembly -s /path/to/update-site/plugins/ --project devstudio_check -o WORKSPACE/path/to/report/folder/ > {code} > Should use https://wiki.jenkins-ci.org/display/JENKINS/OWASP+Dependency-Check+Plugin for better reporting and maybe even enable this on every project job (once moved to CCI Jenkins). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4237) Generate CVE vulnerability report for devstudio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4237?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-4237 at 5/31/17 10:11 AM: ------------------------------------------------------------ Updated CVE report to use devstudio 11 and latest TP. https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/All/job... !CVE-report.png|thumbnail! was (Author: nickboldt): Updated CVE report to use devstudio 11 and latest TP. https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/All/job... ... running.... > Generate CVE vulnerability report for devstudio > ----------------------------------------------- > > Key: JBDS-4237 > URL: https://issues.jboss.org/browse/JBDS-4237 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, versionwatch > Affects Versions: 10.3.0.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 11.0.0.AM1 > > Attachments: CVE-report.png, Screenshot_2017-01-10_18-58-03.png, Screenshot_2017-01-10_19-04-45.png > > > 0. download http://dl.bintray.com/jeremy-long/owasp/dependency-check-1.4.4-release.zip > 1. download latest CI build update site zip, target platform zip, central zip, etc. > 2. unpack update site zips > 3. unpack dep-check zip > 4. generate CVE report for each fetched zip: > {code} > ./dependency-check.sh --disableAssembly -s /path/to/update-site/plugins/ --project devstudio_check -o WORKSPACE/path/to/report/folder/ > {code} > Should use https://wiki.jenkins-ci.org/display/JENKINS/OWASP+Dependency-Check+Plugin for better reporting and maybe even enable this on every project job (once moved to CCI Jenkins). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4237) Generate CVE vulnerability report for devstudio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4237?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4237: ---------------------------------- Updated CVE report to use devstudio 11 and latest TP. https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/All/job... ... running.... > Generate CVE vulnerability report for devstudio > ----------------------------------------------- > > Key: JBDS-4237 > URL: https://issues.jboss.org/browse/JBDS-4237 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, versionwatch > Affects Versions: 10.3.0.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 11.0.0.AM1 > > Attachments: Screenshot_2017-01-10_18-58-03.png, Screenshot_2017-01-10_19-04-45.png > > > 0. download http://dl.bintray.com/jeremy-long/owasp/dependency-check-1.4.4-release.zip > 1. download latest CI build update site zip, target platform zip, central zip, etc. > 2. unpack update site zips > 3. unpack dep-check zip > 4. generate CVE report for each fetched zip: > {code} > ./dependency-check.sh --disableAssembly -s /path/to/update-site/plugins/ --project devstudio_check -o WORKSPACE/path/to/report/folder/ > {code} > Should use https://wiki.jenkins-ci.org/display/JENKINS/OWASP+Dependency-Check+Plugin for better reporting and maybe even enable this on every project job (once moved to CCI Jenkins). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24121) Update versionwatch for devstudio 11 - document/update known multiples & report upstream problems to Eclipse CVS, Help, WST

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24121?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24121: ------------------------------------ Now that we're on Oxygen.0.M7, I've updated the known issues list to include these IU versions: {code} com.google.guava=[15.0.0,21.0.0] javax.wsdl=[1.5.1,1.6.2] org.apache.commons.logging=[1.0.4,1.1.1] org.eclipse.jdt.annotation=[1.1.100,2.1] org.objectweb.asm.tree=[5.0.1,5.2] org.objectweb.asm=[5.0.1,5.2.0] # should this be allowed? org.apache.lucene.core=[3.5,6.1] {code} -- https://github.com/jbosstools/jbosstools-versionwatch/blob/3f8d26c83b6344... > Update versionwatch for devstudio 11 - document/update known multiples & report upstream problems to Eclipse CVS, Help, WST > --------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24121 > URL: https://issues.jboss.org/browse/JBIDE-24121 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, qa, versionwatch > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM1 > > Attachments: Screenshot_2017-03-21_12-37-07.png, version-decreased.png > > > {code} > Version Watch - Summary Report: devstudio-11.0.0.AM1 > Multiple version issues > Feature Problem Reference Version(s) > Plugin Problem Reference Version(s) > org.slf4j.api Multiple versions of same bundle found! 1.7.2.v20121108-1250 1.7.10.v20160921-1923 > org.apache.httpcomponents.httpcore Multiple versions of same bundle found! 4.3.3.v201411290715 4.4.4.v20161115-1643 > org.apache.httpcomponents.httpclient Multiple versions of same bundle found! 4.3.6.v201511171540 4.5.2.v20161115-1643 > Ignored (known issue) > org.apache.lucene.core Multiple versions of bundle are expected and ignored - {3.5.0,5.4.1} 3.5.0.v20120725-1805 6.1.0.v20161115-1612 > javax.wsdl Multiple versions of bundle are expected and ignored - {1.5.1,1.6.2} 1.5.1.v201012040544 1.6.2.v201012040545 > com.jcraft.jsch Multiple versions of bundle are expected and ignored - {0.1.50,0.1.51} 0.1.53.v201508180515 0.1.54.v20170116-1932 > org.eclipse.jdt.annotation Multiple versions of bundle are expected and ignored - {1.1.0,2.1.0} 1.1.100.v20160418-1457 2.1.0.v20170119-1701 > org.objectweb.asm Multiple versions of bundle are expected and ignored - {4.0.0,5.0.1} 4.0.0.v201302062210 5.0.1.v201404251740 > org.apache.commons.logging Multiple versions of bundle are expected and ignored - {1.0.4,1.1.1} 1.0.4.v201101211617 1.1.1.v201101211721 > com.google.guava Multiple versions of bundle are expected and ignored - 13.0.0,15.0.0 15.0.0.v201403281430 18.0.0.v20161115-1643 > Version decreased issues > Feature Problem Reference Version(s) > org.eclipse.cvs Version 1.4.300.v20170126-1030 must be higher than 1.4.301.v20161124-1400 1.4.301.v20161124-1400 > org.eclipse.help Version 2.2.0.v20170126-1030 must be higher than 2.2.1.v20161124-1400 2.2.1.v20161124-1400 > Plugin Problem Reference Version(s) > org.eclipse.cvs Version 1.4.300.v20170126-1030 must be higher than 1.4.301.v20161124-1400 1.4.301.v20161124-1400 > org.eclipse.wst.server.ui Version 1.5.306.v201610202117 must be higher than 1.5.307.v201611072017 1.5.307.v201611072017 > > 7 issues found.{code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 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 2017