October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-964) Confusing versions of BPMN2 features

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-964?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-964: ------------------------------------ Description: Devstudio IS 10.0.0.CR1 contains the following BPMN2 bundles - org.eclipse.bpmn2.feature_1.3.1.Final-v20160927-2047-B56.jar - org.eclipse.bpmn2.modeler.examples_1.3.2.Final-v20161020-1541-B59.jar - org.eclipse.bpmn2.modeler.runtime.jboss_1.3.2.Final-v20161020-1541-B59.jar - org.eclipse.bpmn2.modeler_1.3.2.Final-v20161020-1541-B59.jar As you can see there are two versions which is very confusing. For example, DevstudioIS 10.0.0.Alpha1 contains BPMN2 versions 1.3.0.Final-v20160119-1832 and 1.3.1.Final-v20160831-1132-B55, so how can customer specify correct version in case of reporting an issue? I don't think there are two standalone projects of BPMN2, so there is no reason to use 2 versions. was: Devstudio IS 10.0.0.CR1 contains the following BPMN2 bundles - org.eclipse.bpmn2.feature_1.3.1.Final-v20160927-2047-B56.jar - org.eclipse.bpmn2.modeler.examples_1.3.2.Final-v20161020-1541-B59.jar - org.eclipse.bpmn2.modeler.runtime.jboss_1.3.2.Final-v20161020-1541-B59.jar - org.eclipse.bpmn2.modeler_1.3.2.Final-v20161020-1541-B59.jar As you can see there are two versions which is very confusing. For example, DevstudioIS 10.0.0.Alpha1 contains BPMN2 versions 1.3.0.Final-v20160119-1832 and 1.3.1.Final-v20160831-1132-B55, so how can customer specify correct version in case of reporting an issue? I don't think there are two standalone projects of BPMN2, so there is no reason to use 2 version. > Confusing versions of BPMN2 features > ------------------------------------ > > Key: JBTIS-964 > URL: https://issues.jboss.org/browse/JBTIS-964 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: BPMN2, distribution > Affects Versions: 10.0.0.CR1 > Reporter: Andrej Podhradsky > > Devstudio IS 10.0.0.CR1 contains the following BPMN2 bundles > - org.eclipse.bpmn2.feature_1.3.1.Final-v20160927-2047-B56.jar > - org.eclipse.bpmn2.modeler.examples_1.3.2.Final-v20161020-1541-B59.jar > - org.eclipse.bpmn2.modeler.runtime.jboss_1.3.2.Final-v20161020-1541-B59.jar > - org.eclipse.bpmn2.modeler_1.3.2.Final-v20161020-1541-B59.jar > As you can see there are two versions which is very confusing. For example, DevstudioIS 10.0.0.Alpha1 contains BPMN2 versions 1.3.0.Final-v20160119-1832 and 1.3.1.Final-v20160831-1132-B55, so how can customer specify correct version in case of reporting an issue? > I don't think there are two standalone projects of BPMN2, so there is no reason to use 2 versions. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-964) Confusing versions of BPMN2 features

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-964: --------------------------------------- Summary: Confusing versions of BPMN2 features Key: JBTIS-964 URL: https://issues.jboss.org/browse/JBTIS-964 Project: JBoss Tools Integration Stack Issue Type: Bug Components: BPMN2, distribution Affects Versions: 10.0.0.CR1 Reporter: Andrej Podhradsky Devstudio IS 10.0.0.CR1 contains the following BPMN2 bundles - org.eclipse.bpmn2.feature_1.3.1.Final-v20160927-2047-B56.jar - org.eclipse.bpmn2.modeler.examples_1.3.2.Final-v20161020-1541-B59.jar - org.eclipse.bpmn2.modeler.runtime.jboss_1.3.2.Final-v20161020-1541-B59.jar - org.eclipse.bpmn2.modeler_1.3.2.Final-v20161020-1541-B59.jar As you can see there are two versions which is very confusing. For example, DevstudioIS 10.0.0.Alpha1 contains BPMN2 versions 1.3.0.Final-v20160119-1832 and 1.3.1.Final-v20160831-1132-B55, so how can customer specify correct version in case of reporting an issue? I don't think there are two standalone projects of BPMN2, so there is no reason to use 2 version. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-963) Change the way of KieSession creation

by Jozef Marko (JIRA)

Jozef Marko created JBTIS-963: --------------------------------- Summary: Change the way of KieSession creation Key: JBTIS-963 URL: https://issues.jboss.org/browse/JBTIS-963 Project: JBoss Tools Integration Stack Issue Type: Bug Components: BPMN2, QE Affects Versions: 4.4.0.CR1-TP Reporter: Jozef Marko Assignee: Jozef Marko Update the creation of the KieSession according to this hint: https://issues.jboss.org/browse/RHBPMS-4422?focusedCommentId=13312862&pag... -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-960) Mark the corresponding tests with knowIssues

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/JBTIS-960?page=com.atlassian.jira.plugin.... ] Jozef Marko updated JBTIS-960: ------------------------------ Description: Know issues are: * https://issues.jboss.org/browse/RHBPMS-4420 was: Know issues are: * https://issues.jboss.org/browse/RHBPMS-4420 * https://issues.jboss.org/browse/RHBPMS-4422 > Mark the corresponding tests with knowIssues > -------------------------------------------- > > Key: JBTIS-960 > URL: https://issues.jboss.org/browse/JBTIS-960 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: BPMN2, QE > Affects Versions: 4.4.0.CR1-TP > Reporter: Jozef Marko > Assignee: Jozef Marko > > Know issues are: > * https://issues.jboss.org/browse/RHBPMS-4420 -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23361) Filter text field in Server Editor's Deployment tab is too tall

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23361?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-23361. --------------------------------- Now it's correct. Verified in devstudio-10.2.0.AM3-v20161026-1715-B6309-installer-eap.jar > Filter text field in Server Editor's Deployment tab is too tall > --------------------------------------------------------------- > > Key: JBIDE-23361 > URL: https://issues.jboss.org/browse/JBIDE-23361 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.2.AM2 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.4.2.AM3 > > Attachments: deployment-filter-2.png, deployment-filter.png > > > After JBIDE-23134 changed the overall layout of the Deployment tab in Server Editor and the modules table, the filter text field is now too tall, as if it was 2 lines high. > Otherwise it seems to work perfectly fine. > !deployment-filter.png! -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23380) MOJO that fails or logs errors for build if manifest in .core plugin has .ui dependency

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23380?page=com.atlassian.jira.plugi... ] Martin Malina resolved JBIDE-23380. ----------------------------------- Resolution: Done The build works for me now after I updated my macOS and rebooted. Coincidentally another issue also disappeared after the reboot - JBIDE-23419 So it seems like my java might have been broken somehow. But it's really odd as it pretty rare to fix an issue with a reboot on macOS. > MOJO that fails or logs errors for build if manifest in .core plugin has .ui dependency > --------------------------------------------------------------------------------------- > > Key: JBIDE-23380 > URL: https://issues.jboss.org/browse/JBIDE-23380 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Rob Stryker > Assignee: Nick Boldt > Fix For: 4.4.2.AM3 > > > At a minimum, the mojo should: > foreach plugin, if plugin ends in .core, check plugin/META-INF/MANIFEST for Dependencies manifest header, and verify .ui is not included in the dependencies at all. > However, this minimum goal would not have solved the issue we are experiencing with foundation.checkup. The foundation.checkup plugin does not end in .core and so would be skipped by this simple algorithm. > So... we may wish to check transitive dependencies *only in the same repo*. For example, foundation.core depends on foundation.checker, and foundation.checker is in the same repo, so foundation.checker should also be checked for ui deps or fail. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23419) ClassNotFoundException when clicking on any server in Servers view

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23419?page=com.atlassian.jira.plugi... ] Martin Malina resolved JBIDE-23419. ----------------------------------- Resolution: Cannot Reproduce Bug Since I can't reproduce this any more, I am closing this. > ClassNotFoundException when clicking on any server in Servers view > ------------------------------------------------------------------ > > Key: JBIDE-23419 > URL: https://issues.jboss.org/browse/JBIDE-23419 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, server > Affects Versions: 4.4.2.AM3 > Reporter: Martin Malina > Priority: Blocker > > Today I opened up my laptop with a running devstudio [1]. And now whenever I click on a server in Servers view (I have a cdk and wildfly 10.1 set up), I get an error pop up. > {code} > An error has occurred. See error log for more details. > java.lang.ClassNotFoundException: Provider org.glassfish.jersey.internal.RuntimeDelegateImpl could not be instantiated: java.lang.IllegalStateException: No generator was provided and there is no default generator registered > {code} > Error Log view contains a bit more information: > {code} > Problems occurred when invoking code from plug-in: "org.eclipse.jface". > java.lang.RuntimeException: java.lang.ClassNotFoundException: Provider org.glassfish.jersey.internal.RuntimeDelegateImpl could not be instantiated: java.lang.IllegalStateException: No generator was provided and there is no default generator registered > at javax.ws.rs.ext.RuntimeDelegate.findDelegate(RuntimeDelegate.java:152) > at javax.ws.rs.ext.RuntimeDelegate.getInstance(RuntimeDelegate.java:120) > at javax.ws.rs.core.UriBuilder.newInstance(UriBuilder.java:95) > at javax.ws.rs.core.UriBuilder.fromUri(UriBuilder.java:106) > at org.glassfish.jersey.client.JerseyWebTarget.<init>(JerseyWebTarget.java:82) > at org.glassfish.jersey.client.JerseyClient.target(JerseyClient.java:192) > at org.glassfish.jersey.client.JerseyClient.target(JerseyClient.java:70) > at com.spotify.docker.client.DefaultDockerClient.ping(DefaultDockerClient.java:330) > at org.eclipse.linuxtools.internal.docker.core.DockerConnection.ping(DockerConnection.java:324) > at org.eclipse.linuxtools.internal.docker.core.DockerConnection.open(DockerConnection.java:270) > at org.eclipse.linuxtools.internal.docker.core.DefaultTCPConnectionSettingsProvider.getConnectionSettings(DefaultTCPConnectionSettingsProvider.java:30) > at org.eclipse.linuxtools.internal.docker.core.DefaultDockerConnectionSettingsFinder.getKnownConnectionSettings(DefaultDockerConnectionSettingsFinder.java:265) > at org.eclipse.linuxtools.docker.core.DockerConnectionManager.reloadConnections(DockerConnectionManager.java:60) > at org.eclipse.linuxtools.docker.core.DockerConnectionManager.<init>(DockerConnectionManager.java:50) > at org.eclipse.linuxtools.docker.core.DockerConnectionManager.getInstance(DockerConnectionManager.java:44) > at org.jboss.tools.openshift.cdk.server.core.internal.listeners.CDKDockerUtility.<init>(CDKDockerUtility.java:29) > at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInDockerViewAfterStartupAction.adaptToViewItem(CDKActionProvider.java:104) > at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInViewAfterStartupAction.accept(CDKActionProvider.java:182) > at org.eclipse.wst.server.ui.internal.view.servers.AbstractServerAction.selectionChanged(AbstractServerAction.java:85) > at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInViewAfterStartupAction.selectionChanged(CDKActionProvider.java:198) > at org.eclipse.ui.actions.SelectionProviderAction.selectionChanged(SelectionProviderAction.java:144) > at org.eclipse.jface.viewers.Viewer$1.run(Viewer.java:158) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50) > at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173) > at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.java:155) > at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2191) > at org.eclipse.jface.viewers.StructuredViewer.handleSelect(StructuredViewer.java:1229) > at org.eclipse.ui.navigator.CommonViewer.handleSelect(CommonViewer.java:463) > at org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(StructuredViewer.java:1258) > at org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(OpenStrategy.java:242) > at org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy.java:236) > at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:405) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4248) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1501) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1524) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1509) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1313) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4072) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687) > 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 sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > 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.ClassNotFoundException: Provider org.glassfish.jersey.internal.RuntimeDelegateImpl could not be instantiated: java.lang.IllegalStateException: No generator was provided and there is no default generator registered > at javax.ws.rs.ext.FactoryFinder.newInstance(FactoryFinder.java:122) > at javax.ws.rs.ext.FactoryFinder.find(FactoryFinder.java:225) > at javax.ws.rs.ext.RuntimeDelegate.findDelegate(RuntimeDelegate.java:135) > ... 61 more > Caused by: java.lang.IllegalStateException: No generator was provided and there is no default generator registered > at org.glassfish.hk2.internal.ServiceLocatorFactoryImpl.internalCreate(ServiceLocatorFactoryImpl.java:266) > at org.glassfish.hk2.internal.ServiceLocatorFactoryImpl.create(ServiceLocatorFactoryImpl.java:247) > at org.glassfish.jersey.internal.inject.Injections._createLocator(Injections.java:138) > at org.glassfish.jersey.internal.inject.Injections.createLocator(Injections.java:109) > at org.glassfish.jersey.internal.RuntimeDelegateImpl.<init>(RuntimeDelegateImpl.java:61) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:423) > at java.lang.Class.newInstance(Class.java:442) > at javax.ws.rs.ext.FactoryFinder.newInstance(FactoryFinder.java:118) > ... 63 more > {code} > I'm reporting this before it disappears. I don't have any way to replicate. I know it's not very helpful. I've never seen this before. > [1] devstudio-10.2.0.AM3-v20161024-1202-B6286-installer-standalone.jar -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-960) Mark the corresponding tests with knowIssues

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/JBTIS-960?page=com.atlassian.jira.plugin.... ] Jozef Marko updated JBTIS-960: ------------------------------ Description: Know issues are: * https://issues.jboss.org/browse/RHBPMS-4420 * https://issues.jboss.org/browse/RHBPMS-4422 was:Mark the given test with know issue: https://issues.jboss.org/browse/RHBPMS-4420 > Mark the corresponding tests with knowIssues > -------------------------------------------- > > Key: JBTIS-960 > URL: https://issues.jboss.org/browse/JBTIS-960 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: BPMN2, QE > Affects Versions: 4.4.0.CR1-TP > Reporter: Jozef Marko > Assignee: Jozef Marko > > Know issues are: > * https://issues.jboss.org/browse/RHBPMS-4420 > * https://issues.jboss.org/browse/RHBPMS-4422 -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-960) Mark the corresponding test with knowIssues

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/JBTIS-960?page=com.atlassian.jira.plugin.... ] Jozef Marko updated JBTIS-960: ------------------------------ Summary: Mark the corresponding test with knowIssues (was: Mark the ComplexDefinitionViaElementTest with known issue) > Mark the corresponding test with knowIssues > ------------------------------------------- > > Key: JBTIS-960 > URL: https://issues.jboss.org/browse/JBTIS-960 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: BPMN2, QE > Affects Versions: 4.4.0.CR1-TP > Reporter: Jozef Marko > Assignee: Jozef Marko > > Mark the given test with know issue: https://issues.jboss.org/browse/RHBPMS-4420 -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-960) Mark the corresponding tests with knowIssues

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/JBTIS-960?page=com.atlassian.jira.plugin.... ] Jozef Marko updated JBTIS-960: ------------------------------ Summary: Mark the corresponding tests with knowIssues (was: Mark the corresponding test with knowIssues) > Mark the corresponding tests with knowIssues > -------------------------------------------- > > Key: JBTIS-960 > URL: https://issues.jboss.org/browse/JBTIS-960 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: BPMN2, QE > Affects Versions: 4.4.0.CR1-TP > Reporter: Jozef Marko > Assignee: Jozef Marko > > Mark the given test with know issue: https://issues.jboss.org/browse/RHBPMS-4420 -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 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 October 2016