Hi,
I'm trying to get started using Sling and I am running into a number of
problems getting the launchpad up and running. I've seen the issue in
the archives (
http://mail-archives.apache.org/mod_mbox/sling-users/201308.mbox/ajax/%3C5201CF6A.9040400%40gmail.com%3E
) which indicates that I can't run the standalone jar on java 7.
I've checked out and attempted to build from sources and have worked
around the issue to do with eventing described here (
http://mail-archives.apache.org/mod_mbox/sling-users/201308.mbox/%3C458BFBB4-5A97-45D8-8350-B4CAF8996A71%40adobe.com%3E
) by disabling the tests. The build stalls when trying to stop the server.
The jar was generated so I attempted to run it following the 15 minute
tutorial, but as soon as I enter the first curl command to create a node
I get "problem accessing /content/mynode. Reason: NOT FOUND"
In the Sling error logs there are numerous references to
osgi.wiring.package as follows:
Unable to resolve 50.0: missing requirement [50.0] osgi.wiring.package;
(&(osgi.wiring.package=org.apache.sling.launchpad.api)(version>=1.1.0)(!(version>=2.0.0)))]]
at
org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:3962)
at org.apache.felix.framework.Felix.startBundle(Felix.java:2025)
at
org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1279)
at
org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:304)
at java.lang.Thread.run(Thread.java:722)
though the number 50 changes.
Can anyone offer any insight? I'm new to the Maven build process as
well, so it could well be something I'm doing there (ie I ran the
"install" goal with skip tests, perhaps this is not the correct goal?
Thanks,
Geoff
