This, I contend, is one of Maven's biggest problems. Publishing snapshots is so easy that many projects rely on it instead of pushing out regular releases. And when the only way to get your particular bug fixed is using snapshots, your hands are rather bound.
The TestNG situation was so bad that I re-migrated one of our largest projects back to ant using the maven ant task. At times I miss some of the maven features, but having the capability of completing my work is a nice bonus. -- Kevin On 12/14/07 11:55 AM, in article [EMAIL PROTECTED], "Christian Edward Gruber" <[EMAIL PROTECTED]> wrote: > If you're going to do that, can you please still deploy into a maven > repository. Nearly every organization I work in, and almost all > projects outside of that use Maven, so losing Tapestry as a maven > artifact will be a big fat hairy batch of frustration. > > On a side note, why are you using the surefire 2.4-snapshot, and then > getting upset when the behaviour is different? It's a snapshot. Use > released code if you need consistent behaviour. Just lock it in with > dependencyManagement. > > Christian. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
