Awesome - we should give it a shot. If it makes things more congruent and less to maintain, I'm all for it.
On Fri, Jun 19, 2009 at 9:12 AM, Brett Porter <[email protected]> wrote: > > On 19/06/2009, at 10:54 PM, Niklas Gustavsson wrote: > > On Fri, Jun 19, 2009 at 3:54 AM, Brett Porter<[email protected]> wrote: >> >>> They were pushed up there from the Maven POM in version 6. If you upgrade >>> to >>> it, the other changes are that some plugin versions are locked down if >>> they >>> weren't otherwise specified already (this shouldn't negatively affect >>> your >>> build) , and the remote-resources plugin was added (if you have this in >>> your >>> build already, it might need to be removed). >>> >> >> Is there any documentation available on how to best make use of the >> Apache parent POM? Looking at it, I find many things that we've >> replicated in project POM, so switching the using the parent more >> would be a good idea. However, there are some properties and probably >> some things that must be overridden (like the SCM stuff) and having >> some guidelines would be great! >> >> > Up until now, it had been fairly self-explanatory, but there is a comment > in the top of the latest version to explain how to use the release profile. > The Maven development and release docs are the best reference for those > sections at the moment, as they apply equally to other projects using it. > You're right, the only thing that definitely needs to be overridden is the > SCM settings. > > - Brett > >
