Startup delay due to OSGI bundle resolving - eclipse

I'm currently trying to migrate our product to work on jdk 11 and as a part of this effort upgraded the osgi framework (upgrading from equinox osgi version 3.9.1.v20130814-1242). We managed to upgrade the components and start the pack but currently we see high startup time (startup freezes in the middle for some additional time). we suspect it is due to bundle wiring.
I checked the bundle status using ss comand and all the bundles were in Active state.
Then I enabled osgi debug logs for wiring (org.eclipse.osgi/resolver/wiring) and notice one component trying to wire to same component repeatedly
Following is a part of the log. similar repeated logs for different components can be seen during this startup freeze time . (I attached the full log in http://download2265.mediafire.com/cov16dra60kg/n808avzytuv3xxb/logs.txt)
RESOLVER: Wirings for resolved bundles:
Resource
osgi.identity; osgi.identity="tomcat"; type="osgi.bundle"; version:Version="7.0.85.wso2v1"
Wiring
[1] osgi.wiring.package; filter:="(osgi.wiring.package=*)"; resolution:="dynamic"; cardinality:="multiple" -> [osgi.identity; osgi.identity="axiom"; type="osgi.bundle"; version:Version="1.2.11.wso2v12"]
RESOLVER: Wirings for resolved bundles:
Resource
osgi.identity; osgi.identity="tomcat"; type="osgi.bundle"; version:Version="7.0.85.wso2v1"
Wiring
[1] osgi.wiring.package; filter:="(osgi.wiring.package=*)"; resolution:="dynamic"; cardinality:="multiple" -> [osgi.identity; osgi.identity="axiom"; type="osgi.bundle"; version:Version="1.2.11.wso2v12"]
RESOLVER: Wirings for resolved bundles:
Resource
osgi.identity; osgi.identity="tomcat"; type="osgi.bundle"; version:Version="7.0.85.wso2v1"
Wiring
[1] osgi.wiring.package; filter:="(osgi.wiring.package=*)"; resolution:="dynamic"; cardinality:="multiple" -> [osgi.identity; osgi.identity="axiom"; type="osgi.bundle"; version:Version="1.2.11.wso2v12"]
RESOLVER: Wirings for resolved bundles:
Resource
osgi.identity; osgi.identity="tomcat"; type="osgi.bundle"; version:Version="7.0.85.wso2v1"
Wiring
[1] osgi.wiring.package; filter:="(osgi.wiring.package=*)"; resolution:="dynamic"; cardinality:="multiple" -> [osgi.identity; osgi.identity="axiom"; type="osgi.bundle"; version:Version="1.2.11.wso2v12"]
RESOLVER: Wirings for resolved bundles:
Resource
osgi.identity; osgi.identity="tomcat"; type="osgi.bundle"; version:Version="7.0.85.wso2v1"
Wiring
[1] osgi.wiring.package; filter:="(osgi.wiring.package=*)"; resolution:="dynamic"; cardinality:="multiple" -> [osgi.identity; osgi.identity="axiom"; type="osgi.bundle"; version:Version="1.2.11.wso2v12"]
Can anyone please help me in identifying the problem and why it tries to wire to same package (any additional methods to narrowdown the issue). Same tomcat version was used in the old OSGI version but didn't see this kind of freezing in the middle.
Thanks a lot

Related

Eclipse constantly crashing - could not resolve mylyn module

My installation of Eclipse 2022-09 is crashing constantly, either it freezes and then crashes, or just crashes silently.
I've noticed that it happens when the code completion tooltip is triggered, but not always.
On restart the error log contains the following
org.osgi.framework.BundleException: Could not resolve module: org.eclipse.mylyn.team.ui [2581]
Unresolved requirement: Require-Bundle: org.eclipse.mylyn.tasks.ui; bundle-version="[3.8.0,4.0.0)"
-> Bundle-SymbolicName: org.eclipse.mylyn.tasks.ui; bundle-version="3.25.2.v20200814-0512"; singleton:="true"
org.eclipse.mylyn.tasks.ui [2580]
Unresolved requirement: Require-Bundle: org.eclipse.mylyn.commons.notifications.feed; bundle-version="1.0.0"
-> Bundle-SymbolicName: org.eclipse.mylyn.commons.notifications.feed; bundle-version="1.17.2.v20200813-0821"; singleton:="true"
org.eclipse.mylyn.commons.notifications.feed [2553]
No resolution report for the bundle. Bundle was not resolved because of a uses constraint violation.
org.apache.felix.resolver.reason.ReasonException: Uses constraint violation. Unable to resolve resource org.eclipse.mylyn.commons.notifications.feed [osgi.identity; type="osgi.bundle"; version:Version="1.17.2.v20200813-0821"; osgi.identity="org.eclipse.mylyn.commons.notifications.feed"; singleton:="true"] because it is exposed to package 'javax.xml.bind' from resources javax.xml.bind [osgi.identity; type="osgi.bundle"; version:Version="2.2.0.v201105210648"; osgi.identity="javax.xml.bind"] and jakarta.xml.bind [osgi.identity; type="osgi.bundle"; version:Version="2.3.3.v20201118-1818"; osgi.identity="jakarta.xml.bind"] via two dependency chains.
Chain 1:
org.eclipse.mylyn.commons.notifications.feed [osgi.identity; type="osgi.bundle"; version:Version="1.17.2.v20200813-0821"; osgi.identity="org.eclipse.mylyn.commons.notifications.feed"; singleton:="true"]
require: (&(osgi.wiring.bundle=javax.xml.bind)(bundle-version>=2.2.0))
|
provide: osgi.wiring.bundle: javax.xml.bind
javax.xml.bind [osgi.identity; type="osgi.bundle"; version:Version="2.2.0.v201105210648"; osgi.identity="javax.xml.bind"]
Chain 2:
org.eclipse.mylyn.commons.notifications.feed [osgi.identity; type="osgi.bundle"; version:Version="1.17.2.v20200813-0821"; osgi.identity="org.eclipse.mylyn.commons.notifications.feed"; singleton:="true"]
require: (&(osgi.wiring.bundle=com.sun.xml.bind)(bundle-version>=2.2.0))
|
provide: osgi.wiring.bundle; bundle-version:Version="2.3.3.v20201118-1818"; osgi.wiring.bundle="com.sun.xml.bind"
com.sun.xml.bind [osgi.identity; type="osgi.bundle"; version:Version="2.3.3.v20201118-1818"; osgi.identity="com.sun.xml.bind"]
import: (&(osgi.wiring.package=javax.xml.bind)(&(version>=2.3.3)(!(version>=2.3.4))))
|
export: osgi.wiring.package: javax.xml.bind
jakarta.xml.bind [osgi.identity; type="osgi.bundle"; version:Version="2.3.3.v20201118-1818"; osgi.identity="jakarta.xml.bind"]
at org.eclipse.osgi.container.Module.start(Module.java:463)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel$2.run(ModuleContainer.java:1852)
at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor$1$1.execute(EquinoxContainerAdaptor.java:136)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1845)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1786)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1750)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1672)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:234)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:345)
Short of a reinstall, can this be fixed?
After removing Mylyn, as recommended, the crashes are still occuring, with the following in the error log view
Still crashing, pasting in code into a window is causing the crashes, albeit intermittently.
This is in the error log
eclipse.buildId=4.25.0.I20220831-1800
java.version=19
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_IE
Framework arguments: -product org.eclipse.epp.package.jee.product
Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product
org.eclipse.core.resources
Warning
Fri Oct 14 15:48:23 IST 2022
The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.

Non parseable POM causing Maven build, installs to fail

I am unable to run Maven configuration using my Eclipse IDE hosted on my Mac. It keeps on failing with the message that it is unable to parse a maven enforcer plugin file (see message below). There has not been any change to my Eclipse environment, my Maven project, my Maven configuration or my POM file. This was working fine 3-4 months back. Yesterday I cleaned up my entire repository (under $home/.m2) folder along with files under it and after that I am getting this error. It appears the maven download process is encountering issue. My eclipse plugin (m2e) uses version 1.10. I know it is a maven related issue but any help will be greatly appreciated
[DEBUG] === REACTOR BUILD PLAN ================================================
[DEBUG] Project: fda-spl-fhir:fda-spl-fhir:war:3.8.0
[DEBUG] Tasks: [install]
[DEBUG] Style: Regular
[DEBUG] =======================================================================
[INFO]
[INFO] ---------------------< fda-spl-fhir:fda-spl-fhir >----------------------
[INFO] Building HAPI FHIR JPA Server - Starter Project 3.8.0
[INFO] --------------------------------[ war ]---------------------------------
[DEBUG] Lifecycle default -> [validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy]
[DEBUG] Lifecycle clean -> [pre-clean, clean, post-clean]
[DEBUG] Lifecycle site -> [pre-site, site, post-site, site-deploy]
[WARNING] The POM for org.apache.maven.plugins:maven-enforcer-plugin:jar:3.0.0-M2 is invalid, transitive dependencies (if any) will not be available: 1 problem was encountered while building the effective model
[FATAL] Non-parseable POM /Users/XXXXXX/.m2/repository/org/apache/maven/plugins/maven-enforcer-plugin/3.0.0-M2/maven-enforcer-plugin-3.0.0-M2.pom: entity reference name can not contain character =' (position: START_TAG seen ...com/main?ParticipantID=euekiz39ksg8nwp7iqj2fp5wzfwi5q76&FailedURI=... #1:270) # line 1, column 270
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 0.220 s
[INFO] Finished at: 2020-02-06T13:38:42-05:00
[INFO] ------------------------------------------------------------------------
[ERROR] Plugin org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M2 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-enforcer-plugin:jar:3.0.0-M2: 1 problem was encountered while building the effective model
[ERROR] [FATAL] Non-parseable POM /Users/XXXXXX/.m2/repository/org/apache/maven/plugins/maven-enforcer-plugin/3.0.0-M2/maven-enforcer-plugin-3.0.0-M2.pom: entity reference name can not contain character =' (position: START_TAG seen ...com/main?ParticipantID=euekiz39ksg8nwp7iqj2fp5wzfwi5q76&FailedURI=... #1:270) # line 1, column 270
[ERROR] -> [Help 1]
org.apache.maven.plugin.PluginResolutionException: Plugin org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M2 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-enforcer-plugin:jar:3.0.0-M2
at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:117)
at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getPluginDescriptor(DefaultMavenPluginManager.java:181)
at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getMojoDescriptor(DefaultMavenPluginManager.java:286)
at org.apache.maven.plugin.DefaultBuildPluginManager.getMojoDescriptor(DefaultBuildPluginManager.java:244)
at org.apache.maven.lifecycle.internal.DefaultLifecycleMappingDelegate.calculateLifecycleMappings(DefaultLifecycleMappingDelegate.java:115)
at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateLifecycleMappings(DefaultLifecycleExecutionPlanCalculator.java:265)
at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateMojoExecutions(DefaultLifecycleExecutionPlanCalculator.java:216)
at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateExecutionPlan(DefaultLifecycleExecutionPlanCalculator.java:126)
at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateExecutionPlan(DefaultLifecycleExecutionPlanCalculator.java:144)
at org.apache.maven.lifecycle.internal.builder.BuilderCommon.resolveBuildPlan(BuilderCommon.java:96)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:110)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:956)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:290)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:194)
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.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.eclipse.aether.resolution.ArtifactDescriptorException: Failed to read artifact descriptor for org.apache.maven.plugins:maven-enforcer-plugin:jar:3.0.0-M2
at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:332)
at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:192)
at org.eclipse.aether.internal.impl.DefaultRepositorySystem.readArtifactDescriptor(DefaultRepositorySystem.java:253)
at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:103)
... 27 more
Caused by: org.apache.maven.model.building.ModelBuildingException: 1 problem was encountered while building the effective model
[FATAL] Non-parseable POM /Users/XXXXXX/.m2/repository/org/apache/maven/plugins/maven-enforcer-plugin/3.0.0-M2/maven-enforcer-plugin-3.0.0-M2.pom: entity reference name can not contain character =' (position: START_TAG seen ...com/main?ParticipantID=euekiz39ksg8nwp7iqj2fp5wzfwi5q76&FailedURI=... #1:270) # line 1, column 270
at org.apache.maven.model.building.DefaultModelProblemCollector.newModelBuildingException(DefaultModelProblemCollector.java:197)
at org.apache.maven.model.building.DefaultModelBuilder.readModel(DefaultModelBuilder.java:582)
at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:276)
at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:314)
... 30 more
[ERROR]
[ERROR]
Thanks in advance for your help
As you probably know, Maven uses HTTP/HTTPS to fetch remote dependencies.
Sometimes the Maven repository that it uses is available only when you are connected to a VPN, or is otherwise sometimes unreachable. For example, your employer may have a private Maven repository that works when you're at work, but is unreachable at home.
Some Internet service providers (wrongly) do not return 404 error codes when you ask your browser to locate an unreachable URL. Instead, they return an HTML page with ads or other stuff on it that "help" you try to locate what you were looking for.
When you put all of these concepts together, if Maven uses HTTP to try to fetch a dependency from an unreachable Maven repository URL, it will fetch a page of HTML instead. In your case, you can see from your error message that there is something in that .pom file that looks like perhaps this is what happened.
The solution is to remove the containing directory from your local Maven cache (e.g. /Users/XXXXXX/.m2/repository/org/apache/maven/plugins/maven-enforcer-plugin/) and run Maven again when you know that you have a reliable network connection.

Hi There, I am new to use JBOSS Fuse, i have download the zip file and extracted it . But its not working at all

ERROR: Bundle io.fabric8.fabric-zookeeper [53] Error starting mvn:io.fabric8/fabric-zookeeper/1.0.0.redhat-379 (org.osgi.framework.BundleException: Unresolved constraint in bundle io.fabric8.fabric-zookeeper [53]: Unable to resolve 53.0: missing requirement [53.0] osgi.wiring.package; (&(osgi.wiring.package=com.google.common.base)(version>=15.0.0)(!(version>=16.0.0))))
org.osgi.framework.BundleException: Unresolved constraint in bundle io.fabric8.fabric-zookeeper [53]: Unable to resolve 53.0: missing requirement [53.0] osgi.wiring.package; (&(osgi.wiring.package=com.google.common.base)(version>=15.0.0)(!(version>=16.0.0)))
at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4225)
at org.apache.felix.framework.Felix.startBundle(Felix.java:2063)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1317)
at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:304)
at java.lang.Thread.run(Thread.java:748)
ERROR: Bundle jackson-mapper-asl [54] Error starting mvn:org.codehaus.jackson/jackson-mapper-asl/1.9.12 (org.osgi.framework.BundleException: Unresolved constraint in bundle jackson-mapper-asl [54]: Unable to resolve 54.0: missing requirement [54.0] osgi.wiring.package; (osgi.wiring.package=javax.xml.datatype))
org.osgi.framework.BundleException: Unresolved constraint in bundle jackson-mapper-asl [54]: Unable to resolve 54.0: missing requirement [54.0] osgi.wiring.package; (osgi.wiring.package=javax.xml.datatype)
at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4225)
at org.apache.felix.framework.Felix.startBundle(Felix.java:2063)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1317)
at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:304)
at java.lang.Thread.run(Thread.java:748)
8% [=====> ]ERROR: Bundle org.apache.servicemix.bundles.jasypt [56] Error starting mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.jasypt/1.9.1_1 (org.osgi.framework.BundleException: Unresolved constraint in bundle org.apache.servicemix.bundles.jasypt [56]: Unable to resolve 56.0: missing requirement [56.0] osgi.wiring.package; (osgi.wiring.package=javax.crypto))
org.osgi.framework.BundleException: Unresolved constraint in bundle org.apache.servicemix.bundles.jasypt [56]: Unable to resolve 56.0: missing requirement [56.0] osgi.wiring.package; (osgi.wiring.package=javax.crypto)
at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4225)
at org.apache.felix.framework.Felix.startBundle(Felix.java:2063)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1317)
at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:304)
at java.lang.Thread.run(Thread.java:748)
11% [=======> ]ERROR: Bundle org.fusesource.insight.insight-log [59] Error starting mvn:org.fusesource.insight/insight-log/1.0.0.redhat-379 (org.osgi.framework.BundleException: Unresolved constraint in bundle org.fusesource.insight.insight-log [59]: Unable to resolve 59.0: missing requirement [59.0] osgi.wiring.package; (osgi.wiring.package=javax.management))
org.osgi.framework.BundleException: Unresolved constraint in bundle org.fusesource.insight.insight-log [59]: Unable to resolve 59.0: missing requirement [59.0] osgi.wiring.package; (osgi.wiring.package=javax.management)
at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4225)
at org.apache.felix.framework.Felix.startBundle(Felix.java:2063)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1317)
at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:304)
at java.lang.Thread.run(Thread.java:748)
ERROR: Bundle io.fabric8.fabric-agent [60] Error starting mvn:io.fabric8/fabric-agent/1.0.0.redhat-379 (org.osgi.framework.BundleException: Unresolved constraint in bundle io.fabric8.fabric-agent [60]: Unable to resolve 60.0: missing requirement [60.0] osgi.wiring.package; (&(osgi.wiring.package=io.fabric8.api)(version>=1.0.0)(!(version>=2.0.0))) [caused by: Unable to resolve 62.0: missing requirement [62.0] osgi.wiring.package; (osgi.wiring.package=javax.xml.parsers)])
org.osgi.framework.BundleException: Unresolved constraint in bundle io.fabric8.fabric-agent [60]: Unable to resolve 60.0: missing requirement [60.0] osgi.wiring.package; (&(osgi.wiring.package=io.fabric8.api)(version>=1.0.0)(!(version>=2.0.0))) [caused by: Unable to resolve 62.0: missing requirement [62.0] osgi.wiring.package; (osgi.wiring.package=javax.xml.parsers)]
at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4225)
at org.apache.felix.framework.Felix.startBundle(Felix.java:2063)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1317)
at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:304)
at java.lang.Thread.run(Thread.java:748)
ERROR: Bundle scala-library [61] Error starting mvn:com.weiglewilczek.scala-lang-osgi/scala-library/2.9.1 (org.osgi.framework.BundleException: Unresolved constraint in bundle scala-library [61]: Unable to resolve 61.0: missing requirement [61.0] osgi.wiring.package; (osgi.wiring.package=javax.xml.parsers))
org.osgi.framework.BundleException: Unresolved constraint in bundle scala-library [61]: Unable to resolve 61.0: missing requirement [61.0] osgi.wiring.package; (osgi.wiring.package=javax.xml.parsers)
at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4225)
at org.apache.felix.framework.Felix.startBundle(Felix.java:2063)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1317)
at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:304)
at java.lang.Thread.run(Thread.java:748)
ERROR: Bundle io.fabric8.fabric-api [62] Error starting mvn:io.fabric8/fabric-api/1.0.0.redhat-379 (org.osgi.framework.BundleException: Unresolved constraint in bundle io.fabric8.fabric-api [62]: Unable to resolve 62.0: missing requirement [62.0] osgi.wiring.package; (osgi.wiring.package=javax.xml.parsers))
org.osgi.framework.BundleException: Unresolved constraint in bundle io.fabric8.fabric-api [62]: Unable to resolve 62.0: missing requirement [62.0] osgi.wiring.package; (osgi.wiring.package=javax.xml.parsers)
at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4225)
at org.apache.felix.framework.Felix.startBundle(Felix.java:2063)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1317)
at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:304)
at java.lang.Thread.run(Thread.java:748)
ERROR: Bundle io.fabric8.fabric-boot-commands [63] Error starting mvn:io.fabric8/fabric-boot-commands/1.0.0.redhat-379 (org.osgi.framework.BundleException: Unresolved constraint in bundle io.fabric8.fabric-boot-commands [63]: Unable to resolve 63.0: missing requirement [63.0] osgi.wiring.package; (&(osgi.wiring.package=com.google.common.base)(version>=15.0.0)(!(version>=16.0.0))))
org.osgi.framework.BundleException: Unresolved constraint in bundle io.fabric8.fabric-boot-commands [63]: Unable to resolve 63.0: missing requirement [63.0] osgi.wiring.package; (&(osgi.wiring.package=com.google.common.base)(version>=15.0.0)(!(version>=16.0.0)))
at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4225)
at org.apache.felix.framework.Felix.startBundle(Felix.java:2063)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1317)
at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:304)
at java.lang.Thread.run(Thread.java:748)
ERROR: Bundle org.apache.servicemix.bundles.jsch [64] Error starting mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.jsch/0.1.49_1 (org.osgi.framework.BundleException: Unresolved constraint in bundle org.apache.servicemix.bundles.jsch [64]: Unable to resolve 64.0: missing requirement [64.0] osgi.wiring.package; (osgi.wiring.package=javax.crypto))
org.osgi.framework.BundleException: Unresolved constraint in bundle org.apache.servicemix.bundles.jsch [64]: Unable to resolve 64.0: missing requirement [64.0] osgi.wiring.package; (osgi.wiring.package=javax.crypto)
at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4225)
at org.apache.felix.framework.Felix.startBundle(Felix.java:2063)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1317)
at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:304)
at java.lang.Thread.run(Thread.java:748)
ERROR: Bundle io.fabric8.fabric-core [65] Error starting mvn:io.fabric8/fabric-core/1.0.0.redhat-379 (org.osgi.framework.BundleException: Unresolved constraint in bundle io.fabric8.fabric-core [65]: Unable to resolve 65.0: missing requirement [65.0] osgi.wiring.package; (&(osgi.wiring.package=com.google.common.base)(version>=15.0.0)(!(version>=16.0.0))))
org.osgi.framework.BundleException: Unresolved constraint in bundle io.fabric8.fabric-core [65]: Unable to resolve 65.0: missing requirement [65.0] osgi.wiring.package; (&(osgi.wiring.package=com.google.common.base)(version>=15.0.0)(!(version>=16.0.0)))
at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4225)
at org.apache.felix.framework.Felix.startBundle(Felix.java:2063)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1317)
at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:304)
at java.lang.Thread.run(Thread.java:748)
ERROR: Bundle io.fabric8.fabric-commands [66] Error starting mvn:io.fabric8/fabric-commands/1.0.0.redhat-379 (org.osgi.framework.BundleException: Unresolved constraint in bundle io.fabric8.fabric-commands [66]: Unable to resolve 66.0: missing requirement [66.0] osgi.wiring.package; (&(osgi.wiring.package=com.google.common.base)(version>=15.0.0)(!(version>=16.0.0))))
org.osgi.framework.BundleException: Unresolved constraint in bundle io.fabric8.fabric-commands [66]: Unable to resolve 66.0: missing requirement [66.0] osgi.wiring.package; (&(osgi.wiring.package=com.google.common.base)(version>=15.0.0)(!(version>=16.0.0)))
at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4225)
at org.apache.felix.framework.Felix.startBundle(Felix.java:2063)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1317)
at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:304)
at java.lang.Thread.run(Thread.java:748)
ERROR: Bundle io.fabric8.fabric-configadmin [67] Error starting mvn:io.fabric8/fabric-configadmin/1.0.0.redhat-379 (org.osgi.framework.BundleException: Unresolved constraint in bundle io.fabric8.fabric-configadmin [67]: Unable to resolve 67.0: missing requirement [67.0] osgi.wiring.package; (&(osgi.wiring.package=io.fabric8.api)(version>=1.0.0)(!(version>=2.0.0))) [caused by: Unable to resolve 62.0: missing requirement [62.0] osgi.wiring.package; (osgi.wiring.package=javax.xml.parsers)])
org.osgi.framework.BundleException: Unresolved constraint in bundle io.fabric8.fabric-configadmin [67]: Unable to resolve 67.0: missing requirement [67.0] osgi.wiring.package; (&(osgi.wiring.package=io.fabric8.api)(version>=1.0.0)(!(version>=2.0.0))) [caused by: Unable to resolve 62.0: missing requirement [62.0] osgi.wiring.package; (osgi.wiring.package=javax.xml.parsers)]
at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4225)
at org.apache.felix.framework.Felix.startBundle(Felix.java:2063)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1317)
at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:304)
at java.lang.Thread.run(Thread.java:748)
ERROR: Bundle org.jboss.fuse.esb-commands [68] Error starting mvn:org.jboss.fuse/esb-commands/6.1.0.redhat-379 (org.osgi.framework.BundleException: Unresolved constraint in bundle org.jboss.fuse.esb-commands [68]: Unable to resolve 68.0: missing requirement [68.0] osgi.wiring.package; (osgi.wiring.package=javax.security.auth))
org.osgi.framework.BundleException: Unresolved constraint in bundle org.jboss.fuse.esb-commands [68]: Unable to resolve 68.0: missing requirement [68.0] osgi.wiring.package; (osgi.wiring.package=javax.security.auth)
at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4225)
at org.apache.felix.framework.Felix.startBundle(Felix.java:2063)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1317)
at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:304)
at java.lang.Thread.run(Thread.java:748)
using redhat fuse 6.x will be perfect with java 6 and java 7 and not be stable or not working with java 8.
while I recommend using redhat fuse 7.x with Java 8 as it is more stable and supported right now.
https://developer.jboss.org/thread/250544
This is because of the version of jboss fuse you are working with. If the version is 6.1 then you have to use either java 6 or java 7. If you are using higher version, Then you will get this error.
You can search for compatible version with downloaded fuse. Please check
etc/jre.properties in the fuse installation folder.

Eclipse fails after installing JBoss Tools

After installing JBoss Tools and restarting Eclipse IDE, I get following exception:
An error has occured. See the log file /home/abc/workspace/.metadata/.log
Eclipse does not start anymore. Can anybody help me, to fix this problem?
My setup:
Eclipse Version: Neon 2
OS: Fedora 25
JBoss Tools Update Site: https://download.jboss.org/jbosstools/updates/stable/
Log File:
!SESSION Wed Mar 22 21:41:43 CET 2017 ------------------------------------------
!ENTRY org.eclipse.equinox.launcher 4 0 2017-03-22 21:41:43.812
!MESSAGE Could not find extension: org.eclipse.wst.jsdt.nashorn.extension
!SESSION 2017-03-22 21:41:43.742 -----------------------------------------------
eclipse.buildId=4.6.2.v20170109-1424
java.version=1.8.0_121
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=de_CH
Command-line arguments: -os linux -ws gtk -arch x86_64
!ENTRY org.eclipse.osgi 4 0 2017-03-22 21:41:44.473
!MESSAGE Bundle org.eclipse.wst.jsdt.nashorn.extension not found.
!ENTRY org.jboss.tools.vpe.cordovasim.eclipse 4 0 2017-03-22 21:41:45.447
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.vpe.cordovasim.eclipse [1051]
Unresolved requirement: Require-Bundle: org.jboss.tools.vpe.cordovasim; bundle-version="3.5.0"
-> Bundle-SymbolicName: org.jboss.tools.vpe.cordovasim; bundle-version="3.5.1.Final-v20140303-0018-B169"
org.jboss.tools.vpe.cordovasim [1050]
No resolution report for the bundle. Bundle was not resolved because of a uses contraint violation.
org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.jboss.tools.vpe.cordovasim [osgi.identity; type="osgi.bundle"; version:Version="3.5.1.Final-v20140303-0018-B169"; osgi.identity="org.jboss.tools.vpe.cordovasim"] because it is exposed to package 'org.eclipse.jetty.continuation' from resources org.eclipse.jetty.continuation [osgi.identity; type="osgi.bundle"; version:Version="9.4.0.M0"; osgi.identity="org.eclipse.jetty.continuation"] and org.eclipse.jetty.continuation [osgi.identity; type="osgi.bundle"; version:Version="8.1.14.v20131031"; osgi.identity="org.eclipse.jetty.continuation"] via two dependency chains.
Chain 1:
org.jboss.tools.vpe.cordovasim [osgi.identity; type="osgi.bundle"; version:Version="3.5.1.Final-v20140303-0018-B169"; osgi.identity="org.jboss.tools.vpe.cordovasim"]
require: (&(osgi.wiring.bundle=org.eclipse.jetty.continuation)(bundle-version>=8.1.3))
|
provide: osgi.wiring.bundle: org.eclipse.jetty.continuation
org.eclipse.jetty.continuation [osgi.identity; type="osgi.bundle"; version:Version="9.4.0.M0"; osgi.identity="org.eclipse.jetty.continuation"]
Chain 2:
org.jboss.tools.vpe.cordovasim [osgi.identity; type="osgi.bundle"; version:Version="3.5.1.Final-v20140303-0018-B169"; osgi.identity="org.jboss.tools.vpe.cordovasim"]
require: (&(osgi.wiring.bundle=org.eclipse.jetty.servlets)(bundle-version>=8.1.3))
|
provide: osgi.wiring.bundle; bundle-version:Version="8.1.10.v20130312"; osgi.wiring.bundle="org.eclipse.jetty.servlets"
org.eclipse.jetty.servlets [osgi.identity; type="osgi.bundle"; version:Version="8.1.10.v20130312"; osgi.identity="org.eclipse.jetty.servlets"]
import: (&(osgi.wiring.package=org.eclipse.jetty.server)(&(version>=8.1.0)(!(version>=9.0.0))))
|
export: osgi.wiring.package=org.eclipse.jetty.server; uses:=org.eclipse.jetty.continuation
org.eclipse.jetty.server [osgi.identity; type="osgi.bundle"; version:Version="8.1.14.v20131031"; osgi.identity="org.eclipse.jetty.server"]
import: (&(osgi.wiring.package=org.eclipse.jetty.continuation)(&(version>=8.1.0)(!(version>=9.0.0))))
|
export: osgi.wiring.package: org.eclipse.jetty.continuation
org.eclipse.jetty.continuation [osgi.identity; type="osgi.bundle"; version:Version="8.1.14.v20131031"; osgi.identity="org.eclipse.jetty.continuation"]
at org.eclipse.osgi.container.Module.start(Module.java:444)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1620)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1599)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1571)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1514)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
!ENTRY org.eclipse.ui 2 0 2017-03-22 21:41:47.664
!MESSAGE Warnings while parsing the commands from the 'org.eclipse.ui.commands' and 'org.eclipse.ui.actionDefinitions' extension points.
!SUBENTRY 1 org.eclipse.ui 2 0 2017-03-22 21:41:47.664
!MESSAGE Commands should really have a category: plug-in='net.sf.eclipsecs.ui', id='CheckstylePlugin.PurgeCaches', categoryId='net.sf.eclipsecs'
!ENTRY org.eclipse.ui 2 0 2017-03-22 21:41:48.283
!MESSAGE Warnings while parsing the commands from the 'org.eclipse.ui.commands' and 'org.eclipse.ui.actionDefinitions' extension points.
!SUBENTRY 1 org.eclipse.ui 2 0 2017-03-22 21:41:48.283
!MESSAGE Commands should really have a category: plug-in='net.sf.eclipsecs.ui', id='CheckstylePlugin.PurgeCaches', categoryId='net.sf.eclipsecs'
!ENTRY org.jboss.tools.xulrunner.initializer 2 0 2017-03-22 21:41:50.274
!MESSAGE Could not resolve module: org.jboss.tools.xulrunner.initializer [1068]
Unresolved requirement: Fragment-Host: org.eclipse.swt
Unresolved requirement: Fragment-Host: org.eclipse.swt
!ENTRY org.jboss.tools.vpe.cordovasim.eclipse 2 0 2017-03-22 21:41:50.281
!MESSAGE Could not resolve module: org.jboss.tools.vpe.cordovasim.eclipse [1051]
Unresolved requirement: Require-Bundle: org.jboss.tools.vpe.cordovasim; bundle-version="3.5.0"
-> Bundle-SymbolicName: org.jboss.tools.vpe.cordovasim; bundle-version="3.5.1.Final-v20140303-0018-B169"
org.jboss.tools.vpe.cordovasim [1050]
Bundle was not resolved because of a uses contraint violation.
org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.jboss.tools.vpe.cordovasim [osgi.identity; type="osgi.bundle"; version:Version="3.5.1.Final-v20140303-0018-B169"; osgi.identity="org.jboss.tools.vpe.cordovasim"] because it is exposed to package 'org.eclipse.jetty.continuation' from resources org.eclipse.jetty.continuation [osgi.identity; type="osgi.bundle"; version:Version="9.4.0.M0"; osgi.identity="org.eclipse.jetty.continuation"] and org.eclipse.jetty.continuation [osgi.identity; type="osgi.bundle"; version:Version="8.1.14.v20131031"; osgi.identity="org.eclipse.jetty.continuation"] via two dependency chains.
Chain 1:
org.jboss.tools.vpe.cordovasim [osgi.identity; type="osgi.bundle"; version:Version="3.5.1.Final-v20140303-0018-B169"; osgi.identity="org.jboss.tools.vpe.cordovasim"]
require: (&(osgi.wiring.bundle=org.eclipse.jetty.continuation)(bundle-version>=8.1.3))
|
provide: osgi.wiring.bundle: org.eclipse.jetty.continuation
org.eclipse.jetty.continuation [osgi.identity; type="osgi.bundle"; version:Version="9.4.0.M0"; osgi.identity="org.eclipse.jetty.continuation"]
Chain 2:
org.jboss.tools.vpe.cordovasim [osgi.identity; type="osgi.bundle"; version:Version="3.5.1.Final-v20140303-0018-B169"; osgi.identity="org.jboss.tools.vpe.cordovasim"]
require: (&(osgi.wiring.bundle=org.eclipse.jetty.servlets)(bundle-version>=8.1.3))
|
provide: osgi.wiring.bundle; bundle-version:Version="8.1.10.v20130312"; osgi.wiring.bundle="org.eclipse.jetty.servlets"
org.eclipse.jetty.servlets [osgi.identity; type="osgi.bundle"; version:Version="8.1.10.v20130312"; osgi.identity="org.eclipse.jetty.servlets"]
import: (&(osgi.wiring.package=org.eclipse.jetty.server)(&(version>=8.1.0)(!(version>=9.0.0))))
|
export: osgi.wiring.package=org.eclipse.jetty.server; uses:=org.eclipse.jetty.continuation
org.eclipse.jetty.server [osgi.identity; type="osgi.bundle"; version:Version="8.1.14.v20131031"; osgi.identity="org.eclipse.jetty.server"]
import: (&(osgi.wiring.package=org.eclipse.jetty.continuation)(&(version>=8.1.0)(!(version>=9.0.0))))
|
export: osgi.wiring.package: org.eclipse.jetty.continuation
org.eclipse.jetty.continuation [osgi.identity; type="osgi.bundle"; version:Version="8.1.14.v20131031"; osgi.identity="org.eclipse.jetty.continuation"] Bundle was not resolved because of a uses contraint violation.
org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.jboss.tools.vpe.cordovasim [osgi.identity; type="osgi.bundle"; version:Version="3.5.1.Final-v20140303-0018-B169"; osgi.identity="org.jboss.tools.vpe.cordovasim"] because it is exposed to package 'org.eclipse.jetty.continuation' from resources org.eclipse.jetty.continuation [osgi.identity; type="osgi.bundle"; version:Version="9.4.0.M0"; osgi.identity="org.eclipse.jetty.continuation"] and org.eclipse.jetty.continuation [osgi.identity; type="osgi.bundle"; version:Version="8.1.14.v20131031"; osgi.identity="org.eclipse.jetty.continuation"] via two dependency chains.
Chain 1:
org.jboss.tools.vpe.cordovasim [osgi.identity; type="osgi.bundle"; version:Version="3.5.1.Final-v20140303-0018-B169"; osgi.identity="org.jboss.tools.vpe.cordovasim"]
require: (&(osgi.wiring.bundle=org.eclipse.jetty.continuation)(bundle-version>=8.1.3))
|
provide: osgi.wiring.bundle: org.eclipse.jetty.continuation
org.eclipse.jetty.continuation [osgi.identity; type="osgi.bundle"; version:Version="9.4.0.M0"; osgi.identity="org.eclipse.jetty.continuation"]
Chain 2:
org.jboss.tools.vpe.cordovasim [osgi.identity; type="osgi.bundle"; version:Version="3.5.1.Final-v20140303-0018-B169"; osgi.identity="org.jboss.tools.vpe.cordovasim"]
require: (&(osgi.wiring.bundle=org.eclipse.jetty.servlets)(bundle-version>=8.1.3))
|
provide: osgi.wiring.bundle; bundle-version:Version="8.1.10.v20130312"; osgi.wiring.bundle="org.eclipse.jetty.servlets"
org.eclipse.jetty.servlets [osgi.identity; type="osgi.bundle"; version:Version="8.1.10.v20130312"; osgi.identity="org.eclipse.jetty.servlets"]
import: (&(osgi.wiring.package=org.eclipse.jetty.server)(&(version>=8.1.0)(!(version>=9.0.0))))
|
export: osgi.wiring.package=org.eclipse.jetty.server; uses:=org.eclipse.jetty.continuation
org.eclipse.jetty.server [osgi.identity; type="osgi.bundle"; version:Version="8.1.14.v20131031"; osgi.identity="org.eclipse.jetty.server"]
import: (&(osgi.wiring.package=org.eclipse.jetty.continuation)(&(version>=8.1.0)(!(version>=9.0.0))))
|
export: osgi.wiring.package: org.eclipse.jetty.continuation
org.eclipse.jetty.continuation [osgi.identity; type="osgi.bundle"; version:Version="8.1.14.v20131031"; osgi.identity="org.eclipse.jetty.continuation"]
!ENTRY org.jboss.tools.foundation.security.linux 2 0 2017-03-22 21:41:50.282
!MESSAGE Could not resolve module: org.jboss.tools.foundation.security.linux [997]
Unresolved requirement: Fragment-Host: org.eclipse.equinox.security; bundle-version="1.1.100"
Unresolved requirement: Fragment-Host: org.eclipse.equinox.security; bundle-version="1.1.100"
!ENTRY org.jboss.tools.vpe.cordovasim 2 0 2017-03-22 21:41:50.282
!MESSAGE Could not resolve module: org.jboss.tools.vpe.cordovasim [1050]
Bundle was not resolved because of a uses contraint violation.
org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.jboss.tools.vpe.cordovasim [osgi.identity; type="osgi.bundle"; version:Version="3.5.1.Final-v20140303-0018-B169"; osgi.identity="org.jboss.tools.vpe.cordovasim"] because it is exposed to package 'org.eclipse.jetty.continuation' from resources org.eclipse.jetty.continuation [osgi.identity; type="osgi.bundle"; version:Version="9.4.0.M0"; osgi.identity="org.eclipse.jetty.continuation"] and org.eclipse.jetty.continuation [osgi.identity; type="osgi.bundle"; version:Version="8.1.14.v20131031"; osgi.identity="org.eclipse.jetty.continuation"] via two dependency chains.
Chain 1:
org.jboss.tools.vpe.cordovasim [osgi.identity; type="osgi.bundle"; version:Version="3.5.1.Final-v20140303-0018-B169"; osgi.identity="org.jboss.tools.vpe.cordovasim"]
require: (&(osgi.wiring.bundle=org.eclipse.jetty.continuation)(bundle-version>=8.1.3))
|
provide: osgi.wiring.bundle: org.eclipse.jetty.continuation
org.eclipse.jetty.continuation [osgi.identity; type="osgi.bundle"; version:Version="9.4.0.M0"; osgi.identity="org.eclipse.jetty.continuation"]
Chain 2:
org.jboss.tools.vpe.cordovasim [osgi.identity; type="osgi.bundle"; version:Version="3.5.1.Final-v20140303-0018-B169"; osgi.identity="org.jboss.tools.vpe.cordovasim"]
require: (&(osgi.wiring.bundle=org.eclipse.jetty.servlets)(bundle-version>=8.1.3))
|
provide: osgi.wiring.bundle; bundle-version:Version="8.1.10.v20130312"; osgi.wiring.bundle="org.eclipse.jetty.servlets"
org.eclipse.jetty.servlets [osgi.identity; type="osgi.bundle"; version:Version="8.1.10.v20130312"; osgi.identity="org.eclipse.jetty.servlets"]
import: (&(osgi.wiring.package=org.eclipse.jetty.server)(&(version>=8.1.0)(!(version>=9.0.0))))
|
export: osgi.wiring.package=org.eclipse.jetty.server; uses:=org.eclipse.jetty.continuation
org.eclipse.jetty.server [osgi.identity; type="osgi.bundle"; version:Version="8.1.14.v20131031"; osgi.identity="org.eclipse.jetty.server"]
import: (&(osgi.wiring.package=org.eclipse.jetty.continuation)(&(version>=8.1.0)(!(version>=9.0.0))))
|
export: osgi.wiring.package: org.eclipse.jetty.continuation
org.eclipse.jetty.continuation [osgi.identity; type="osgi.bundle"; version:Version="8.1.14.v20131031"; osgi.identity="org.eclipse.jetty.continuation"]
!ENTRY org.eclipse.osgi 4 0 2017-03-22 21:41:50.282
!MESSAGE Application error
!STACK 1
org.eclipse.e4.ui.css.core.sac.ParserNotFoundException: java.lang.ClassCastException: org.apache.batik.css.parser.Parser cannot be cast to org.w3c.css.sac.Parser
at org.eclipse.e4.ui.css.core.impl.dom.parsers.AbstractCSSParser.getParser(AbstractCSSParser.java:149)
at org.eclipse.e4.ui.css.core.impl.dom.parsers.AbstractCSSParser.parseStyleSheet(AbstractCSSParser.java:58)
at org.eclipse.e4.ui.css.core.impl.engine.AbstractCSSEngine.parseStyleSheet(AbstractCSSEngine.java:183)
at org.eclipse.e4.ui.css.swt.internal.theme.ThemeEngine.setTheme(ThemeEngine.java:428)
at org.eclipse.e4.ui.css.swt.internal.theme.ThemeEngine.setTheme(ThemeEngine.java:389)
at org.eclipse.e4.ui.css.swt.internal.theme.ThemeEngine.setTheme(ThemeEngine.java:381)
at org.eclipse.e4.ui.css.swt.internal.theme.ThemeEngine.restore(ThemeEngine.java:568)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.setCSSTheme(PartRenderingEngine.java:1399)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.initializeStyling(PartRenderingEngine.java:1292)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1026)
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:693)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:610)
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)
at org.eclipse.equinox.launcher.Main.main(Main.java:1492)
Caused by: java.lang.ClassCastException: org.apache.batik.css.parser.Parser cannot be cast to org.w3c.css.sac.Parser
at org.eclipse.e4.ui.css.core.impl.sac.SACParserFactoryImpl.makeParser(SACParserFactoryImpl.java:49)
at org.eclipse.e4.ui.css.core.sac.SACParserFactory.makeParser(SACParserFactory.java:36)
at org.eclipse.e4.ui.css.core.impl.dom.parsers.AbstractCSSParser.getParser(AbstractCSSParser.java:139)
... 30 more
The version of the JBoss Tools, which you get from this update site is from 2014. It's too old. The correct update site link is: http://download.jboss.org/jbosstools/neon/stable/updates/.
By now the latest stable version is 4.4.3.Final: http://tools.jboss.org/downloads/jbosstools/neon/4.4.3.Final.html
Other versions (development and nightly) you can find here: http://tools.jboss.org/downloads/jbosstools/neon/index.html
The best and easiest way to install jbosstools plugins to Eclipse is by using Eclipse Marketplace plugin: https://marketplace.eclipse.org/content/jboss-tools.
Old, but still actual video with instructions of how to install JBoss Tools via Eclipse Marketplace plugin: http://tools.jboss.org/downloads/installation.html
I've updated the README.html on the /updates/stable page [1] to point users to the latest JBoss Tools releases [2].
[1] http://download.jboss.org/jbosstools/updates/stable/
[2] http://tools.jboss.org/downloads/jbosstools/
Also updated the composite*.xml files in [1] to point to the Neon release, though this URL should not be considered current at all times (as you saw, it was pointing you at the JBoss Tools 4.1 release based on Eclipse Kepler, not the 4.4 release based on Neon).

Installing Tycho via Maven with offline flag

I want to run Tycho in an offline environment. Therefore, I mirrored a demo repository on GitHub and executed the command mvn clean install on a computer with internet access. The build succeeded, however when I try to run mvn -o install to install all dependencies in offline mode, I recieve the following exception:
C:\Users\user\Documents\MVN_Test\itp01>mvn clean -e -o install
[INFO] Error stacktraces are turned on.
[INFO] Scanning for projects...
[WARNING] No explicit target runtime environment configuration. Build is platform dependent.
[INFO] Computing target platform for MavenProject: tycho.demo.itp01:tycho.demo.itp01:1.0.0-SNAPSHOT # C:\Users\user\Documents\MVN_Test\itp01\tycho.demo.itp01\pom.xml
[INFO] Adding repository http://download.eclipse.org/releases/helios
[ERROR] Internal error: java.lang.RuntimeException: Failed to load p2 repository with ID 'helios' from location http://download.eclipse.org/releases/helios: Repository system is offline and no local cache available for http://download.eclipse.org/releases/helios -> [Help 1]
org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: Failed to load p2 repository with ID 'helios' from location http://download.eclipse.org/releases/helios
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:121)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
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:497)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: java.lang.RuntimeException: Failed to load p2 repository with ID 'helios' from location http://download.eclipse.org/releases/helios
at org.eclipse.tycho.p2.target.TargetPlatformFactoryImpl.loadMetadataRepository(TargetPlatformFactoryImpl.java:302)
at org.eclipse.tycho.p2.target.TargetPlatformFactoryImpl.gatherExternalInstallableUnits(TargetPlatformFactoryImpl.java:270)
at org.eclipse.tycho.p2.target.TargetPlatformFactoryImpl.createTargetPlatform(TargetPlatformFactoryImpl.java:176)
at org.eclipse.tycho.p2.target.TargetPlatformFactoryImpl.createTargetPlatform(TargetPlatformFactoryImpl.java:128)
at org.eclipse.tycho.p2.target.TargetPlatformFactoryImpl.createTargetPlatform(TargetPlatformFactoryImpl.java:1)
at org.eclipse.tycho.p2.manager.ReactorRepositoryManagerImpl.computePreliminaryTargetPlatform(ReactorRepositoryManagerImpl.java:84)
at org.eclipse.tycho.p2.resolver.P2DependencyResolver.computePreliminaryTargetPlatform(P2DependencyResolver.java:223)
at org.eclipse.tycho.core.resolver.DefaultTychoResolver.resolveProject(DefaultTychoResolver.java:109)
at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:95)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:266)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
... 11 more
Caused by: org.eclipse.equinox.p2.core.ProvisionException: Repository system is offline and no local cache available for http://download.eclipse.org/releases/helios
at org.eclipse.tycho.p2.remote.RemoteRepositoryCacheManager.createCache(RemoteRepositoryCacheManager.java:57)
at org.eclipse.equinox.internal.p2.metadata.repository.SimpleMetadataRepositoryFactory.getLocalFile(SimpleMetadataRepositoryFactory.java:66)
at org.eclipse.equinox.internal.p2.metadata.repository.SimpleMetadataRepositoryFactory.load(SimpleMetadataRepositoryFactory.java:88)
at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.factoryLoad(MetadataRepositoryManager.java:57)
at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:768)
at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:668)
at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96)
at org.eclipse.tycho.p2.remote.RemoteMetadataRepositoryManager.loadRepository(RemoteMetadataRepositoryManager.java:61)
at org.eclipse.tycho.p2.remote.RemoteMetadataRepositoryManager.loadRepository(RemoteMetadataRepositoryManager.java:53)
at org.eclipse.tycho.p2.target.TargetPlatformFactoryImpl.loadMetadataRepository(TargetPlatformFactoryImpl.java:298)
... 22 more
[ERROR]
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/InternalErrorException
I have found the following information, these may be a bug:
Demo project which demonstrates offline build failure
The problem is reproducible always with the following steps:
rm -rf ~/.m2/repository
unzip demo-project.zip
cd mvn-demo-parent/releng
mvn clean install
Build succeeds
mvn clean -o clean install
Build fails because "Repository system is offline and no local cache available for http:// download.eclipse.org/releases/mars"
From Bug 474885 - Build with -o flag fails with "Failed to resolve target definition" message:
This was a bug in tycho 0.24.0 and fixed in Tycho 0.25.0.
To use tycho 0.25.0 From Tycho/Release Notes/0.25
Tycho 0.25.0 is currently in development. To try out the most recent snapshot build of 0.25.0, simply add the following snippet to your (parent) pom.xml or settings.xml, and set the property for the Tycho version (e.g. tycho-version) to 0.25.0-SNAPSHOT.
<pluginRepositories>
<pluginRepository>
<id>tycho-snapshots</id>
<url>https://repo.eclipse.org/content/repositories/tycho-snapshots/</url>
</pluginRepository>
</pluginRepositories>