January 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16309) Move inter-JBT dependencies to component poms

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16309?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-16309: ------------------------------------------ done for OpenShift: https://github.com/jbosstools/jbosstools-openshift/pull/344 > Move inter-JBT dependencies to component poms > --------------------------------------------- > > Key: JBIDE-16309 > URL: https://issues.jboss.org/browse/JBIDE-16309 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.2.0.Alpha2 > > > It has been discussed several times that the composite site is a kind of "weak point" in our build chain, because it allows cyclic dependencies, and it also introduces indirections that make it less straightforward to find out what a project should/does depend on to build. > The benefit of composite now seem a bit light: it's cool because we can put it in parent pom and all builds succeed to get there dependencies, but out of that, there hasn't been much other use-cases. And as we want to provide more and more autonomy to project, this composite site they'd depend on is something that doesn't make them autonomous. > So the idea is to move dependencies to project root poms. I've made a draft of how it would look like in project pom if we remove the "jbosstools-site" from parent pom and let projects manage their inter-dependencies: https://github.com/mickaelistria/jbosstools-javaee/tree/JBIDE-16309 > You can try this by running "mvn clean verify -P\!jbosstools-site". The "-P\!jbosstools-site" disable the jbosstools-site profile, which is the one controlling addition of the composite or ggregate to the resolver > https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16309) Move inter-JBT dependencies to component poms

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16309?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-16309: ---------------------------------------- Still pending: * https://github.com/jbosstools/jbosstools-central/pull/201 [~fbricon] * https://github.com/jbosstools/jbosstools-hibernate/pull/35 [~koen.aers] * https://github.com/jbosstools/jbosstools-openshift/pull/344 [~adietish] * https://github.com/jbosstools/jbosstools-server/pull/186 [~rob.stryker] > Move inter-JBT dependencies to component poms > --------------------------------------------- > > Key: JBIDE-16309 > URL: https://issues.jboss.org/browse/JBIDE-16309 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.2.0.Alpha2 > > > It has been discussed several times that the composite site is a kind of "weak point" in our build chain, because it allows cyclic dependencies, and it also introduces indirections that make it less straightforward to find out what a project should/does depend on to build. > The benefit of composite now seem a bit light: it's cool because we can put it in parent pom and all builds succeed to get there dependencies, but out of that, there hasn't been much other use-cases. And as we want to provide more and more autonomy to project, this composite site they'd depend on is something that doesn't make them autonomous. > So the idea is to move dependencies to project root poms. I've made a draft of how it would look like in project pom if we remove the "jbosstools-site" from parent pom and let projects manage their inter-dependencies: https://github.com/mickaelistria/jbosstools-javaee/tree/JBIDE-16309 > You can try this by running "mvn clean verify -P\!jbosstools-site". The "-P\!jbosstools-site" disable the jbosstools-site profile, which is the one controlling addition of the composite or ggregate to the resolver > https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16262) README.md still points to community.jboss.org

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16262?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-16262: ---------------------------------------- [~mmurray] Should this README.md changes be tagged as documentation? Those files are aimed at guiding people looking at our GitHub repositories (potential contributors). > README.md still points to community.jboss.org > --------------------------------------------- > > Key: JBIDE-16262 > URL: https://issues.jboss.org/browse/JBIDE-16262 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Mickael Istria > Priority: Minor > Fix For: 4.2.0.Alpha2 > > > README.md still point to community.jboss.org, which isn't up to date and nor maintained any more. > Those files should be updated to point to https://github.com/jbosstools/jbosstools-devdoc -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16262) README.md still points to community.jboss.org

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16262?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-16262: ----------------------------------- Priority: Minor (was: Major) > README.md still points to community.jboss.org > --------------------------------------------- > > Key: JBIDE-16262 > URL: https://issues.jboss.org/browse/JBIDE-16262 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Mickael Istria > Priority: Minor > Fix For: 4.2.0.Alpha2 > > > README.md still point to community.jboss.org, which isn't up to date and nor maintained any more. > Those files should be updated to point to https://github.com/jbosstools/jbosstools-devdoc -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-447) Explain how to configure SSL options for connecting to Enterprise Servers.

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-447?page=com.atlassian.jira.plug... ] Andre Dietisheim edited comment on TOOLSDOC-447 at 1/17/14 3:38 AM: -------------------------------------------------------------------- We have planned to inform and allow user to accept/refuse non-valid SSL certificates but didnt implement it yet: JBIDE-14768 So in the current state we blindly accept any certificate. was (Author: adietish): We have planned to inform and allow user to accept/refuse non-valid SSL certificates but didnt implement it yet: JBIDE-14768 > Explain how to configure SSL options for connecting to Enterprise Servers. > -------------------------------------------------------------------------- > > Key: TOOLSDOC-447 > URL: https://issues.jboss.org/browse/TOOLSDOC-447 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: User Guide - OpenShift Tools > Affects Versions: 4.1.1 > Environment: Build Name: 22443, User Guide-7.1 > Build Date: 11-12-2013 15:10:49 > Topic ID: 25166-566980 [Latest] > Reporter: Eric Rich > Assignee: Michelle Murray > Priority: Minor > Fix For: 4.2.0 > > > Title: Customizing Overview > Describe the issue: > It would be good to explain configuration options for connecting to multiple or different Enterprise Servers. > Also explaining how to manage your SSL certificates or update them for connection to Enterprise Servers or Online would be helpful. > Suggestions for improvement: > Additional information: -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-447) Explain how to configure SSL options for connecting to Enterprise Servers.

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-447?page=com.atlassian.jira.plug... ] Andre Dietisheim commented on TOOLSDOC-447: ------------------------------------------- We have planned to inform and allow user to accept/refuse non-valid SSL certificates but didnt implement it yet: JBIDE-14768 > Explain how to configure SSL options for connecting to Enterprise Servers. > -------------------------------------------------------------------------- > > Key: TOOLSDOC-447 > URL: https://issues.jboss.org/browse/TOOLSDOC-447 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: User Guide - OpenShift Tools > Affects Versions: 4.1.1 > Environment: Build Name: 22443, User Guide-7.1 > Build Date: 11-12-2013 15:10:49 > Topic ID: 25166-566980 [Latest] > Reporter: Eric Rich > Assignee: Michelle Murray > Priority: Minor > Fix For: 4.2.0 > > > Title: Customizing Overview > Describe the issue: > It would be good to explain configuration options for connecting to multiple or different Enterprise Servers. > Also explaining how to manage your SSL certificates or update them for connection to Enterprise Servers or Online would be helpful. > Suggestions for improvement: > Additional information: -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16311) release 4.2.0.Alpha1 webtools site to so WTP discovery upstream can find it

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16311?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-16311: ---------------------------------------- You can already try to install the latest Integration build (towards M5) of WTP and check whether the catalog is updated: http://download.eclipse.org/webtools/downloads/drops/R3.6.0/I-3.6.0-20140... > release 4.2.0.Alpha1 webtools site to so WTP discovery upstream can find it > --------------------------------------------------------------------------- > > Key: JBIDE-16311 > URL: https://issues.jboss.org/browse/JBIDE-16311 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, updatesite > Affects Versions: 4.2.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.2.0.Alpha2 > > Attachments: eclipse44-installed-all-features-from jbt-wtp-site-4.2.0.Alpha1.png, eclipse44-installed-all-features-from jbt-wtp-site-4.2.0.Alpha1_2.png > > > Need a semi-working placeholder (even if it's a weak first alpha) so that WTP can resolve http://download.jboss.org/jbosstools/updates/webtools/luna/ as a valid site. > Content that needs to be verified (install tested) and renamed is here: > http://download.jboss.org/jbosstools/updates/JBossTools-4.2.0.Alpha1.webt... > Upstream issue: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=424213 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16374) Application wizard: should be able to see all domains/apps when choosing an existing application

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-16374: ---------------------------------------- Summary: Application wizard: should be able to see all domains/apps when choosing an existing application Key: JBIDE-16374 URL: https://issues.jboss.org/browse/JBIDE-16374 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.1.1.Final Reporter: Andre Dietisheim Fix For: 4.2.x Attachments: choose-existing-application.png When choosing an existing application one should be able to see all domains and applications. The current UI is only showing the applications that are within the domain that you selected in the parent page via the domain-combo: !choose-existing-application.png! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16374) Application wizard: should be able to see all domains/apps when choosing an existing application

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16374?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16374: ------------------------------------- Attachment: choose-existing-application.png > Application wizard: should be able to see all domains/apps when choosing an existing application > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-16374 > URL: https://issues.jboss.org/browse/JBIDE-16374 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.1.Final > Reporter: Andre Dietisheim > Fix For: 4.2.x > > Attachments: choose-existing-application.png > > > When choosing an existing application one should be able to see all domains and applications. The current UI is only showing the applications that are within the domain that you selected in the parent page via the domain-combo: > !choose-existing-application.png! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15807) Eclipe 4.4M3 with jbosstoolstarget-4.40.0.Alpa1-SNAPSHOT target platform does not start

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15807?page=com.atlassian.jira.plugi... ] Mickael Istria resolved JBIDE-15807. ------------------------------------ Fix Version/s: 4.2.0.Alpha2 (was: 4.2.x) Resolution: Done Thanks for the feedback [~kmarmaliykov] > Eclipe 4.4M3 with jbosstoolstarget-4.40.0.Alpa1-SNAPSHOT target platform does not start > --------------------------------------------------------------------------------------- > > Key: JBIDE-15807 > URL: https://issues.jboss.org/browse/JBIDE-15807 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.2.0.Alpha1 > Reporter: Daniel Azarov > Assignee: Denis Golovin > Priority: Minor > Fix For: 4.2.0.Alpha2 > > Attachments: mat.png, scr.png > > > 1. I tried to run JBDS from developer's environment with vm args - -XX:MaxPermSize=512m -Xms1024m -Xmx2048m with all plugins from my workspace > and I got follow exception: > {code} > java.lang.OutOfMemoryError: Java heap space > at java.util.HashMap.createEntry(HashMap.java:869) > at java.util.HashMap.addEntry(HashMap.java:856) > at java.util.HashMap.put(HashMap.java:484) > at org.apache.felix.resolver.Candidates.copy(Candidates.java:1002) > at org.apache.felix.resolver.ResolverImpl.checkDynamicPackageSpaceConsistency(ResolverImpl.java:1288) > at org.apache.felix.resolver.ResolverImpl.checkPackageSpaceConsistency(ResolverImpl.java:1083) > at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:261) > at org.eclipse.osgi.container.ModuleResolver$ResolveProcess.resolve(ModuleResolver.java:652) > at org.eclipse.osgi.container.ModuleResolver.resolveDelta(ModuleResolver.java:75) > at org.eclipse.osgi.container.ModuleContainer.resolveAndApply(ModuleContainer.java:451) > at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:409) > at org.eclipse.osgi.container.ModuleContainer.refresh(ModuleContainer.java:877) > at org.eclipse.osgi.storage.Storage.discardBundlesOnLoad(Storage.java:206) > at org.eclipse.osgi.storage.Storage.createStorage(Storage.java:87) > at org.eclipse.osgi.internal.framework.EquinoxContainer.<init>(EquinoxContainer.java:75) > at org.eclipse.osgi.launch.Equinox.<init>(Equinox.java:31) > at org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:287) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:222) > 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:636) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) > at org.eclipse.equinox.launcher.Main.run(Main.java:1450) > at org.eclipse.equinox.launcher.Main.main(Main.java:1426) > {code} > 2. If I try to run new run configuration with only plugins from target platform I got follow stack trace: > {code} > !SESSION 2013-10-28 10:29:47.350 ----------------------------------------------- > eclipse.buildId=unknown > java.version=1.6.0_24 > java.vendor=Sun Microsystems Inc. > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product org.eclipse.platform.ide > Command-line arguments: -product org.eclipse.platform.ide -data /home/daniel/workspaces/JBDS_GIT/../runtime-New_configuration(2) -dev file:/home/daniel/workspaces/JBDS_GIT/.metadata/.plugins/org.eclipse.pde.core/New_configuration (2)/dev.properties -os linux -ws gtk -arch x86_64 -consoleLog > !ENTRY org.eclipse.equinox.simpleconfigurator 4 0 2013-10-28 10:36:19.748 > !MESSAGE FrameworkEvent ERROR > !STACK 0 > org.osgi.framework.BundleException: Exception in org.eclipse.equinox.internal.simpleconfigurator.Activator.start() of bundle org.eclipse.equinox.simpleconfigurator. > at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:782) > at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:717) > at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:869) > at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:257) > at org.eclipse.osgi.container.Module.doStart(Module.java:556) > at org.eclipse.osgi.container.Module.start(Module.java:427) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1455) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1438) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1416) > at org.eclipse.osgi.container.SystemModule.startWorker(SystemModule.java:216) > at org.eclipse.osgi.container.Module.doStart(Module.java:556) > at org.eclipse.osgi.container.Module.start(Module.java:427) > at org.eclipse.osgi.container.SystemModule.start(SystemModule.java:151) > at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:347) > at org.eclipse.osgi.launch.Equinox.start(Equinox.java:115) > at org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:310) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:222) > 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:616) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) > at org.eclipse.equinox.launcher.Main.run(Main.java:1450) > at org.eclipse.equinox.launcher.Main.main(Main.java:1426) > Caused by: java.lang.OutOfMemoryError: Java heap space > at java.util.HashMap.addEntry(HashMap.java:770) > at java.util.HashMap.put(HashMap.java:402) > at org.apache.felix.resolver.ResolverImpl.mergeUses(ResolverImpl.java:960) > at org.apache.felix.resolver.ResolverImpl.calculatePackageSpaces(ResolverImpl.java:787) > at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:252) > at org.eclipse.osgi.container.ModuleResolver$ResolveProcess.resolve(ModuleResolver.java:652) > at org.eclipse.osgi.container.ModuleResolver.resolveDelta(ModuleResolver.java:75) > at org.eclipse.osgi.container.ModuleContainer.resolveAndApply(ModuleContainer.java:451) > at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:409) > at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:399) > at org.eclipse.osgi.container.Module.start(Module.java:406) > at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:347) > at org.eclipse.equinox.internal.simpleconfigurator.ConfigApplier.startBundles(ConfigApplier.java:427) > at org.eclipse.equinox.internal.simpleconfigurator.ConfigApplier.install(ConfigApplier.java:109) > at org.eclipse.equinox.internal.simpleconfigurator.SimpleConfiguratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:182) > at org.eclipse.equinox.internal.simpleconfigurator.SimpleConfiguratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:196) > at org.eclipse.equinox.internal.simpleconfigurator.Activator.start(Activator.java:48) > at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:761) > at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1) > at java.security.AccessController.doPrivileged(Native Method) > at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:754) > at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:717) > at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:869) > at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:257) > at org.eclipse.osgi.container.Module.doStart(Module.java:556) > at org.eclipse.osgi.container.Module.start(Module.java:427) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1455) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1438) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1416) > at org.eclipse.osgi.container.SystemModule.startWorker(SystemModule.java:216) > at org.eclipse.osgi.container.Module.doStart(Module.java:556) > at org.eclipse.osgi.container.Module.start(Module.java:427) > Root exception: > java.lang.OutOfMemoryError: Java heap space > at java.util.HashMap.addEntry(HashMap.java:770) > at java.util.HashMap.put(HashMap.java:402) > at org.apache.felix.resolver.ResolverImpl.mergeUses(ResolverImpl.java:960) > at org.apache.felix.resolver.ResolverImpl.calculatePackageSpaces(ResolverImpl.java:787) > at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:252) > at org.eclipse.osgi.container.ModuleResolver$ResolveProcess.resolve(ModuleResolver.java:652) > at org.eclipse.osgi.container.ModuleResolver.resolveDelta(ModuleResolver.java:75) > at org.eclipse.osgi.container.ModuleContainer.resolveAndApply(ModuleContainer.java:451) > at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:409) > at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:399) > at org.eclipse.osgi.container.Module.start(Module.java:406) > at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:347) > at org.eclipse.equinox.internal.simpleconfigurator.ConfigApplier.startBundles(ConfigApplier.java:427) > at org.eclipse.equinox.internal.simpleconfigurator.ConfigApplier.install(ConfigApplier.java:109) > at org.eclipse.equinox.internal.simpleconfigurator.SimpleConfiguratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:182) > at org.eclipse.equinox.internal.simpleconfigurator.SimpleConfiguratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:196) > at org.eclipse.equinox.internal.simpleconfigurator.Activator.start(Activator.java:48) > at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:761) > at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1) > at java.security.AccessController.doPrivileged(Native Method) > at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:754) > at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:717) > at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:869) > at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:257) > at org.eclipse.osgi.container.Module.doStart(Module.java:556) > at org.eclipse.osgi.container.Module.start(Module.java:427) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1455) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1438) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1416) > at org.eclipse.osgi.container.SystemModule.startWorker(SystemModule.java:216) > at org.eclipse.osgi.container.Module.doStart(Module.java:556) > at org.eclipse.osgi.container.Module.start(Module.java:427) > {code} > 3. If I try same as 2. but with "Running Platform" as target platform - eclipse starts -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 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 2014