You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2014/05/02 15:43:14 UTC
[jira] [Created] (SLING-3541) Standalone Launchpad Archetype fails
to start due to random selection of jarWebSupport
Robert Munteanu created SLING-3541:
--------------------------------------
Summary: Standalone Launchpad Archetype fails to start due to random selection of jarWebSupport
Key: SLING-3541
URL: https://issues.apache.org/jira/browse/SLING-3541
Project: Sling
Issue Type: Bug
Components: Maven Plugins and Archetypes
Affects Versions: Launchpad Standalone Archetype 1.0.0
Reporter: Robert Munteanu
Assignee: Robert Munteanu
Fix For: Launchpad Standalone Archetype 1.0.2
After generating an archetype it fails to start
{code}
[INFO] --- maven-launchpad-plugin:2.3.0:run (default-cli) @ launchpad ---
[INFO] Using bundle list file from /home/ADOBENET/rmuntean/.m2/repository/org/apache/sling/org.apache.sling.launchpad/6/org.apache.sling.launchpad-6-bundlelist.xml
[INFO] HTTP server port: 8080
INFO: Command file absent or older than last execution timestamp, nothing to execute (/home/ADOBENET/rmuntean/tmp/launchpad/sling/sling_bootstrap.txt)
INFO: Ignoring /home/ADOBENET/rmuntean/tmp/launchpad/sling/startup/1/org.apache.sling.commons.log-2.1.2.jar: More recent version already installed
INFO: Ignoring /home/ADOBENET/rmuntean/tmp/launchpad/sling/startup/1/org.apache.felix.http.jetty-2.3.0-R1579739.jar: More recent version already installed
INFO: Ignoring /home/ADOBENET/rmuntean/tmp/launchpad/sling/startup/1/org.apache.felix.http.jetty-2.2.2.jar: More recent version already installed
INFO: Using timestamp from file:/home/ADOBENET/rmuntean/.m2/repository/org/apache/sling/maven-launchpad-plugin/2.3.0/maven-launchpad-plugin-2.3.0.jar.
INFO: Using timestamp from file:/home/ADOBENET/rmuntean/.m2/repository/org/apache/sling/maven-launchpad-plugin/2.3.0/maven-launchpad-plugin-2.3.0.jar.
INFO: Using timestamp from /home/ADOBENET/rmuntean/tmp/launchpad/sling/startup/1/org.apache.sling.commons.log-2.1.2.jar.
INFO: Final self timestamp: 1399037235000.
INFO: Started startup handler with target start level=35, and expected bundle count=3
INFO: Startup progress 1/3
INFO: Startup progress 1/3
ERROR: Bundle org.apache.felix.http.jetty [2]: Error starting slinginstall:org.apache.felix.http.jetty-2.3.0-R1579739.jar (org.osgi.framework.BundleException: Unresolved constraint in bundle org.apache.felix.http.jetty [2]: Unable to resolve 2.0: missing requirement [2.0] package; (&(package=javax.servlet)(version>=3.0.0)(!(version>=4.0.0))))
org.osgi.framework.BundleException: Unresolved constraint in bundle org.apache.felix.http.jetty [2]: Unable to resolve 2.0: missing requirement [2.0] package; (&(package=javax.servlet)(version>=3.0.0)(!(version>=4.0.0)))
at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3443)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1727)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1156)
at org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264)
at java.lang.Thread.run(Thread.java:744)
{code}
We should set the org.apache.felix.http.jetty bundle version to the one expected by the configured defaultBundleList.
--
This message was sent by Atlassian JIRA
(v6.2#6252)