On Wednesday 20 July 2016 15:00:26 Robert Munteanu wrote: > Hi, > > On Tue, 2016-07-19 at 18:53 +0200, Oliver Lietz wrote: > > hi all, > > > > I've added a new module org.apache.sling.testing.paxexam in > > trunk/testing > > recently. It provides Sling's Launchpad Karaf Features as Options > > for Pax > > Exam (without Karaf) to setup a Sling instance with less boilerplate > > code: > > > > * allows to run ITs in the same module (with the build artifact under > > test) > > * allows using different versions in build and tests > > * allows overriding of versions > > (snip) > > I really like this from an API point of view, as it makes it much > simpler to configure tests. > > A couple of thoughts: > > - there are notes about code being auto-generated. Can you add > instructions and/or scripts to SVN, allowing other to update as well?
Sure, the templates used to generate both Java files from Launchpad Karaf Features are already in SVN under resources. The code (some Java classes running from my IDE) reading the feature.xml and generating the Java sources needs some cleanup and optimization. The same code is also used to query Maven Central and to update dependencies in feature.xml – the paths to features and templates are hard-coded and guava is "fixed". I will come up with some kind of "application", fatjar or similar for easy usage. > - we still reference snapshots. I know this is how we currently keep > the launchpad, but we can't ship a release with tests pointing to > SNAPSHOT versions. Not sure what the best way to fix it is though. The only essential bundle is Oak Server, all other snapshots will be removed in the near future to not block a first release of Launchpad Karaf any longer. I've released a bunch of bundles in the past days to finally get rid of the snapshots and will not let any new snapshots in. Hence Testing PaxExam will not use snapshots. If you need snapshots for testing you can override the version using SlingVersionResolver. > I've also tried using this for moving the Sling ITs to Oak but failed, > let's continue that discussion in SLING-5870. Will have a look. Regards, O. > Robert
