December 2017 - jbosstools-issues

[JBoss JIRA] (JBDS-4613) Reduce CVE vulnerabilities in devstudio 11.2

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBDS-4613?page=com.atlassian.jira.plugin.... ] Jeff MAURY updated JBDS-4613: ----------------------------- Sprint: devex #142 December 2017 > Reduce CVE vulnerabilities in devstudio 11.2 > -------------------------------------------- > > Key: JBDS-4613 > URL: https://issues.jboss.org/browse/JBDS-4613 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Epic > Components: 3rd-party-certification, 3rd-party-dependencies, upstream > Affects Versions: 11.1.0.GA > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 11.2.0.AM3 > > > The list of CVE vulnerabilities has been steadily increasing in both 3rd party deps and even some org.jboss.tools plugins since Jan 2017. > Is it time to do something about this, or should we just keep logging the volume of problems? > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... - *2658 warnings* > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... - *1508 warnings* -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4613) Reduce CVE vulnerabilities in devstudio 11.2

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBDS-4613?page=com.atlassian.jira.plugin.... ] Jeff MAURY commented on JBDS-4613: ---------------------------------- Will process next sprint > Reduce CVE vulnerabilities in devstudio 11.2 > -------------------------------------------- > > Key: JBDS-4613 > URL: https://issues.jboss.org/browse/JBDS-4613 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Epic > Components: 3rd-party-certification, 3rd-party-dependencies, upstream > Affects Versions: 11.1.0.GA > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 11.2.0.AM3 > > > The list of CVE vulnerabilities has been steadily increasing in both 3rd party deps and even some org.jboss.tools plugins since Jan 2017. > Is it time to do something about this, or should we just keep logging the volume of problems? > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... - *2658 warnings* > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... - *1508 warnings* -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25454) Automate test of BYOE installation from installer jar

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25454?page=com.atlassian.jira.plugi... ] Lukáš Valach closed JBIDE-25454. -------------------------------- > Automate test of BYOE installation from installer jar > ----------------------------------------------------- > > Key: JBIDE-25454 > URL: https://issues.jboss.org/browse/JBIDE-25454 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.5.2.AM3 > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 4.5.2.AM3 > > > Having this automated will save me some time. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25453) Automate RD Central test against JBossTools

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25453?page=com.atlassian.jira.plugi... ] Lukáš Valach closed JBIDE-25453. -------------------------------- > Automate RD Central test against JBossTools > -------------------------------------------- > > Key: JBIDE-25453 > URL: https://issues.jboss.org/browse/JBIDE-25453 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.5.2.AM3 > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 4.5.2.AM3 > > > Recently we discovered problem installing all the stuff from RH Central at once. This problem affect only JBossTools. This bug was found because I am testing Central upon JBossTools manually. This process takes some time so it will be nice have it automated. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1190) Teiid throwns an AssertionFailedException when running against Devstudio RPM

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1190?page=com.atlassian.jira.plugin... ] Lukáš Valach closed JBTIS-1190. ------------------------------- Resolution: Won't Fix I tried it again in 11.2.0.AM2. The exception still appears in the log of automated test, but I can't reproduce it locally. I also tried to install "JBoss Data Virtualization Development" by hands on VM at OpenStack (on the same environment as used for automated testing), but I didn't reproducet this error. I compared rpm packages installed on my (hand make) system and on system prepared by jenkins test, but I didn't found any difference. Also content of ~/.eclipse is almost the same. Finaly, I tested Teiid on system produced by Jenkins. It seems that Teiid works fine, so I think we can ignore this error message and close this jira. > Teiid throwns an AssertionFailedException when running against Devstudio RPM > ----------------------------------------------------------------------------- > > Key: JBTIS-1190 > URL: https://issues.jboss.org/browse/JBTIS-1190 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: teiid > Affects Versions: 11.1.0.Beta1b > Environment: * Devstudio repo: https://devstudio.redhat.com/11/staging/builds/devstudio-11.2.0.AM1-build... > * DevTools repo: http://brewweb.engineering.redhat.com/brewroot/repos/devtools-2.1-rh-ecli... > * RHEL7 > Reporter: Lukáš Valach > Assignee: Andrej Podhradsky > Fix For: 11.1.0.CR1 > > Attachments: Teiid_AssertionFailedException.log > > > I installed Devstudio RPM 11.2.0.AM1 and then "JBoss Data Virtualization Development" from RH Central. After restart this error appeared in the log: > {code} > !ENTRY org.eclipse.equinox.p2.publisher 4 0 2017-11-20 04:45:17.459 > !MESSAGE An error occured while parsing advice file: basePath=/home/hudson/.eclipse/org.eclipse.platform_1565164387_linux_gtk_x86_64/features/org.teiid.designer.teiid.client.feature_11.1.1.v20171023-1407, adviceFilePath=p2.inf. > !STACK 0 > org.eclipse.core.runtime.AssertionFailedException: null argument: > at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:85) > at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:73) > at org.eclipse.equinox.internal.p2.metadata.RequiredCapability.<init>(RequiredCapability.java:104) > at org.eclipse.equinox.p2.metadata.MetadataFactory.createRequirement(MetadataFactory.java:465) > at org.eclipse.equinox.p2.publisher.AdviceFileParser.createRequirement(AdviceFileParser.java:318) > at org.eclipse.equinox.p2.publisher.AdviceFileParser.parseRequired(AdviceFileParser.java:292) > at org.eclipse.equinox.p2.publisher.AdviceFileParser.parseRequires(AdviceFileParser.java:244) > at org.eclipse.equinox.p2.publisher.AdviceFileParser.parse(AdviceFileParser.java:110) > at org.eclipse.equinox.p2.publisher.AdviceFileAdvice.<init>(AdviceFileAdvice.java:78) > at org.eclipse.equinox.p2.publisher.eclipse.FeaturesAction.createAdviceFileAdvice(FeaturesAction.java:166) > at org.eclipse.equinox.p2.publisher.eclipse.FeaturesAction.generateFeatureIUs(FeaturesAction.java:407) > at org.eclipse.equinox.p2.publisher.eclipse.FeaturesAction.perform(FeaturesAction.java:605) > at org.eclipse.equinox.internal.provisional.p2.directorywatcher.RepositoryListener.publish(RepositoryListener.java:160) > at org.eclipse.equinox.internal.provisional.p2.directorywatcher.RepositoryListener.processFeature(RepositoryListener.java:155) > at org.eclipse.equinox.internal.provisional.p2.directorywatcher.RepositoryListener.process(RepositoryListener.java:133) > at org.eclipse.equinox.internal.provisional.p2.directorywatcher.RepositoryListener.added(RepositoryListener.java:117) > at org.eclipse.equinox.internal.provisional.p2.directorywatcher.DirectoryWatcher.processFile(DirectoryWatcher.java:197) > at org.eclipse.equinox.internal.provisional.p2.directorywatcher.DirectoryWatcher.scanDirectories(DirectoryWatcher.java:160) > at org.eclipse.equinox.internal.provisional.p2.directorywatcher.DirectoryWatcher.poll(DirectoryWatcher.java:108) > at org.eclipse.equinox.internal.p2.extensionlocation.SiteListener.synchronizeRepositories(SiteListener.java:111) > at org.eclipse.equinox.internal.p2.extensionlocation.ExtensionLocationArtifactRepository.ensureInitialized(ExtensionLocationArtifactRepository.java:66) > at org.eclipse.equinox.internal.p2.extensionlocation.ExtensionLocationArtifactRepository.getProperties(ExtensionLocationArtifactRepository.java:259) > at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.addRepository(AbstractRepositoryManager.java:129) > at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:674) > at org.eclipse.equinox.internal.p2.artifact.repository.ArtifactRepositoryManager.loadRepository(ArtifactRepositoryManager.java:104) > at org.eclipse.equinox.internal.p2.artifact.repository.ArtifactRepositoryManager.loadRepository(ArtifactRepositoryManager.java:100) > at org.eclipse.equinox.internal.p2.touchpoint.eclipse.Util.getRunnableRepositories(Util.java:161) > at org.eclipse.equinox.internal.p2.touchpoint.eclipse.Util.getAggregatedBundleRepository(Util.java:153) > at org.eclipse.equinox.internal.p2.extensionlocation.Activator.getBundlePoolRepository(Activator.java:88) > at org.eclipse.equinox.internal.p2.extensionlocation.BundlePoolFilteredListener.<init>(BundlePoolFilteredListener.java:29) > at org.eclipse.equinox.internal.p2.extensionlocation.SiteListener.synchronizeRepositories(SiteListener.java:109) > at org.eclipse.equinox.internal.p2.extensionlocation.ExtensionLocationMetadataRepository.ensureInitialized(ExtensionLocationMetadataRepository.java:65) > at org.eclipse.equinox.internal.p2.extensionlocation.ExtensionLocationMetadataRepository.getProperties(ExtensionLocationMetadataRepository.java:193) > at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.addRepository(AbstractRepositoryManager.java:129) > at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.addRepository(MetadataRepositoryManager.java:37) > at org.eclipse.equinox.internal.p2.reconciler.dropins.Activator.createExtensionLocationMetadataRepository(Activator.java:81) > at org.eclipse.equinox.internal.p2.reconciler.dropins.PlatformXmlListener.synchronizeConfiguration(PlatformXmlListener.java:236) > at org.eclipse.equinox.internal.p2.reconciler.dropins.PlatformXmlListener.stopPoll(PlatformXmlListener.java:132) > at org.eclipse.equinox.internal.provisional.p2.directorywatcher.DirectoryWatcher.stopPoll(DirectoryWatcher.java:171) > at org.eclipse.equinox.internal.provisional.p2.directorywatcher.DirectoryWatcher.poll(DirectoryWatcher.java:109) > at org.eclipse.equinox.internal.p2.reconciler.dropins.Activator.watchConfiguration(Activator.java:519) > at org.eclipse.equinox.internal.p2.reconciler.dropins.Activator.start(Activator.java:175) > at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:779) > at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1) > at java.security.AccessController.doPrivileged(Native Method) > at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:772) > at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:729) > at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:933) > at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:309) > at org.eclipse.osgi.container.Module.doStart(Module.java:581) > at org.eclipse.osgi.container.Module.start(Module.java:449) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1628) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1608) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1579) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1522) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1) > at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) > at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340) > Starting application: 85414 > {code} > Log: [^Teiid_AssertionFailedException.log] > CC: [~apodhrad] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25455) JBoss Tools marketplace listing includes org.eclipse features

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25455?page=com.atlassian.jira.plugi... ] Aurélien Pupier edited comment on JBIDE-25455 at 12/12/17 3:13 AM: ------------------------------------------------------------------- I don't understand which features need to be installed/removed. [~jeffmaury] I gave you the admin rights was (Author: aurelien.pupier): I don't understand which features need to installed/removed. [~jeffmaury] I gave you the admin rights > JBoss Tools marketplace listing includes org.eclipse features > ------------------------------------------------------------- > > Key: JBIDE-25455 > URL: https://issues.jboss.org/browse/JBIDE-25455 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace > Affects Versions: 4.5.1.Final > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.5.2.Final > > > Someone added org.eclipse.buildship and org.eclipse.wst.* features to the Marketplace listing as optional-selected features. > Shouldn't these be installed via requirements from JBT features, and therefore not needed on the site? > The list of sanctioned features in the CoreTools category on the JBT site is here: > http://download.jboss.org/jbosstools/static/oxygen/stable/updates/core/4.... > So... why did the other features get added? And if they SHOULD be there, they should also be added to the JBT site too, for consistency. Right? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25455) JBoss Tools marketplace listing includes org.eclipse features

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25455?page=com.atlassian.jira.plugi... ] Aurélien Pupier commented on JBIDE-25455: ----------------------------------------- I don't understand which features need to installed/removed. [~jeffmaury] I gave you the admin rights > JBoss Tools marketplace listing includes org.eclipse features > ------------------------------------------------------------- > > Key: JBIDE-25455 > URL: https://issues.jboss.org/browse/JBIDE-25455 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace > Affects Versions: 4.5.1.Final > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.5.2.Final > > > Someone added org.eclipse.buildship and org.eclipse.wst.* features to the Marketplace listing as optional-selected features. > Shouldn't these be installed via requirements from JBT features, and therefore not needed on the site? > The list of sanctioned features in the CoreTools category on the JBT site is here: > http://download.jboss.org/jbosstools/static/oxygen/stable/updates/core/4.... > So... why did the other features get added? And if they SHOULD be there, they should also be added to the JBT site too, for consistency. Right? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25455) JBoss Tools marketplace listing includes org.eclipse features

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25455?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-25455: ------------------------------------ +1 for not including org.eclipse features. But who has write access to markeplace (I don't) ? > JBoss Tools marketplace listing includes org.eclipse features > ------------------------------------------------------------- > > Key: JBIDE-25455 > URL: https://issues.jboss.org/browse/JBIDE-25455 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace > Affects Versions: 4.5.1.Final > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.5.2.Final > > > Someone added org.eclipse.buildship and org.eclipse.wst.* features to the Marketplace listing as optional-selected features. > Shouldn't these be installed via requirements from JBT features, and therefore not needed on the site? > The list of sanctioned features in the CoreTools category on the JBT site is here: > http://download.jboss.org/jbosstools/static/oxygen/stable/updates/core/4.... > So... why did the other features get added? And if they SHOULD be there, they should also be added to the JBT site too, for consistency. Right? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25406) Fuse Tools New and Noteworthy for 4.5.2.AM2

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25406?page=com.atlassian.jira.plugi... ] Tomáš Sedmík closed JBIDE-25406. -------------------------------- verified with master branch > Fuse Tools New and Noteworthy for 4.5.2.AM2 > --------------------------------------------------- > > Key: JBIDE-25406 > URL: https://issues.jboss.org/browse/JBIDE-25406 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: fusetools, fusetools-extras > Reporter: Jeff MAURY > Assignee: Lars Heinemann > Priority: Critical > Labels: task > Fix For: 4.5.2.AM2 > > > Lars Heinemann, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Fuse Tools 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 Fuse Tools, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Fuse Tools 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-25400 #comment Create N&N for Fuse Tools 4.5.2.AM2 #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 Fuse Tools for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3983) Development Suite Installer should work behind proxy

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3983?page=com.atlassian.jira.plugin.... ] Denis Golovin closed JBDS-3983. ------------------------------- Resolution: Migrated to another ITS The only issue in topic was moved here https://github.com/redhat-developer-tooling/developer-platform-install/is.... > Development Suite Installer should work behind proxy > ---------------------------------------------------- > > Key: JBDS-3983 > URL: https://issues.jboss.org/browse/JBDS-3983 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Epic > Components: platform-installer > Affects Versions: 10.1.0.AM1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: release_notes > Fix For: 11.2.0.AM3 > > > DevSuite installer cannot download stack software form external links because it uses nodejs request module without proxy settings: > CDK also requires proxy to be configured to have vagrant up working after installation, which could affect CDK Server Adapter Implementation. > To make DevStudio Installer working behind proxy there should be variable HTTPS_PROXY in user environment which sets up URL to proxy server. URL examples for none auth proxy: > * http(s)://servername.com:3128 > * http(s)://192.168.0.47:3128 > For auth proxy: > * http(s)://username:password@servername.com:3128 > * http(s)://username:password@192.168.0.47:3128 > If you use email as username then replace @ with %40: > * http(s)://username%40server.com:password@servername.com:3128 > * http(s)://username%40server.com:password@192.168.0.47:3128 > Additional details are here https://github.com/request/request#controlling-proxy-behaviour-using-envi.... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 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 December 2017