November 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23322) create mojo that takes as input a list of URLs and a name, and generates a composite site

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23322?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23322: ------------------------------- Fix Version/s: 4.4.3.AM1 (was: 4.4.2.Final) > create mojo that takes as input a list of URLs and a name, and generates a composite site > ----------------------------------------------------------------------------------------- > > Key: JBIDE-23322 > URL: https://issues.jboss.org/browse/JBIDE-23322 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.3.AM1 > > > In https://issues.jboss.org/browse/WINDUP-1189 it was requested that tycho builds be able to produce a simple composite site, using as input 2 or more URLs. > So, to generalize this for use by other projects, we need a mojo that can be configured with a set of URLs, and a site name, in order to produce three files: > {code} > target/composite/compositeContent.xml > target/composite/compositeArtifacts.xml > target/composite/p2.index (like https://devstudio.jboss.com/10.0/stable/updates/p2.index ) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23489) Find out how to run mvn clean verify -Dtest.installBase=path/to/devstudio/rpm

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23489?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23489: ------------------------------- Fix Version/s: 4.4.x (was: 4.4.2.Final) > Find out how to run mvn clean verify -Dtest.installBase=path/to/devstudio/rpm > ------------------------------------------------------------------------------ > > Key: JBIDE-23489 > URL: https://issues.jboss.org/browse/JBIDE-23489 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.2.AM3 > Reporter: Pavol Srna > Fix For: 4.4.x > > > We need to find a way how to run automated tests agains devstudio rpm. > I've tried the following paths: > 1) (as root) mvn clean verify -Dtest.installBase=/opt/rh/rh-eclipse46/root/usr/shareclipse/droplets/devstudio/eclipse/ > 2) (as hudson) mvn clean verify -Dtest.installBase=~/.eclipse/org.eclipse.platform_283378046_linux_gtk_x86_64 > But none of the above works. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23480) update p2diff & p2browser to build against Neon

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23480?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23480: ------------------------------- Fix Version/s: 4.4.x > update p2diff & p2browser to build against Neon > ----------------------------------------------- > > Key: JBIDE-23480 > URL: https://issues.jboss.org/browse/JBIDE-23480 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.4.x > > > To make them current and more easily used, make sure that both p2browser and p2diff can be compiled against Neon (not Luna) dependencies. > https://github.com/ifedorenko/p2-browser > https://github.com/irbull/p2diff -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-989) Publish Devstudio IS 10.0.0.GA to Eclipse marketplace

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-989?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-989. ----------------------------------- Verified with eclipse-jee-neon-R > Publish Devstudio IS 10.0.0.GA to Eclipse marketplace > ----------------------------------------------------- > > Key: JBTIS-989 > URL: https://issues.jboss.org/browse/JBTIS-989 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 10.0.0.GA > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Blocker > Fix For: 10.0.0.GA > > > Publish Devstudio IS 10.0.0.GA to Eclipse marketplace -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4201) CLI-only installation is available but does not provide necessary info

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/JBDS-4201?page=com.atlassian.jira.plugin.... ] Misha Ali commented on JBDS-4201: --------------------------------- [~akazakov], could you have a look at this JIRA please? > CLI-only installation is available but does not provide necessary info > ---------------------------------------------------------------------- > > Key: JBDS-4201 > URL: https://issues.jboss.org/browse/JBDS-4201 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Affects Versions: 10.2.0.GA > Reporter: Misha Ali > > I had some feedback from another writer testing a procedure with devstudio. He was using a CLI-only VM and was confused because the installer worked but offered little information, as would be expected. > Essentially, the non-GUI installation worked (java -jar devstudio_version.jar) but did not ask where to install devstudio, nor did it provide the default target folder it used. The GUI version asks if the user wants to deploy devstudio after the installation, but the non-GUI version does nothing. The resulting user experience was confusion, not knowing where devstudio was installed or how to start it. > My questions here are: > - is the non-GUI way a valid installation path? If yes, we should document it, and if not, we should mention it, either in the docs or when installation happens. > - If the non-GUI installation is a valid path, it should replicate the questions in the wizard, such as where to install devstudio and which jdk to use, etc. The difference between the two installation paths causes confusion. > Any thoughts? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4201) CLI-only installation is available but does not provide necessary info

by Misha Ali (JIRA)

Misha Ali created JBDS-4201: ------------------------------- Summary: CLI-only installation is available but does not provide necessary info Key: JBDS-4201 URL: https://issues.jboss.org/browse/JBDS-4201 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Enhancement Affects Versions: 10.2.0.GA Reporter: Misha Ali I had some feedback from another writer testing a procedure with devstudio. He was using a CLI-only VM and was confused because the installer worked but offered little information, as would be expected. Essentially, the non-GUI installation worked (java -jar devstudio_version.jar) but did not ask where to install devstudio, nor did it provide the default target folder it used. The GUI version asks if the user wants to deploy devstudio after the installation, but the non-GUI version does nothing. The resulting user experience was confusion, not knowing where devstudio was installed or how to start it. My questions here are: - is the non-GUI way a valid installation path? If yes, we should document it, and if not, we should mention it, either in the docs or when installation happens. - If the non-GUI installation is a valid path, it should replicate the questions in the wizard, such as where to install devstudio and which jdk to use, etc. The difference between the two installation paths causes confusion. Any thoughts? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4200) Problem installing switchyard from devstudio IS 10.0.0.GA site into devstudio rpm

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4200?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4200: ----------------------------- Parent: (was: JBDS-4175) Issue Type: Task (was: Sub-task) > Problem installing switchyard from devstudio IS 10.0.0.GA site into devstudio rpm > --------------------------------------------------------------------------------- > > Key: JBDS-4200 > URL: https://issues.jboss.org/browse/JBDS-4200 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: integration, rpm > Affects Versions: 10.2.0.GA > Environment: RHEL7 > Reporter: Lukáš Valach > Assignee: Nick Boldt > Fix For: 10.3.0.AM1 > > Attachments: rh-eclipse46-devstudio10.2.log.switchyard_plugin_test.txt > > > I tried to install switchyard and this error appeared in the log after restart: > {code} > !ENTRY org.switchyard.tools.core 4 0 2016-11-23 09:45:11.118 > !MESSAGE FrameworkEvent ERROR > !STACK 0 > org.osgi.framework.BundleException: Could not resolve module: org.switchyard.tools.core [1390] > Bundle was not resolved because of a uses contraint violation. > org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.switchyard.tools.core [osgi.identity; osgi.identity="org.switchyard.tools.core"; type="osgi.bundle"; version:Version="2.2.0.Final-v20161110-1803-B65"] because it is exposed to package 'org.slf4j' from resources org.slf4j.api [osgi.identity; type="osgi.bundle"; version:Version="1.7.2.v20121108-1250"; osgi.identity="org.slf4j.api"] and slf4j.api [osgi.identity; type="osgi.bundle"; version:Version="1.7.4"; osgi.identity="slf4j.api"] via two dependency chains. > {code} > See whole log here [^rh-eclipse46-devstudio10.2.log.switchyard_plugin_test.txt]. > Tested in 10.2-0.20161123.1426. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22417) Eclipse will not run with java9 - NoClassDefFoundError

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22417?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22417: ------------------------------- Fix Version/s: 4.4.x (was: 4.4.3.AM1) > Eclipse will not run with java9 - NoClassDefFoundError > ------------------------------------------------------ > > Key: JBIDE-22417 > URL: https://issues.jboss.org/browse/JBIDE-22417 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.4.0.Alpha2 > Reporter: Martin Malina > Assignee: Alexey Kazakov > Priority: Critical > Labels: java9 > Fix For: 4.4.x > > Attachments: e, eclipse.log.20161021-1321.txt > > > As of the latest build of Oracle JDK 9, Eclipse Neon M7 will not start. > Java version: > {code} > $ java -version > java version "9-ea" > Java(TM) SE Runtime Environment (build 9-ea+118) > Java HotSpot(TM) 64-Bit Server VM (build 9-ea+118, mixed mode) > {code} > Error log: > {code} > !ENTRY org.eclipse.osgi 4 0 2016-05-19 11:14:42.241 > !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:386) > at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:294) > at org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:162) > at org.eclipse.e4.ui.internal.workbench.swt.E4Application.createDefaultHeadlessContext(E4Application.java:490) > at org.eclipse.e4.ui.internal.workbench.swt.E4Application.createDefaultContext(E4Application.java:504) > at org.eclipse.e4.ui.internal.workbench.swt.E4Application.createE4Workbench(E4Application.java:203) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:626) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) > 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 jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(java.base@9-ea/Native Method) > at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(java.base@9-ea/NativeMethodAccessorImpl.java:62) > at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(java.base@9-ea/DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(java.base@9-ea/Method.java:531) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610) > at org.eclipse.equinox.launcher.Main.run(Main.java:1519) > Caused by: java.lang.NoClassDefFoundError: javax/annotation/PostConstruct > at org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:151) > at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:375) > ... 22 more > Caused by: java.lang.ClassNotFoundException: javax.annotation.PostConstruct cannot be found by org.eclipse.e4.core.di_1.6.0.v20160319-0612 > at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:394) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:357) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:349) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161) > at java.lang.ClassLoader.loadClass(java.base@9-ea/ClassLoader.java:419) > ... 24 more > !ENTRY org.eclipse.e4.ui.workbench 4 0 2016-05-19 11:14:42.248 > !MESSAGE FrameworkEvent ERROR > !STACK 0 > java.lang.NoClassDefFoundError: javax/annotation/PreDestroy > at org.eclipse.e4.core.internal.di.InjectorImpl.disposed(InjectorImpl.java:426) > at org.eclipse.e4.core.internal.di.Requestor.disposed(Requestor.java:154) > 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:175) > at org.eclipse.e4.core.internal.contexts.osgi.EclipseContextOSGi.dispose(EclipseContextOSGi.java:106) > at org.eclipse.e4.core.internal.contexts.osgi.EclipseContextOSGi.bundleChanged(EclipseContextOSGi.java:139) > at org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(BundleContextImpl.java:903) > 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:156) > 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:191) > at org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle$EquinoxSystemModule$1.run(EquinoxBundle.java:165) > at java.lang.Thread.run(java.base@9-ea/Thread.java:804) > Caused by: java.lang.ClassNotFoundException: javax.annotation.PreDestroy cannot be found by org.eclipse.e4.core.di_1.6.0.v20160319-0612 > at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:394) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:357) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:349) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161) > at java.lang.ClassLoader.loadClass(java.base@9-ea/ClassLoader.java:419) > ... 21 more > {code} > Upstream issue - targeted for Neon.1: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=493761 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23515) Create and use Neon.2 target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23515?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23515: ------------------------------- Fix Version/s: 4.4.3.Final (was: 4.4.2.Final) > Create and use Neon.2 target platform > ------------------------------------- > > Key: JBIDE-23515 > URL: https://issues.jboss.org/browse/JBIDE-23515 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: target-platform > Affects Versions: 4.4.1.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.3.Final > > > Once available in December, we should move up to Neon.2 > https://wiki.eclipse.org/index.php?title=Neon/Simultaneous_Release_Plan#S... > Story points: 21 (fibonacci) > jbt tp, > jbds tp, > central tp; > jbt-build-sites, > jbds site build; > update install/matrix jobs to use new Eclipse JEE/platform binary; > mailing list announcements -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23515) Create and use Neon.2 target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23515?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23515: ------------------------------- Description: Once available in December, we should move up to Neon.2 https://wiki.eclipse.org/index.php?title=Neon/Simultaneous_Release_Plan#S... Story points: 21 (fibonacci) jbt tp, jbds tp, central tp; jbt-build-sites, jbds site build; update install/matrix jobs to use new Eclipse JEE/platform binary; mailing list announcements was: Once available in late August or early September, we should move up to Neon.1. https://wiki.eclipse.org/index.php?title=Neon/Simultaneous_Release_Plan#S... Story points: 21 (fibonacci) jbt tp, jbds tp, central tp; jbt-build-sites, jbds site build; update install/matrix jobs to use new Eclipse JEE/platform binary; mailing list announcements > Create and use Neon.2 target platform > ------------------------------------- > > Key: JBIDE-23515 > URL: https://issues.jboss.org/browse/JBIDE-23515 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: target-platform > Affects Versions: 4.4.1.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.2.Final > > > Once available in December, we should move up to Neon.2 > https://wiki.eclipse.org/index.php?title=Neon/Simultaneous_Release_Plan#S... > Story points: 21 (fibonacci) > jbt tp, > jbds tp, > central tp; > jbt-build-sites, > jbds site build; > update install/matrix jobs to use new Eclipse JEE/platform binary; > mailing list announcements -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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