You could add Makdown4j as embedded dependency inside your pom, something felix maven plugin supports [1]. It does not have to be an OSGi bundle. It will just get embedded in your OSGi bundles’ jar and added to it’s internal classpath. You could also try to add it to the /apps/<appDir>/install in Sling. I believe jcrinstaller has some magic to wrap it as OSGi bundle even if it does not have OSGi manifest headers. I think neither one of these are great solutions. It would be better to actually add Markdown as another supported scripting/templating option to Sling in its own bundle. But for your purpose these would work.
By the way I am experimenting with Sightly+Sling and will probably work on an example. I am thinking implementing a blog would be an interesting exercise. If you are interested I could put something in github. But most likely it will not be this holiday weekend. :) Sightly is a new templating engine that was just contributed by Adobe to Sling. [1] http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html On Dec 30, 2014, at 3:01 PM, Sylvain Wallez <[email protected]> wrote: > Ok, got it running. There was a node.js server running on port 8080 on my > machine and for some reason Sling was answering requests in the browser, but > node.js was answering to Maven deploy requests. Go figure... > > I started implenting within espblog an observer to capture the content of a > markdown file written using WebDAV. Works fine once I remembered that on a > nt:file, jcr:content is an actual node with a jcr:data property! > > And then I found out that the Markdown4J library I added to the POM doesn't > have an OSGI manifest file. This holiday evenings project turns out to be > rather complicated :-) > > I'm not sure I'll end up with something that deserves to be contributed, but > want to thank you guys for the support in helping me dive into Sling! > > Sylvain > > > Le 30/12/2014 10:23, Bertrand Delacretaz a écrit : >> On Tue, Dec 30, 2014 at 12:30 AM, Henry Saginor <[email protected]> wrote: >>> ...if you can access the web console you can also upload/install the bundle >>> manually from there (from http://localhost:8080/system/console/bundles), >>> just to get going.... >> Yes, or also via WebDAV, just copy the required bundles under a folder >> named "install" not more than 5 (or 4, I never remember) levels deep >> under /apps. >> >> So /apps/espblog/install for example would do it. >> >> Apart from that I have no idea why the maven-sling-plugin can say "not >> found" if http://localhost:8080/system/console works - it's just doing >> an HTTP POST on that URL. Maybe look at the sling/logs/error.log. >> >> -Bertrand > > > -- > Sylvain Wallez - http://bluxte.net >
