Umm, I would say the main priority is that Joseph creates the pom such
that proton builds via "mvn clean install" OOTB (as any good Maven
project should.) As long as he's met that threshold, I don't see a need
anymore for maintaining two sources of records for builds.
Maven is really mind-numbingly simple for those building with it. No
matter what you're building, it's always "mvn clean install" (so long as
the pom is properly written, as it nearly always is). All you need to
do is download Maven, add $MAVEN_HOME/bin to your system path (just like
you do for Ant) and you're all set.
The problem with providing an Ant build is that non-Maven users, never
having worked with it, tend to awfulize Maven, and then stick with Ant,
continuing their misconception of Maven. Maven is really an ice cream
cone, not a brussels sprout, but sometimes people need to be given a
push to find that out. :) Also, burdening Joseph by having him
create/maintain a separate Ant build also takes away his efforts towards
creating an awesome Maven build.
Glen
>Hi,
>It looks for me that the structure of proton-j sub-project will be
>quite simple and will not require the creation of complicated building
>scripts similar to what we have in qpid java tree right now. I believe
>that we can have 2 building systems for proton-j at least on first
>stages of the project. That would allow developers to use either ant
>or maven depending from their preferences.
>IMHO, it should not be big overhead for the project.
>
>Kind Regards,
>Alex
--
Glen Mazza
Talend Community Coders
coders.talend.com
blog: www.jroller.com/gmazza
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
