October 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4602) RPM should depend on tern rpm

by Nick Boldt (JIRA)

Nick Boldt created JBDS-4602: -------------------------------- Summary: RPM should depend on tern rpm Key: JBDS-4602 URL: https://issues.jboss.org/browse/JBDS-4602 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Sub-task Components: 3rd-party-dependencies, rpm, target-platform, upstream Affects Versions: 11.1.0.AM1 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 11.x RPM should depend on upstream tern.java rpm(s). Depends on getting this done in Fedora and devtools channel first. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4603) RPM should depend on tern rpmbuildship/gradle rpms

by Nick Boldt (JIRA)

Nick Boldt created JBDS-4603: -------------------------------- Summary: RPM should depend on tern rpmbuildship/gradle rpms Key: JBDS-4603 URL: https://issues.jboss.org/browse/JBDS-4603 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Sub-task Components: 3rd-party-dependencies, rpm, target-platform, upstream Affects Versions: 11.1.0.AM1 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 11.x RPM should depend on upstream buildship & grade tooling commons rpm(s). Depends on getting this done in Fedora and devtools channel first. See https://github.com/gradle/tooling-commons We probably want to contribute a maven-based build for this too, so that we can use it in the RPMs rather than needing to use gradle to build the rpms. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4604) Ensure Datatools and WTP-JPT (Dali) are available in DevTools (rh-eclipse47) so downstream rh-eclipse47-devstudio can use it

by Nick Boldt (JIRA)

Nick Boldt created JBDS-4604: -------------------------------- Summary: Ensure Datatools and WTP-JPT (Dali) are available in DevTools (rh-eclipse47) so downstream rh-eclipse47-devstudio can use it Key: JBDS-4604 URL: https://issues.jboss.org/browse/JBDS-4604 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Sub-task Components: rpm, upstream Affects Versions: 11.1.0.AM1 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 11.1.0.GA Mat says that Eclipse DTP and WTP-JPT are already in Fedora. So we need to ensure Datatools and WTP-JPT (Dali) are ALSO available in DevTools (rh-eclipse47); then downstream rh-eclipse47-devstudio can use it -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4605) rh-eclipse47-devstudio should depend on rh-eclipse47-eclipse-linuxtools-docker

by Nick Boldt (JIRA)

Nick Boldt created JBDS-4605: -------------------------------- Summary: rh-eclipse47-devstudio should depend on rh-eclipse47-eclipse-linuxtools-docker Key: JBDS-4605 URL: https://issues.jboss.org/browse/JBDS-4605 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Sub-task Components: docker, rpm Affects Versions: 11.1.0.AM2 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 11.1.0.AM2 To remove duplicate / older versions of linuxtools docker tools from the devstudio rpm install, we should depend on the upstream rh-eclipse47-eclipse-linuxtools-docker rpm. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4530) Work to remove all upstream 3rd party deps in the devstudio rpm

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4530?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4530: ----------------------------- Fix Version/s: 11.2.0.AM1 (was: 11.1.0.GA) > Work to remove all upstream 3rd party deps in the devstudio rpm > --------------------------------------------------------------- > > Key: JBDS-4530 > URL: https://issues.jboss.org/browse/JBDS-4530 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: 3rd-party-dependencies, rpm, target-platform, upstream > Affects Versions: 11.1.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 11.2.0.AM1 > > > This is a wrapper issue for a number of subtasks and linked issues related to eliminating the 3rd party plugins in the devstudio copr rpm, so that it can ultimately be built w/ brew. > Tasks include: > * add rpms already in Fedora to SCL/DevTools (eg., Datatools, WTP Dali/JPT) > * create new rpms in Fedora (buildship, recommenders/snipmatch, sapphire[1], m2e & extras[2], m2e-wtp & extras[3], tern.java) > * removal of old/duplicate versions in the target platform (javax.activation, guava, jetty, asm, aries > * ensure we're using the latest linuxtools/docker tools (including new features/plugins added for 6.1/6.1.1) > [1] may require contributing a Maven/Tycho build upstream to that project so we can then consume it in Koji/Brew > [2] m2e extras include: buildhelper, egit, mavenarchiver > [3] m2e.wtp extras include: jaxrs, jpa, jsf -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22966) create bzira fork that supports scraping RH bugzilla

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22966?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22966: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.1.Final) > create bzira fork that supports scraping RH bugzilla > ---------------------------------------------------- > > Key: JBIDE-22966 > URL: https://issues.jboss.org/browse/JBIDE-22966 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.5.x > > > Sample issue to scrape: > https://bugzilla.redhat.com/show_bug.cgi?id=1363849 > More issues: > https://bugzilla.redhat.com/buglist.cgi?component=rh-eclipse46&list_id=56... > Target method: > * look for whiteboard = RHT (then filter by date since last change, as current bzira.py [1] does) > Mappings: > * BZ Product = Red Hat Software Collections --> RHECLIPSE jira > * BZ component = rh-eclipse46 (maybe others in future, eg., eclipse-cdt, eclipse-docker) --> same component in jira (python script will generate new components automatically) > * Version = rh-eclipse46 --> "rh-eclipse46" version in JIRA > * Target Milestone --> label in JIRA > * Target Release -> label in JIRA > [1] https://github.com/maxandersen/jiralint/blob/master/bzira.py -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25268) cannot deploy jbosstools-hibernate to dl.jb.o

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25268?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-25268. -------------------------------- Resolution: Done Fixed with https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... >=1001, but now we have (unrelated) test failures. > cannot deploy jbosstools-hibernate to dl.jb.o > --------------------------------------------- > > Key: JBIDE-25268 > URL: https://issues.jboss.org/browse/JBIDE-25268 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, hibernate > Affects Versions: 4.5.1.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.5.1.Final > > > {code} > 15:27:49 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on > project hibernatetools.doc: Deployment failed: repository element was not specified in the > POM inside distributionManagement element or in > -DaltDeploymentRepository=id::layout::url parameter -> [Help 1] > {code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 11 months

1
0
0 / 0

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

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4588?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4588: ----------------------------- Fix Version/s: 11.x (was: 11.1.0.GA) > 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.x > > > 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)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25264) jenkins PR builds unable to connect to nexus: "Connection reset"

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25264?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-25264. -------------------------------- Resolution: Done Hasn't been a problem for a few days so resolving. > jenkins PR builds unable to connect to nexus: "Connection reset" > ---------------------------------------------------------------- > > Key: JBIDE-25264 > URL: https://issues.jboss.org/browse/JBIDE-25264 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.1.AM3 > Reporter: Andre Dietisheim > Assignee: Nick Boldt > Fix For: 4.5.1.Final > > > jenkins PR build currently fail to contact nexus with a "Connection reset": > * in jbosstools-base: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... > {code} > [ERROR] The build could not read 1 project -> [Help 1] > [ERROR] > [ERROR] The project org.jboss.tools:base:4.5.0-SNAPSHOT (/mnt/hudson_workspace/workspace/jbosstools-base-Pull-Request/pom.xml) has 1 error > [ERROR] Non-resolvable parent POM org.jboss.tools:parent:4.5.1.Final-SNAPSHOT for org.jboss.tools:base:4.5.0-SNAPSHOT: Could not transfer artifact org.jboss.tools:parent:pom:4.5.1.Final-20171017.105727-25 from/to jboss-snapshots-repository (https://repository.jboss.org/nexus/content/repositories/snapshots/): Connection reset and 'parent.relativePath' points at wrong local POM @ line 5, column 10 -> [Help 2] > {code} > * in jbosstools-openshift: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... > {code} > [ERROR] The project org.jboss.tools:openshift:3.4.1-SNAPSHOT (/mnt/hudson_workspace/workspace/jbosstools-openshift-Pull-Request/pom.xml) has 1 error > [ERROR] Non-resolvable parent POM org.jboss.tools:parent:4.5.1.Final-SNAPSHOT for org.jboss.tools:openshift:3.4.1-SNAPSHOT: Could not transfer artifact org.jboss.tools:parent:pom:4.5.1.Final-20171017.105727-25 from/to jboss-snapshots-repository (https://repository.jboss.org/nexus/content/repositories/snapshots/): Connection reset and 'parent.relativePath' points at wrong local POM @ line 4, column 10 -> [Help 2] > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4593) devstudio 11.1 nightly based on oxygen 1a will not run with Java 9

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4593?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4593: ----------------------------- Component/s: installer > devstudio 11.1 nightly based on oxygen 1a will not run with Java 9 > ------------------------------------------------------------------ > > Key: JBDS-4593 > URL: https://issues.jboss.org/browse/JBDS-4593 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 11.1.0.GA > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 11.1.0.GA > > > Not sure what component to use here. > I tried to run latest devstudio 11.1.0.GA nightly with java 9 and it won't run. > Here's what I got in the log: > {code} > !SESSION 2017-10-24 14:47:37.893 ----------------------------------------------- > eclipse.buildId=11.1.0.GA-v20171024-0818-B1458 > java.version=9 > java.vendor=Oracle Corporation > BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_CZ > Framework arguments: -product com.jboss.devstudio.core.product -keyring /Users/rasp/.eclipse_keyring > Command-line arguments: -os macosx -ws cocoa -arch x86_64 -product com.jboss.devstudio.core.product -keyring /Users/rasp/.eclipse_keyring > !ENTRY org.eclipse.osgi 4 0 2017-10-24 14:47:54.644 > !MESSAGE Application error > !STACK 1 > org.eclipse.e4.core.di.InjectionException: java.lang.NoClassDefFoundError: javax/annotation/PostConstruct > at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:410) > at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:318) > at org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:162) > at org.eclipse.e4.ui.internal.workbench.swt.E4Application.createDefaultHeadlessContext(E4Application.java:491) > at org.eclipse.e4.ui.internal.workbench.swt.E4Application.createDefaultContext(E4Application.java:505) > at org.eclipse.e4.ui.internal.workbench.swt.E4Application.createE4Workbench(E4Application.java:204) > at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:614) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:564) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590) > at org.eclipse.equinox.launcher.Main.run(Main.java:1499) > Caused by: java.lang.NoClassDefFoundError: javax/annotation/PostConstruct > at org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:124) > at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:399) > ... 22 more > Caused by: java.lang.ClassNotFoundException: javax.annotation.PostConstruct cannot be found by org.eclipse.e4.core.di_1.6.100.v20170421-1418 > at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:433) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:395) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:387) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:150) > at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:496) > ... 24 more > !ENTRY org.eclipse.e4.ui.workbench 4 0 2017-10-24 14:47:54.653 > !MESSAGE FrameworkEvent ERROR > !STACK 0 > java.lang.NoClassDefFoundError: javax/annotation/PreDestroy > at org.eclipse.e4.core.internal.di.InjectorImpl.disposed(InjectorImpl.java:450) > at org.eclipse.e4.core.internal.di.Requestor.disposed(Requestor.java:156) > at org.eclipse.e4.core.internal.contexts.ContextObjectSupplier$ContextInjectionListener.update(ContextObjectSupplier.java:78) > at org.eclipse.e4.core.internal.contexts.TrackableComputationExt.update(TrackableComputationExt.java:111) > at org.eclipse.e4.core.internal.contexts.TrackableComputationExt.handleInvalid(TrackableComputationExt.java:74) > at org.eclipse.e4.core.internal.contexts.EclipseContext.dispose(EclipseContext.java:178) > at org.eclipse.e4.core.internal.contexts.osgi.EclipseContextOSGi.dispose(EclipseContextOSGi.java:99) > at org.eclipse.e4.core.internal.contexts.osgi.EclipseContextOSGi.bundleChanged(EclipseContextOSGi.java:141) > at org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(BundleContextImpl.java:908) > at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) > at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148) > at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEventPrivileged(EquinoxEventPublisher.java:213) > at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEvent(EquinoxEventPublisher.java:120) > at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEvent(EquinoxEventPublisher.java:112) > at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor.publishModuleEvent(EquinoxContainerAdaptor.java:168) > at org.eclipse.osgi.container.Module.publishEvent(Module.java:476) > at org.eclipse.osgi.container.Module.doStop(Module.java:634) > at org.eclipse.osgi.container.Module.stop(Module.java:498) > at org.eclipse.osgi.container.SystemModule.stop(SystemModule.java:202) > at org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle$EquinoxSystemModule$1.run(EquinoxBundle.java:165) > at java.base/java.lang.Thread.run(Thread.java:844) > Caused by: java.lang.ClassNotFoundException: javax.annotation.PreDestroy cannot be found by org.eclipse.e4.core.di_1.6.100.v20170421-1418 > at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:433) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:395) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:387) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:150) > at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:496) > ... 21 more > {code} > So it's those java.lang.NoClassDefFoundError errors that we've seen before. > I know that for 11.1.0.GA it's not our goal to run devstudio on java 9, but it would be good to figure out what's wrong. > This devstudio is based on the new oxygen 1a TP which includes > org.eclipse.platform_4.7.1.v20171009-0410 > I tried plain Eclipse Oxygen 1a and it can start on java 9 without a problem. > Maybe they have some tweaks in their eclipse.ini that we could emulate? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues October 2017