To be clear, I'm a huge fan of Sling and concepts and engineering behind it. That's one of the reasons I'm working on broadening our adoption of the platform in my organization. One of the challenges of this is to be able to get someone up and running to the point where they can look around and see what's available.
As you mentioned, an initial quick start for developing and trying out. Yet if they go to the website and download the live jar to do just that, it will fail. Because it requires a version of Java that's two releases old, and unsupported. And yes, I don't know a single person in my organization, running Java 6. I think it's cool that you're angling towards a consistent rolling release, with maven integration. But if that's the aim why even bother making the Launchpad available? As it is now, it's broken and/or filled with bundles that are far older than what is currently available, is that really the first impression that you want people to have of the framework? -Jason -----Original Message----- From: Robert Munteanu [mailto:[email protected]] Sent: Monday, July 21, 2014 7:36 AM To: [email protected] Subject: Re: Sling Standalone Application won't start On Sun, Jul 20, 2014 at 4:07 AM, Jason Bailey <[email protected]> wrote: > Well that's a kick in the teeth to my plans to get it adopted. Does anyone on > the list know when the next stable release is? This isn't a direct answer to your question but hopefully sets you in the right direction. IMO you the Sling Launchpad is an everything-but-the-kitchen-sink deliverable that we provide for getting an initial quick start for development and trying out Sling. The recommended way is to create your launchpad where you include your own bundles, loosely based on the definition that the Sling launchpad has. A simple of starting with this is taking the development ( or stable ) Sling Launchpad and removing bundles you don't need. For quickly creating a launchpad project, you can use our sling-launchpad-standalone-archetype (or sling-launchpad-webapp-archetype is you want to produce a WAR file ). HTH, Robert
