January 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23758) Avoid caught NPE in wst StopAction by providing an empty list instead of null

by Aurélien Pupier (JIRA)

Aurélien Pupier created JBIDE-23758: --------------------------------------- Summary: Avoid caught NPE in wst StopAction by providing an empty list instead of null Key: JBIDE-23758 URL: https://issues.jboss.org/browse/JBIDE-23758 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.4.2.Final Reporter: Aurélien Pupier when starting JBDS, there is a silent caught NPE in AsbtractServerAction.selectionChanged because org.jboss.ide.eclipse.as.ui.actions.AbstractServerActionDelegate$4 is returning null instead of an empty list {noformat} Thread [main] (Suspended (exception NullPointerException)) owns: RunnableLock (id=138) StopAction(AbstractServerAction).selectionChanged(IStructuredSelection) line: 75 StopAction.<init>(Shell, ISelectionProvider) line: 36 StopServerActionDelegate.init(IWorkbenchWindow) line: 24 WWinPluginAction.initDelegate() line: 187 WWinPluginAction(PluginAction).createDelegate() line: 125 WWinPluginAction.refreshActionList() line: 167 AbstractUIPlugin$1.run() line: 482 RunnableLock.run() line: 35 UISynchronizer(Synchronizer).runAsyncMessages(boolean) line: 182 Display.runAsyncMessages(boolean) line: 4203 Display.readAndDispatch() line: 3819 PartRenderingEngine$4.run() line: 1121 Realm.runWithDefault(Realm, Runnable) line: 336 PartRenderingEngine.run(MApplicationElement, IEclipseContext) line: 1022 E4Workbench.createAndRunUI(MApplicationElement) line: 150 Workbench$5.run() line: 687 Realm.runWithDefault(Realm, Runnable) line: 336 Workbench.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 604 PlatformUI.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 148 IDEApplication.start(IApplicationContext) line: 138 EclipseAppHandle.run(Object) line: 196 EclipseAppLauncher.runApplication(Object) line: 134 EclipseAppLauncher.start(Object) line: 104 EclipseStarter.run(Object) line: 388 EclipseStarter.run(String[], Runnable) line: 243 NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method] NativeMethodAccessorImpl.invoke(Object, Object[]) line: 62 DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43 Method.invoke(Object, Object...) line: 498 Main.invokeFramework(String[], URL[]) line: 673 Main.basicRun(String[]) line: 610 Main.run(String[]) line: 1519 Main.main(String[]) line: 1492 {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14792) Marketplace install button tooltips all say Juno, not the actual required Eclipse version

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14792?page=com.atlassian.jira.plugi... ] Lukáš Valach closed JBIDE-14792. -------------------------------- Verified, fixed in upstream, closing. > Marketplace install button tooltips all say Juno, not the actual required Eclipse version > ------------------------------------------------------------------------------------------ > > Key: JBIDE-14792 > URL: https://issues.jboss.org/browse/JBIDE-14792 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace, upstream > Affects Versions: 4.1.0.Beta1 > Reporter: Rastislav Wagner > Assignee: Nick Boldt > Fix For: 4.4.3.AM2 > > > Install button (tooltip) issue is upstream. Reported here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=410196 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4190) [central-update] problem installing springide: eclipse.boot.dash plugin depends on slf4j 1.7.2 and ide.eclipse.quickfix depends on javax.servlet 3.1.0

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4190?page=com.atlassian.jira.plugin.... ] Lukáš Valach closed JBDS-4190. ------------------------------ Verified in 10.3.0.AM2. Central contains Spring IDE 3.8.3.201612191259. I was able to install Spring IDE* + Eclipse Integration Commons. Eclipse crashed on restart as Nick described above. So I restart Eclipse with -clean and it started properly. > [central-update] problem installing springide: eclipse.boot.dash plugin depends on slf4j 1.7.2 and ide.eclipse.quickfix depends on javax.servlet 3.1.0 > ------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBDS-4190 > URL: https://issues.jboss.org/browse/JBDS-4190 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: central-update, rpm, upstream > Affects Versions: 10.2.0.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.3.0.AM2 > > Attachments: rh-eclipse46-devstudio10.2.log.20161118-1112_strict.txt, rh-eclipse46-devstudio10.2.log.20161118-1207_strict.txt, springide382.png, springide383-fixed-jbds4190-installed.png, springide383-fixed-jbds4190.png, springide383-install-feature-list-select.png > > > springide 3.7.3 depends on slf4j 1.7.2 and javax.servlet 3.1.0 > {code} > org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NoClassDefFoundError: org/springframework/ide/eclipse/beans/core/model/IProfileAwareBeansComponent) > Caused by: java.lang.NoClassDefFoundError: org/springframework/ide/eclipse/beans/core/model/IProfileAwareBeansComponent > at org.springframework.ide.eclipse.beans.ui.navigator.filters.NonMatchingProfilesFilter.select(NonMatchingProfilesFilter.java:24) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4249) Add cleanup for outdated cached files

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4249?page=com.atlassian.jira.plugin.... ] Jan Richter updated JBDS-4249: ------------------------------ Story Points: 2 > Add cleanup for outdated cached files > ------------------------------------- > > Key: JBDS-4249 > URL: https://issues.jboss.org/browse/JBDS-4249 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: platform-installer > Affects Versions: 10.3.0.AM2 > Reporter: Jan Richter > Assignee: Jan Richter > Fix For: 10.3.0.AM2 > > > Need to delete files that are no longer supposed to be bundled from the requirements cache. Otherwise unwanted files may end up in the bundled builds. (for example Mac builds that contain both rhel.iso and rhel-vagrant-box) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23655) Integration tests: when pulling an image without tag, we should assert that only the latet image is pulled

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23655?page=com.atlassian.jira.plugi... ] Josef Kopriva reassigned JBIDE-23655: ------------------------------------- Assignee: Josef Kopriva > Integration tests: when pulling an image without tag, we should assert that only the latet image is pulled > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23655 > URL: https://issues.jboss.org/browse/JBIDE-23655 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests > Affects Versions: 4.4.3.AM1 > Reporter: Andre Dietisheim > Assignee: Josef Kopriva > Fix For: 4.4.3.AM2 > > > In https://bugs.eclipse.org/bugs/show_bug.cgi?id=499843 it was discovered that the docker tooling was pulling all images if no tag was provided. We should have a test that asserts that this isnt happening. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23752) For JBIDE 4.4.3.AM2: Prepare for 4.4.3.AM2 / 10.3.0.AM2 [visual-page-editor-core]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23752?page=com.atlassian.jira.plugi... ] Ilya Buziuk reassigned JBIDE-23752: ----------------------------------- Assignee: Ilya Buziuk > For JBIDE 4.4.3.AM2: Prepare for 4.4.3.AM2 / 10.3.0.AM2 [visual-page-editor-core] > --------------------------------------------------------------------------------- > > Key: JBIDE-23752 > URL: https://issues.jboss.org/browse/JBIDE-23752 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: visual-page-editor-core > Reporter: Friendly Jira Robot > Assignee: Ilya Buziuk > Priority: Blocker > Labels: task > Fix For: 4.4.3.AM2 > > > For JBIDE 4.4.3.AM2 [visual-page-editor-core]: Please perform the following tasks: 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.3.AM2-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.3.AM2-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: README.md features plugins pom.xml pom.xml.orig site tests *{color:orange}4.4.3.AM2-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. {code} mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT {code} 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 4b. Ensure you've *run your tests using the latest *maximum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for visual-page-editor-core task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23742) For JBIDE 4.4.3.AM2: Prepare for 4.4.3.AM2 / 10.3.0.AM2 [browsersim]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23742?page=com.atlassian.jira.plugi... ] Ilya Buziuk reassigned JBIDE-23742: ----------------------------------- Assignee: Ilya Buziuk > For JBIDE 4.4.3.AM2: Prepare for 4.4.3.AM2 / 10.3.0.AM2 [browsersim] > -------------------------------------------------------------------- > > Key: JBIDE-23742 > URL: https://issues.jboss.org/browse/JBIDE-23742 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: browsersim > Reporter: Friendly Jira Robot > Assignee: Ilya Buziuk > Priority: Blocker > Labels: task > Fix For: 4.4.3.AM2 > > > For JBIDE 4.4.3.AM2 [browsersim]: Please perform the following tasks: 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.3.AM2-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.3.AM2-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: README.md features plugins pom.xml pom.xml.orig products site tests *{color:orange}4.4.3.AM2-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. {code} mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT {code} 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 4b. Ensure you've *run your tests using the latest *maximum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for browsersim task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4191) problem installing atlassian: depends on javax.servlet 3.1.0 -- remove atlassian from Central

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4191?page=com.atlassian.jira.plugin.... ] Lukáš Valach closed JBDS-4191. ------------------------------ Verified in 10.3.0.AM2. > problem installing atlassian: depends on javax.servlet 3.1.0 -- remove atlassian from Central > --------------------------------------------------------------------------------------------- > > Key: JBDS-4191 > URL: https://issues.jboss.org/browse/JBDS-4191 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: central-update, rpm > Affects Versions: 10.2.0.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.3.0.AM2 > > > atlassian: depends on javax.servlet 3.1.0 (via req-bundle on javax.xml.rpc 1.1.0 from c.a.conn.eclipse.jira.core) > : also depends on org.eclipse.core.runtime.compatibility.auth > : also depends on mortbay, which breaks because of javax/servlet/Servlet > {code} > !MESSAGE Authorization infrastructure (org.eclipse.core.runtime.compatibility.auth) not installed. > !STACK 0 > java.lang.ClassNotFoundException: org.eclipse.core.internal.runtime.auth.AuthorizationDatabase cannot be found by org.eclipse.core.runtime_3.12.0.v20160920-1429 > at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:461) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:372) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:364) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:264) > at org.eclipse.core.internal.runtime.AuthorizationHandler.getAuthClass(AuthorizationHandler.java:48) > at org.eclipse.core.internal.runtime.AuthorizationHandler.loadKeyring(AuthorizationHandler.java:69) > at org.eclipse.core.internal.runtime.AuthorizationHandler.flushAuthorizationInfo(AuthorizationHandler.java:231) > at org.eclipse.core.runtime.Platform.flushAuthorizationInfo(Platform.java:590) > at com.atlassian.connector.eclipse.internal.commons.ui.MigrateToSecureStorageJob.migrateToSecureStorage(MigrateToSecureStorageJob.java:89) > at com.atlassian.connector.eclipse.internal.commons.ui.MigrateToSecureStorageJob.runInUIThread(MigrateToSecureStorageJob.java:60) > !ENTRY org.eclipse.core.jobs 4 2 2016-11-17 21:09:30.244 > !MESSAGE An internal error occurred during: "Start Embedded Web Server". > !STACK 0 > java.lang.LinkageError: loader constraint violation: when resolving method "org.mortbay.jetty.servlet.ServletHolder.<init>(Ljavax/servlet/Servlet;)V" the class loader (instance of org/eclipse/osgi/internal/loader/EquinoxClassLoader) of the current class, com/atlassian/connector/eclipse/internal/directclickthrough/ui/DirectClickThroughUiPlugin$2, and the class loader (instance of org/eclipse/osgi/internal/loader/EquinoxClassLoader) for the method's defining class, org/mortbay/jetty/servlet/ServletHolder, have different Class objects for the type javax/servlet/Servlet used in the signature > at com.atlassian.connector.eclipse.internal.directclickthrough.ui.DirectClickThroughUiPlugin$2.runImpl(DirectClickThroughUiPlugin.java:88) > at com.atlassian.connector.eclipse.internal.core.jobs.JobWithStatus.run(JobWithStatus.java:50) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > depends on and installs javax.servlet: > * com.atlassian.connector.eclipse.bamboo.feature > * com.atlassian.connector.eclipse.directclickthrough.feature > * com.atlassian.connector.eclipse.jira.feature > * com.atlassian.connector.commons.feature -> connector.commons -> javax.xml.rpc 1.1.0 -> javax.servlet 3.1.0 > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4249) Add cleanup for outdated cached files

by Jan Richter (JIRA)

Jan Richter created JBDS-4249: --------------------------------- Summary: Add cleanup for outdated cached files Key: JBDS-4249 URL: https://issues.jboss.org/browse/JBDS-4249 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Task Components: platform-installer Affects Versions: 10.3.0.AM2 Reporter: Jan Richter Assignee: Jan Richter Fix For: 10.3.0.AM2 Need to delete files that are no longer supposed to be bundled from the requirements cache. Otherwise unwanted files may end up in the bundled builds. (for example Mac builds that contain both rhel.iso and rhel-vagrant-box) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4084) Provide documentation about using the installed DevStudio

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/JBDS-4084?page=com.atlassian.jira.plugin.... ] Misha Ali closed JBDS-4084. --------------------------- Assignee: Misha Ali Resolution: Rejected Thanks, [~aurelien.pupier]. If you have any thoughts about RFEs or changes in docs, please don't hesitate to let me know or log a bug. > Provide documentation about using the installed DevStudio > --------------------------------------------------------- > > Key: JBDS-4084 > URL: https://issues.jboss.org/browse/JBDS-4084 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: documentation, platform-installer > Affects Versions: 10.1.0.GA > Reporter: Aurélien Pupier > Assignee: Misha Ali > > when following the getting started http://developers.redhat.com/products/devsuite/get-started/ > at the ned it redirect to the "command-line" version to use Containers. > it would be really better to provide tutorials to use the installed JBDS and the pre-configured CDK which is available in Servers view. > Personal note: I wasn't able to find by myself how do it in the Studio, I'm representing a UI-lover end-user, I asked for help on Devsuite HipChat channel -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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 January 2017