Hi, sure having binary releases of the launchers would be great.
My main concern of not doing this so far was, that it requires to create the required LICENSE and NOTICE files for such a release. That means that we have to check every single artifact that we include in the binary release and add the required information to LICENSE and NOTICE. Since we were only doing source releases so far, there was no need for this because in a source release the dependencies are not included and only referenced. This is different in a binary release where we ship everything in one package. So be prepared for this extra work. Best, - Fabian 2013/10/21 Rupert Westenthaler <rupert.westentha...@gmail.com>: > Hi all, > > I was considering to create Stanbol launchers without data bundles in > the release branch. This would allow us to do a binary release. > > We could create launchers for > > * stateless (Enhancer & Entityhub) > * semindexing (Stateless & Contenthub & CMS Adapter) > * reasoning (Ontologymanager & Rules & Reasoning) > * full (all stanbol modules) > > In addition we could include the Entityhub indexing tools as binary releases. > > WDYT > Rupert > > On Mon, Oct 21, 2013 at 1:12 PM, Reto Bachmann-Gmür <r...@wymiwyg.com> wrote: >> Hi Fabian >> >> As we might need to build more release candidates I suggest to do this in >> the release branch. For the release plugin to work it will afaik be >> necessary to adapt the svn url in the pom >> >> Cheers, >> Reto >> >> >> On Sat, Oct 19, 2013 at 1:39 PM, Fabian Christ <christ.fab...@googlemail.com >>> wrote: >> >>> Hi, >>> >>> good to hear about the progress ;) >>> >>> I am currently checking that the trunk is fine when trying to build >>> with the apache-release profile (this includes the RAT check). Once >>> this succeeds we could create the release branch. >>> >>> Best, >>> - Fabian >>> >>> 2013/10/19 Andreas Kuckartz <a.kucka...@ping.de>: >>> > Rupert Westenthaler: >>> >> However there is still no progress on the build issues of Andreas. As >>> >> explained in [4] I can see in the log what is going wrong, but I have >>> >> still no idea why this is happening in Andreas environment. All my >>> >> tries to reproduce this where not successful. >>> > >>> > I have executed and am executing more experiments with the integration >>> > tests and will report today or tomorrow. I think that I observed >>> > something during the start of the launcher which might or might not have >>> > something to do with the issues. >>> > >>> > A good thing is that I have no problem reproducing the issues ;-) >>> > >>> >> Still I would suggest to close the trunk for new things ASAP. Release >>> >> related bug fixes can still be done during the release preparation and >>> >> while checking/voting for the release candidates. >>> > >>> > +1 >>> > >>> > Cheers, >>> > Andreas >>> >>> >>> >>> -- >>> Fabian >>> http://twitter.com/fctwitt >>> > > > > -- > | Rupert Westenthaler rupert.westentha...@gmail.com > | Bodenlehenstraße 11 ++43-699-11108907 > | A-5500 Bischofshofen -- Fabian http://twitter.com/fctwitt
