So what is the enforcer needed for?
On 18 July 2013 00:15, Jeff MAURY <jeffma...@jeffmaury.com> wrote: > What are you refering to ? The enforcer rule ? > The problem you mentioned about 1.8 should be managed by the animal sniffer > plugin > > Jeff > > > On Thu, Jul 18, 2013 at 1:12 AM, sebb <seb...@gmail.com> wrote: > >> On 18 July 2013 00:10, Emmanuel Lécharny <elecha...@gmail.com> wrote: >> > Le 7/18/13 12:42 AM, sebb a écrit : >> >> On 17 July 2013 23:21, Jeff MAURY <jeffma...@jeffmaury.com> wrote: >> >>> Build also except if the benchmarks profile is activated: build fails >> >>> because it seems the benchmarks pom is still on 3.0.0-M1-SNAPSHOT >> >> Both of these files still refer to the SNAPSHOT release: >> >> >> >> benchmarks/pom.xml >> >> benchmarks2/pom.xml >> >> >> >> Looks like the release plugin did not work properly, or the poms are >> >> not configured correctly. >> > >> > No, as I said, this is my mistake : those poms are belonging to modules >> > taht are activated by a profile, and I forgot to use it. >> >> Is it possible to auto-activate it when using the release plugin? >> >> > >> > -- >> > Regards, >> > Cordialement, >> > Emmanuel Lécharny >> > www.iktek.com >> > >> > > > > -- > Jeff MAURY > > > "Legacy code" often differs from its suggested alternative by actually > working and scaling. > - Bjarne Stroustrup > > http://www.jeffmaury.com > http://riadiscuss.jeffmaury.com > http://www.twitter.com/jeffmaury
