2.1
Won't work every time.
We have a corporate pom, it's pretty much stable and it won't change often. All
our projects inherit from that one, it will be a pain to update everything
every time we would want to upgrade some plug-ins.
Stéphane
On 4/12/07, Hayes, Peter <[EMAIL PROT
I'd like to give my 2 cents on this issue.
Would it be possible to maintain a super POM on repo1 that contains a
vetted set of plugin versions and then version that POM appropriately
based on new releases of core plugins? Then it would simply be an
inclusion of a specific parent version in a proj
