On 2 May 2014 14:40, Robbie Gemmell <[email protected]> wrote:
> As many of you are aware, we have been working on new Maven builds for the > Java components... > > Short version: > > I would like us to begin using the new Maven builds for the Java components > exclusively, removing the old build system from trunk and updating the > version in the 0.28 release to signal that it will be removed in 0.30. > > Agreed - now that the maven build does everything that the ant build does, I think we should take the plunge and move as soon as possible. Keeping two build systems up to date in parallel is an unnecessary overhead for everybody, and though I'm not the world's biggest fan of maven I think it's best we switch over and focus on a single build tool going forward. -- Rob > Additional detail: > > The Maven build is now able to do all of the core build and test > functionality the old build system does, plus some things it cant. While > there are no doubt still some finishing touches we can perform to improve > usability further, I think these would be best achieved through actual use > and evolution by everyone. > > I have been merging the changes from trunk such that the 0.28 release is > going to ship with a near-parity preview of the current trunk Maven build > for the main Java tree, simply requiring an explicit flag to enable it. I > am keen to avoid further overlap of having multiple builds systems. In > particular I think there is reduced need for such overlap as there was for > say for the C++ build systems in the past, because unlike that situation > the source code and its build process are typically not part of a users > primary interaction with the Java components; this will mainly only affect > the people developing Qpid. > > There are some instructions on using the new Maven build here: > https://cwiki.apache.org/confluence/display/qpid/qpid+java+build+how+to > > Robbie >
