For the record, I'm not proposing to move to Maven. I just want to
make sure that those who want to use it are happy. As far as I am
concerned, the Ant build is the authoritative build until we all
decide we don't want it to be.
On Aug 5, 2008, at 9:05 AM, Sean Owen wrote:
Cool, I have some build targets that are a bit trickier, but, could
simply retain them in an auxilliary Ant build file as needed.
I think the core of my build is already in the main build.xml file. So
if we're porting to Maven, erm, would someone who knows it well care
to step up and do it? then I can rationalize what remains of my build
file versus the Maven file and take whatever steps I need to to finish
my part.
I am open to Maven but neutral on it versus Ant. I'll go with the
consensus.
On Tue, Aug 5, 2008 at 1:41 AM, Ted Dunning <[EMAIL PROTECTED]>
wrote:
I have had the chance to use a maven centric build just lately from
the
IntelliJ point of view and found it painless to keep the pom as the
master
structure. IntelliJ can even sync back to the pom.
I don't think that using ant from maven would be as useful as
switching over
entirely to maven.
On Mon, Aug 4, 2008 at 9:11 PM, Karl Wettin <[EMAIL PROTECTED]>
wrote:
I've managed to keep the POMs in sync locally at least up until a
month
ago. Hopefully it's not too much of a hassle to update them. It
was mostly
trouble with nested deps that needed to be excluded. Also, core/
src/examples
needs to be moved to a new maven module in order to work and that
will
require touching the ant build.
Sorry for my recent inactivity and short communication the last
weeks! Been
busy catching the sun, changing country and moving to a new
apartment. Have
a whole bunch of halfbaked patches and comments here. Please allow
a few
days for me to sync with trunk and catch up with discussions on
the fora.
karl
5 aug 2008 kl. 04.06 skrev Sean Owen:
That's nice -- how about targets that need more customized
scripting?
I suppose we can keep those separate, and connect them to the
auto-generated build file. At least then build logic is not
duplicated. Sounds good?
On Mon, Aug 4, 2008 at 9:56 PM, pi song <[EMAIL PROTECTED]> wrote:
You can generate ant build file/intelliJ project file/Eclipse
project
file
from Maven poms. One way is to too keep maven as your master so
you don't
have to maintain both.
On Tue, Aug 5, 2008 at 11:32 AM, Sean Owen <[EMAIL PROTECTED]>
wrote:
I don't know, I have not found a great solution for this. I
don't use
Maven myself but am not against learning how to use it
effectively.
Part of that is sorting out how to keep it in sync with Ant build
scripts. We could delegate all building to Ant. Perhaps that's
the
easiest way.
Anyone know enough about Maven to understand best practices? I
assume
some does or else we wouldn't be bothering with it.
On Mon, Aug 4, 2008 at 8:47 PM, Grant Ingersoll <[EMAIL PROTECTED]
>
wrote:
So, what's are plan for the Maven poms? How do we intend to
keep them
in
sync such that they are actually useful for those who want to
use Maven
(not
me, but others...)?
-Grant
--
ted
