On Dec 10, 2013 12:13 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote: > > In addition to the various "legal" issues with binaries in the repo, > we'd be masking the cause of this failure. In order to prevent further > deterioration of the build process, we need to figure out what went > wrong and fix it. > > EdB > > PS. Thanks for leaving the keyboard on the Mustella VM set to FR... > Took me while to figure out that I hadn't gone insane or if my > keyboard was broken ;-)
Oh, that's what it was. I spent a whole session copy pasting commands from my computer on to the VM :-) > > > > On Tue, Dec 10, 2013 at 9:04 AM, Maurice Amsellem > <maurice.amsel...@systar.com> wrote: > >> someone who does use the pbj's will grab the nightly and complain. > > > > I don't understand. > > Why would someone complain if the pbj's are in the nightly? > > > > [From the other emai] > >>Apache repos aren't supposed to contain compiled code. The pbj files were removed during the initial release audit. > >>I don't think a workaround can involve checking in the pbj files. But we could borrow them from a prior release package temporarily. > > > >>So we could make the compilation conditional on a env parameter, and > >>set that in the Jenkins job accordingly? > >>Yes but ... > > > > Alex, the conversation is getting out synch, so I am not sure that I have understood what you said. > > > > So can we include the pbj in the repo, and have a parameter to conditionally compile the pbj ? > > - This parameter would be set by default to do the compilation (so that folks can recompile) > > - and turned off on the b.a.o vm, with pre-compiled pbj's. > > > > > > Maurice > > > > > > -- > Ix Multimedia Software > > Jan Luykenstraat 27 > 3521 VB Utrecht > > T. 06-51952295 > I. www.ixsoftware.nl
