Thanks David. -- Samuel Bratton
-----David Bosschaert <[email protected]> wrote: ----- To: "[email protected]" <[email protected]> From: David Bosschaert <[email protected]> Date: 11/09/2015 10:47AM Subject: Re: Subsystem-itests pom.xml not updated after Subsystems release 2.0.6 Oh - I'm really sorry. For some reason they were local mods on my checkout. Sorry - I didn't spot that earlier. I've hopefully rectified this now. Cheers, David On 9 November 2015 at 16:21, Thomas Watson <[email protected]> wrote: > Looking at the file in SVN [1] I see old references to 2.0.5-SNAPSHOT for > both org.apache.aries.subsystem.api and org.apache.aries.subsystem.core > > Tom > > [1] > http://svn.apache.org/viewvc/aries/trunk/subsystem/subsystem-itests/pom.xml?view=markup > > > > > > From: David Bosschaert <[email protected]> > To: "[email protected]" <[email protected]> > Date: 11/09/2015 03:04 AM > Subject: Re: Subsystem-itests pom.xml not updated after Subsystems > release 2.0.6 > > > > Hi Sam, > > I looked at the itests pom and it points at 2.0.7-SNAPSHOT as > expected. Are you sure you're looking at the latest version? > > David > > On 6 November 2015 at 18:54, Samuel E Bratton <[email protected]> wrote: >> It looks like after the last subsystem 2.0.6 release the > subsystem/subsystem-itests/pom.xml was not updated to point to new maven > dependencies, >> org.apache.aries.subsystem.core:2.0.7-SNAPSHOT, > org.apache.aries.subsystem.api:2.0.7-SNAPSHOT (still pointing to > 2.0.5-SNAPSHOT). >> >> I think this also means the jenkins build results for subsystem are > suspect. >> >> Can we get these updated? >> >> Thanks >> >> -- >> Sam Bratton >> > > > >
