Hi Robert,
Am 28.11.16 um 23:32 schrieb Robert Munteanu:
On Fri, 2016-11-18 at 00:22 +0100, Sandro Boehme wrote:
Hi Julian,
I like the idea of individual Jenkins jobs for the reasons you
pointed out!
If we would have a "nightly" build (whatever time that would be) we
could link it at the Getting and building Sling page. We could write
there that in case the build does currently not work (e.g. because
there
is some bigger work in progress or a plain oversight) they could have
a
look at what revision actually does work and use that.
I've updated the building Sling docs to reflect how we expect things to
work now, see especially
http://sling.apache.org/documentation/development/getting-and-buildin
g-sling.html#tldr-short-form-build-run-instructions
http://sling.apache.org/documentation/development/getting-and-buildin
g-sling.html#with-the-maven-command-line-tool
Hopefully that makes more sense now.
It absolutely does!
I've just had cases where 'mvn clean install sling:install' of a
snapshot bundle to the normal launchpad seem to make problems with
resolving bundles. But if it should generally work it's all good.
Best,
Sandro
