Bump, and adding suggested diff for including a notice in the existing
build such that we could put it in 0.28 to indicate the transition. This
would print out the message at the end of the build and test targets when
run from the java directory.
Robbie
diff --git qpid/java/build.xml qpid/java/build.xml
index 97ae967..567de04 100644
--- qpid/java/build.xml
+++ qpid/java/build.xml
@@ -104,6 +104,16 @@
<available file="${build.failed}"/>
</condition>
+ <echo>
+ ----------------------- NOTE ---------------------------
+ The Java components are transitioning to using a Maven based
+ build process, this build process will be removed in the 0.30
+ release. A preview of the new Maven build is available
+ alongside this one, simply requiring -Denable=true be specified
+ in any Maven commands used.
+ ---------------------------------------------------------------
+ </echo>
+
<fail if="failed" message="TEST SUITE FAILED"/>
</target>
@@ -172,6 +182,15 @@
<target name="build" depends="retrieve-dependencies" description="build
the project">
<iterate target="build"/>
<antcall target="manifest"/>
+ <echo>
+ ----------------------- NOTE ---------------------------
+ The Java components are transitioning to using a Maven based
+ build process, this build process will be removed in the 0.30
+ release. A preview of the new Maven build is available
+ alongside this one, simply requiring -Denable=true be specified
+ in any Maven commands used.
+ ---------------------------------------------------------------
+ </echo>
</target>
<target name="prepare">
On 2 May 2014 13: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.
>
> 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
>
