[JBoss JIRA] (JBDS-4200) Problem installing switchyard from devstudio IS 10.0.0.GA site into devstudio rpm
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-4200?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-4200:
---------------------------------
Fix Version/s: 10.x
(was: 10.2.0.GA)
> 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: Sub-task
> Components: integration, rpm, upstream
> Affects Versions: 10.2.0.GA
> Environment: RHEL7
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Fix For: 10.x
>
> 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
[JBoss JIRA] (JBIDE-23315) Connection wizard: "Advanced >>" Button is cropped
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23315?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-23315:
-----------------------------------------------
Use case that reproduces in my environment (Ubuntu + GTK3):
1. Ensure that OpenShift 3 connection is the recent one, by editing it.
2. From main Eclipse menu call File->New->New OpenShift Application.
Wizard should open on Sign-In page with recent OpenShift 3 connection.
Without PR 'Advanced' button is cropped, with PR it is fully visible.
> Connection wizard: "Advanced >>" Button is cropped
> --------------------------------------------------
>
> Key: JBIDE-23315
> URL: https://issues.jboss.org/browse/JBIDE-23315
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.Final
> Reporter: Aurélien Pupier
> Priority: Minor
> Labels: connection_wizard
> Fix For: 4.4.x
>
> Attachments: 2016-11-23 at 15-04-44.mp4, screenshot-1.png
>
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-17591) org.jboss.tools.common.el.core.test fails on Max OS X Mavericks
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17591?page=com.atlassian.jira.plugi... ]
Andre Dietisheim resolved JBIDE-17591.
--------------------------------------
Resolution: Out of Date
> org.jboss.tools.common.el.core.test fails on Max OS X Mavericks
> ---------------------------------------------------------------
>
> Key: JBIDE-17591
> URL: https://issues.jboss.org/browse/JBIDE-17591
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common
> Affects Versions: 4.2.0.Beta2
> Environment: Mac OS X Mavericks
> Reporter: Denis Golovin
> Assignee: Alexey Kazakov
> Fix For: 4.4.2.Final
>
> Attachments: org.jboss.tools.common.el.core.test.CommonELAllTests2.txt
>
>
> {code}junit.framework.AssertionFailedError
> at junit.framework.Assert.fail(Assert.java:55)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.Assert.assertNotNull(Assert.java:256)
> at junit.framework.Assert.assertNotNull(Assert.java:248)
> at junit.framework.TestCase.assertNotNull(TestCase.java:417)
> at org.jboss.tools.common.el.core.test.resolver.TypeInfoCollectorTest.testTypeResolution(TypeInfoCollectorTest.java:68)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
> at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)
> at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175)
> at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:123)
> at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:86)
> at org.eclipse.tycho.surefire.osgibooter.HeadlessTestApplication.run(HeadlessTestApplication.java:21)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:587)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:198)
> 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:379)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:233)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-17591) org.jboss.tools.common.el.core.test fails on Max OS X Mavericks
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17591?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-17591:
------------------------------------------
[builld #68|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_master_otherOS/68/] is blue
> org.jboss.tools.common.el.core.test fails on Max OS X Mavericks
> ---------------------------------------------------------------
>
> Key: JBIDE-17591
> URL: https://issues.jboss.org/browse/JBIDE-17591
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common
> Affects Versions: 4.2.0.Beta2
> Environment: Mac OS X Mavericks
> Reporter: Denis Golovin
> Assignee: Alexey Kazakov
> Fix For: 4.4.2.Final
>
> Attachments: org.jboss.tools.common.el.core.test.CommonELAllTests2.txt
>
>
> {code}junit.framework.AssertionFailedError
> at junit.framework.Assert.fail(Assert.java:55)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.Assert.assertNotNull(Assert.java:256)
> at junit.framework.Assert.assertNotNull(Assert.java:248)
> at junit.framework.TestCase.assertNotNull(TestCase.java:417)
> at org.jboss.tools.common.el.core.test.resolver.TypeInfoCollectorTest.testTypeResolution(TypeInfoCollectorTest.java:68)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
> at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)
> at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175)
> at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:123)
> at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:86)
> at org.eclipse.tycho.surefire.osgibooter.HeadlessTestApplication.run(HeadlessTestApplication.java:21)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:587)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:198)
> 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:379)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:233)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-17591) org.jboss.tools.common.el.core.test fails on Max OS X Mavericks
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17591?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-17591:
-------------------------------------
Fix Version/s: 4.4.2.Final
(was: 4.3.x)
> org.jboss.tools.common.el.core.test fails on Max OS X Mavericks
> ---------------------------------------------------------------
>
> Key: JBIDE-17591
> URL: https://issues.jboss.org/browse/JBIDE-17591
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common
> Affects Versions: 4.2.0.Beta2
> Environment: Mac OS X Mavericks
> Reporter: Denis Golovin
> Assignee: Alexey Kazakov
> Fix For: 4.4.2.Final
>
> Attachments: org.jboss.tools.common.el.core.test.CommonELAllTests2.txt
>
>
> {code}junit.framework.AssertionFailedError
> at junit.framework.Assert.fail(Assert.java:55)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.Assert.assertNotNull(Assert.java:256)
> at junit.framework.Assert.assertNotNull(Assert.java:248)
> at junit.framework.TestCase.assertNotNull(TestCase.java:417)
> at org.jboss.tools.common.el.core.test.resolver.TypeInfoCollectorTest.testTypeResolution(TypeInfoCollectorTest.java:68)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
> at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)
> at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175)
> at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:123)
> at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:86)
> at org.eclipse.tycho.surefire.osgibooter.HeadlessTestApplication.run(HeadlessTestApplication.java:21)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:587)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:198)
> 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:379)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:233)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-3328) generate/edit jboss modules content for easily deployment/config of jdbc driver
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBDS-3328?page=com.atlassian.jira.plugin.... ]
Andre Dietisheim updated JBDS-3328:
-----------------------------------
Fix Version/s: LATER
(was: 10.x)
> generate/edit jboss modules content for easily deployment/config of jdbc driver
> -------------------------------------------------------------------------------
>
> Key: JBDS-3328
> URL: https://issues.jboss.org/browse/JBDS-3328
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: server
> Reporter: Max Rydahl Andersen
> Assignee: Viacheslav Kabanovich
> Fix For: LATER
>
>
> in EAP7-56 its asked:
> "I can easily generate and deploy a JBoss Module from existing jars including JDBC Drivers and shared libraries. (Tooling to automatically generate module.xml and related artifacts by scanning classes from a library jar file, or pom.xml if provided e.g real life use case: creating modules for JDBC Type 4 Drivers )"
> this would be nice to have and linked with our datasource wizards.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-21727) add OpenShift server adapter to downloadable WTP server adapters
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21727?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-21727:
-------------------------------------
So do we still want this feature? Do we need to change our wtp update site? What needs to be done here? Gimme the tl;dr
> add OpenShift server adapter to downloadable WTP server adapters
> ----------------------------------------------------------------
>
> Key: JBIDE-21727
> URL: https://issues.jboss.org/browse/JBIDE-21727
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift, server
> Reporter: Max Rydahl Andersen
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.5.0.AM1
>
> Attachments: compositeArtifacts.xml, compositeContent.xml, mockup-change-1.png, mockup-change-2.png, openshiftv3-tools-server-adapter-manually-installed.png, openshiftv3-tools-server-adapter-no-license-found.png, openshiftv3-tools-server-adapter.png
>
>
> We have JBoss server adapters available in Eclise new Server wizard; would be great if we could put OpenShift in there too.
> Anything preventing us from doing so ?
> Is there a workflow from New server that helps users to create openshift connection etc. ?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-21727) add OpenShift server adapter to downloadable WTP server adapters
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21727?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21727:
-------------------------------------
Fix Version/s: 4.5.0.AM1
(was: 4.4.x)
> add OpenShift server adapter to downloadable WTP server adapters
> ----------------------------------------------------------------
>
> Key: JBIDE-21727
> URL: https://issues.jboss.org/browse/JBIDE-21727
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift, server
> Reporter: Max Rydahl Andersen
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.5.0.AM1
>
> Attachments: compositeArtifacts.xml, compositeContent.xml, mockup-change-1.png, mockup-change-2.png, openshiftv3-tools-server-adapter-manually-installed.png, openshiftv3-tools-server-adapter-no-license-found.png, openshiftv3-tools-server-adapter.png
>
>
> We have JBoss server adapters available in Eclise new Server wizard; would be great if we could put OpenShift in there too.
> Anything preventing us from doing so ?
> Is there a workflow from New server that helps users to create openshift connection etc. ?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[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:
-----------------------------
Summary: Problem installing switchyard from devstudio IS 10.0.0.GA site into devstudio rpm (was: Problem installing switchyard)
> 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: Sub-task
> Components: rpm
> Affects Versions: 10.2.0.GA
> Environment: RHEL7
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Fix For: 10.2.0.GA
>
> 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
[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:
-----------------------------
Component/s: integration
> 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: Sub-task
> Components: integration, rpm
> Affects Versions: 10.2.0.GA
> Environment: RHEL7
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Fix For: 10.2.0.GA
>
> 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