On Wed, 2017-10-11 at 16:04 +0200, Karl Pauls wrote: > On Wed, Oct 11, 2017 at 3:46 PM, Ian Boston <[email protected]> wrote: > > Hi, > > > > On 11 October 2017 at 11:21, Robert Munteanu <[email protected]> > > wrote: > > > > > Hi Ian, > > > > > > On Wed, 2017-10-11 at 10:47 +0100, Ian Boston wrote: > > > > Hi, > > > > Could be me. > > > > I do mvn clean install on a clean Sling checkout with a clean > > > > maven > > > > repo > > > > and I get failiures to download slingfeature:9-SNAPSHOT > > > > required by > > > > an IT > > > > test sample. This happens before the reactor starts. > > > > > > Fixed in http://svn.apache.org/viewvc?rev=1811803&view=revev . > > > > > > > > > > > If I fix that by using slingfeature:9 I then get 11 test > > > > failures in > > > > commons.log related to the format of the logging output. > > > > > > > > Is this just me ? > > > > > > > > If it is just me, I can disable tests there to move on. > > > > > > I am not sure anyone is building the full reactor anymore > > > > > > > > Isnt that a bit dangerous ? > > Not being able to reliably build Sling could allow a failure to go > > for > > months without being noticed using old snapshot builds from other > > modules. > > > > I assume no one is building all of Sling because it takes too long > > now ? > > > Carsten and I did sit down semi-regularly and got it back building. > Not sure when we did that last but it can't be more than a month or > two. > > I agree that this is not a good state to be in. > > regards, > > Karl
Would it help if we added weekly builds for all modules, irrespective if any changes are present? Robert
