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=rev . > > > > > 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 ? > - we are > building individual modules on Jenkins [1]. > > commons.log builds fine for me as an individual module and I don't see > it failing on Jenkins either. > > If there's a consistent failure at your end, please file a bug. Both commons log and commons log webconsole fail performing PaxExam ITs, reliably. Normal Unit tests are Ok. JDK 1.8.0 Maven 3.5.0 I have disabled tests in those bundles to move on, assuming its something strange about my box. Best Regards Ian > But for > getting the launchpad up and running only need to build > launchpad/builder/ - all depenendencies are releases therefore the > reactor build is not used. > > Thanks, > > Robert > > > [1]: https://builds.apache.org/view/S-Z/view/Sling/ >
