On Wed, 2017-04-05 at 13:12 +0200, Oliver Lietz wrote: > On Wednesday 05 April 2017 11:56:56 Konrad Windszus wrote: > > For ITs we sometimes leverage dedicated test bundles (which should > > only be > > deployed for the purpose of running the IT). Those test bundles are > > usually > > not released (i.e. stay at 1.0.0-SNAPSHOT). But with PaxExam or > > even with > > the slingstart-maven-plugin it is now easily possible to have ITs > > in the > > same Maven module as the actual bundle (e.g. > > https://github.com/apache/sling/tree/trunk/bundles/extensions/valid > > ation/co > > re, leveraging PaxExam or > > https://github.com/apache/sling/tree/trunk/bundles/extensions/model > > s/valida > > tion-impl leveraging slingstart-maven-plugin). For the former I > > have the > > problem that doing a release on that is not possible because that > > still has > > a dependency to > > https://github.com/apache/sling/blob/trunk/bundles/extensions/valid > > ation/te > > st-services/pom.xml. What do you prefer: > > > > 1. Release with the Snapshot test dependency, leveraging > > http://maven.apache.org/maven-release/maven-release-plugin/prepare- > > mojo.htm > > l#allowTimestampedSnapshots, compare with > > http://stackoverflow.com/questions/37562658/release-project-with-sn > > apshot-t > > est-dependency or > > 2. Release the test-services as well? > > 3. Move test services into bundle under test when possible (see > Scripting > Thymeleaf for example)
+1 to that as well, I prefer it over 2. That being said, 2 is usually much easier to do and in the context of a release I would not ask for 3. Robert > > If 3. is not possible or to cumbersome, release test-services (2.). > > Regards, > O. > > > Thanks for your input, > > Konrad > >
