May I ask why? It seemed like a very natural fit to me. A tool like clirr seemed as it were built to help enforce version standards. Why not have it be explicit?
Rex On Sun, Jul 11, 2010 at 3:03 AM, Evgeny Mandrikov <[email protected]>wrote: > Hi Rex, > > First of all - thanks for your contribution. But I'm not sure about > MCLIRR-33 - I think that clirr plugin should not be used for such > tasks. > > On Sun, Jul 11, 2010 at 8:14 AM, Rex Hoffman <[email protected]> wrote: > > First up, Thanks all for great maven plugins!!! > > So just lobbed 3 jiras against the clirr mojo, all with patches of > course. > > http://jira.codehaus.org/browse/MCLIRR-31 > > http://jira.codehaus.org/browse/MCLIRR-32 > > http://jira.codehaus.org/browse/MCLIRR-33 > > Site documentation fully updated. > > 33's patch unfortunately contains the contents of 32's as well. > > Did my best to minimize any potential side-effects. Gave the code it's > > first test (not a very impressive one). > > I'd also like to write a plugin that takes the version number convergence > > checks that are done in by the dependency analysis report and enforce > them > > at build time. > > If you'd be willing to host it here, I'd be appreciative. > > Rex Hoffman > > > > -- > Best regards, > Evgeny Mandrikov aka Godin <http://godin.net.ru> > http://twitter.com/_godin_ > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
