November 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-24844) fix *.it.weekly jobs to properly build on macos w/ jdk1.8 (not openjdk 1.8)

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24844?page=com.atlassian.jira.plugi... ] Lukáš Valach closed JBIDE-24844. -------------------------------- Verified, closing. > fix *.it.weekly jobs to properly build on macos w/ jdk1.8 (not openjdk 1.8) > --------------------------------------------------------------------------- > > Key: JBIDE-24844 > URL: https://issues.jboss.org/browse/JBIDE-24844 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.5.0.Final > Reporter: Nick Boldt > Assignee: Pavol Srna > Fix For: 4.5.2.AM1 > > Attachments: red-weekly-smoke-tests.png, redballs-16.png > > > As noted in JBIDE-24835, the it.weekly jobs try to run on macos w/ openjdk 1.8, but no such JDK exists there. Therefore need a combinationFilter to let us build with openjdk on windows and linux, and oracle jdk on macos. > {code} > combinationFilter = (label_exp == "macosx").implies(jdk == "jdk1.8") && (label_exp != "macosx").implies(jdk == "openjdk-1.8") > {code} > TODO: verify all the jobs linked from here [1] are working for all OSes > [1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/devstudi... > * hibernatetools-itests.download-devstudio - test failures on rhel7 (not a matrix job) > * livereload.it.weekly - failing for windows 8.1 & 10 due to unresolved parent pom > * browsersim.it.weekly - failing for windows 8.1 due to unresolved parent pom > * archives.it.weekly - failed to resolve tycho-plugins:repo-utils1.0.0 (bad Nexus settings?) on win81 > * vpe.it.weekly - test failures on win81 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25400) Create New and Noteworthy for 4.5.2.AM2

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25400?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25400: ------------------------------- Story Points: 8 > Create New and Noteworthy for 4.5.2.AM2 > --------------------------------------- > > Key: JBIDE-25400 > URL: https://issues.jboss.org/browse/JBIDE-25400 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.5.2.AM2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for all N&N. See subtasks below. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3743) Cannot use JBDS 10.2 with jdk 9 EA build 140

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-3743?page=com.atlassian.jira.plugin.... ] Lukáš Valach closed JBDS-3743. ------------------------------ I didn't found jdk 9 EA build 140 so I tested it with 9-ea+135 (which we are using on jenkins). With 9-ea+135 it is possible to start Devstudio, jdk is configured by default, adding jdks works fine, but quick starts doesn't work. With JDK 9.0.1 everything works, including quick starts. So we can close this jira I think. > Cannot use JBDS 10.2 with jdk 9 EA build 140 > -------------------------------------------- > > Key: JBDS-3743 > URL: https://issues.jboss.org/browse/JBDS-3743 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer, upstream > Affects Versions: 10.0.0.Alpha1, 10.2.0.AM2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 11.1.0.GA > > Attachments: launchdevstudio10.2.0.AM2-with-jdk9ea140-configuration-settings.png, launchdevstudio10.2.0.AM2-with-jdk9ea140-jre-not-found-cant-build.png, launchdevstudio10.2.0.AM2-with-jdk9ea140-jre-not-supported.png > > > Oracle changed their JDK 1.9 Early Access builds recently. Now the installed jdk reports its version as 9-ea instead of 1.9 used previously. This caused a problem with the JBDS installer: JBDS-3581 > But even if I select jdk 1.8 in the installer and change jbdevstudio.ini to point to my 1.9 installation, JBDS won't start (I'm on Mac). > It just shows an error saying where to look for log. The log is linked here: > https://issues.jboss.org/secure/attachment/12396824/1453206771791.log > Upstream BZ: https://bugs.eclipse.org/bugs/show_bug.cgi?id=486213 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25400) Create New and Noteworthy for 4.5.2.AM2

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25400?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25400: ------------------------------- Sprint: devex #141 December 2017 > Create New and Noteworthy for 4.5.2.AM2 > --------------------------------------- > > Key: JBIDE-25400 > URL: https://issues.jboss.org/browse/JBIDE-25400 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.5.2.AM2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for all N&N. See subtasks below. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25398) [Regression]Camel/Fuse keywords are missing for Jboss Tools Marketplace

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25398?page=com.atlassian.jira.plugi... ] Lukáš Valach closed JBIDE-25398. -------------------------------- Verified, closing. > [Regression]Camel/Fuse keywords are missing for Jboss Tools Marketplace > ----------------------------------------------------------------------- > > Key: JBIDE-25398 > URL: https://issues.jboss.org/browse/JBIDE-25398 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace > Affects Versions: 4.5.1.Final > Reporter: Aurélien Pupier > Assignee: Nick Boldt > Fix For: 4.5.1.Final > > Attachments: image-2017-11-16-10-00-03-122.png > > > !image-2017-11-16-10-00-03-122.png|thumbnail! > proposal of keywords to add: > camel, apache camel, fuse, esb, fuse tooling -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25275) intermittent test failures in central in org.jboss.tools.maven.configurators.tests.EndorsedLibConfiguratorTest.testJBIDE11738_quote_hack_support

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25275?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25275: ------------------------------- Fix Version/s: (was: 4.5.x) > intermittent test failures in central in org.jboss.tools.maven.configurators.tests.EndorsedLibConfiguratorTest.testJBIDE11738_quote_hack_support > ------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-25275 > URL: https://issues.jboss.org/browse/JBIDE-25275 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.5.1.Final > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Critical > Fix For: 4.5.2.AM2 > > Attachments: intermittent-test-failures-central.png > > > intermittent test failures since Oct 3, when the last commit was pushed. > !intermittent-test-failures-central.png|thumbnail! > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Should we disable this test? or fix it? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4594) Enable java 9 in devstudio installer

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4594?page=com.atlassian.jira.plugin.... ] Lukáš Valach commented on JBDS-4594: ------------------------------------ Devstudio installer 11.2.0.AM1 allows to use JDK 9-ea, the warning is shown as expected, but in the case of JDK 9.0.1 the error is shown and it is not possible to proceed with installation. > Enable java 9 in devstudio installer > ------------------------------------ > > Key: JBDS-4594 > URL: https://issues.jboss.org/browse/JBDS-4594 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: installer > Affects Versions: 11.1.0.GA > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 11.2.0.AM2 > > > Right now when you select java 9 when installing devstudio we will reject - we only accept java 8. > With JBDS-4593, devstudio will now launch with java 9. It's not really supported yet and things can break. But at some point we should enable java 9 in the installer. Even if with a warning initially. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4588) update installer to be able to use JDK 9

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4588?page=com.atlassian.jira.plugin.... ] Lukáš Valach commented on JBDS-4588: ------------------------------------ I think that it should be done in JBDS-4594, I will add a reminder. > update installer to be able to use JDK 9 > ---------------------------------------- > > Key: JBDS-4588 > URL: https://issues.jboss.org/browse/JBDS-4588 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 11.1.0.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 11.2.0.AM2 > > Attachments: jdk9-ea.png, jdk9.0.1.png > > > Investigate what's needed to support running the installer w/ JDK 9. > May also need to add this to the devstudio.ini, after *-vmargs*: > {code}-Dosgi.requiredJavaVersion=1.8 > --add-modules=ALL-SYSTEM{code} -- https://wiki.eclipse.org/Configure_Eclipse_for_Java_9#Configure_Eclipse_f... > cc: [~mmalina] [~jeffmaury] [~dgolovin] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4583) Allow to maximize the window of the installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4583?page=com.atlassian.jira.plugin.... ] Denis Golovin resolved JBDS-4583. --------------------------------- Fix Version/s: 11.2.0.AM2 (was: 11.x) Resolution: Migrated to another ITS Moved to https://github.com/redhat-developer-tooling/developer-platform-install/is... > Allow to maximize the window of the installer > --------------------------------------------- > > Key: JBDS-4583 > URL: https://issues.jboss.org/browse/JBDS-4583 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Reporter: Aurélien Pupier > Fix For: 11.2.0.AM2 > > Attachments: image-2017-10-10-17-06-22-685.png, image-2017-10-10-17-06-47-629.png, image-2017-10-10-17-07-05-212.png > > > it is particularly useful on "Confirmation" page where selecting the components to install, it will avoid to have a long scrollbar > currently I ave 3 "dialog size" to see everything: > !image-2017-10-10-17-06-22-685.png|thumbnail! > !image-2017-10-10-17-06-47-629.png|thumbnail! > !image-2017-10-10-17-07-05-212.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 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 commented on JBTIS-1190: ------------------------------------- I had reproduced this issue on Jenkins \[1\] and also locally before I filed this jira. \[1\] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/user/lvalach... Andrej told me that he isn't able to reproduce so I tried it again (locally) from scratch. I uninstalled all rh-* packages and also removed rh-eclipse folder (rm \-rf /opt/rh/rh-eclipse47) and then installed rh-eclipse47-devstudio, I also removed ~/.eclipse folder (as always). The error didn't appear again, so my first idea was that some old/incompatible files or packagese were installed. So I applyed the same fix on jenkins (yum remove rh-\*; rm -rf /opt/rh/rh-eclipse47) but it didn't help. > 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, 4 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 November 2017