On Tue, Jan 5, 2010 at 6:40 PM, ant elder <ant.el...@gmail.com> wrote: > On Tue, Jan 5, 2010 at 2:02 PM, ant elder <ant.el...@gmail.com> wrote: >> On Tue, Jan 5, 2010 at 11:21 AM, Simon Laws <simonsl...@googlemail.com> >> wrote: >>> Ok, have made the fix and got a clean build so will check in. Ant has >>> mentioned that there is some maven magic that will tell us when we >>> have unversioned dependencies (which is what caused this issue). So am >>> hoping he'll post on the details. >>> >>> Simon >>> >> >> That would be the Maven Enforcer plugin and its requirePluginVersions >> option - >> http://maven.apache.org/enforcer/enforcer-rules/requirePluginVersions.html. >> I'll have a go getting that running in our build. >> >> ...ant >> > > I know this thread is about 1.x but as a start i've updated the 2.x > build to use the enforcer plugin to verify only released plugin > versions are used. The current build is running ok for me with this > and I've just kicked off a hudson build to check thats working ok, let > me know if anyone sees any problems. If it looks ok we can try the > same for the 1.x build. > > ...ant >
This appears to be working ok so i guess it should be fine to try on 1.x now. ...ant
