You could just not use launchpad. I've created an OSGi project using
pax-construct. The project provisions all the required Sling Bundles,
which first must be built and installed in my local repository. In my
OSGi project provisioning, I just reference all the SNAPSHOT versions
if I want to work with trunk.
The maven-pax-plugin could probably just be included in the top-level
Sling pom instead, so you could do 'mvn clean install pax:provision'
to run the app during development. The launchpad would then be used
later for deploying your finished app.
-Andreas
On May 18, 2009, at 2:25 PM, Mike Müller wrote:
Hi
Replying to the head with some observations with a "user of sling
trunk" hat on rather than a core sling developer.
If I make changes to sling trunk (eg usermanager servlets)
and use the
launchpad..... nothing happens.
because launchpad depends on released versions and has nothing to do
with trunk.
Its just another patch that I have to maintain, which is Ok,
but it I
was coming to it fresh I would find it very confusing. (and
have done
for the last 20 minutes). There are some blindingly obvious
pointers... if you know were to look, like the bundle
versions in the
console.
IMHO that's exactly the problem (or the point of view) which I
encoutered also: If you make changes to the actual trunk or if
you like to test the latest committed patch in whatever bundle,
where not the most recent bundle is refered in the pom of
launchpad/bundles, you test something older with the launchpad app.
My workaround is, that I patch the poms of launchpad/bundles and
launchpad/app. I think there should be an easier way for developers
to use the latest code base.
best regards
mike
