(Moving this discussion to grammatica-users; please only reply on
I would prefer not having to analyse the build.xml just to get things
going. Yes, it's possible and it only takes a while but it's still a
waste of my time. With Maven everything is consistent and known. I
know where the code is and I know how to build it. No need to (yet
again) learn yet another way of how to build software. The same
applies to tools, Maven is a known entity so it's easy to work with.
Just think of a tool like Hudson.
Secondly, if we would like to add some tool to the build (code
coverage, static analysis, whatever) then in the Ant build you'd have
to learn this new tool *and* you'd have to figure out how to include
it in the build. With Maven you just include the plugin and you're
done. (I don't mean to imply that Maven is perfect but it sure beats
having to do the same thing time and again.)
I'd be happy to do the work and make sure there's also a build.xml for
Ant. In fact, Maven is able to generate a build.xml! :-) I don't think
you'd really notice if you didn't want to. The main "problem" is that
to really take advantage of Maven we'd have to comply with its
"Standard Directory Layout" (see
Again, I don't mind doing the work but I'd really need commit access
to move things around. (And I don't really expect you to do that
because right now I'm all talk and no action.) :-)
> Haven't used Maven myself, so I can't say much about it. But what
> problem would it solve for us? What would it make easier?
> I've opted for a plain Ant build file out of simplicity and low
> requirements. Most people are able to get that stuff to work without
> any issues. Don't think Maven is installed everywhere, so we'd have to
> keep the Ant build.xml anyway I guess...
> On Sun, Sep 20, 2009 at 04:14, Hilco Wijbenga <[hidden email]> wrote:
>> Hi all,
>> Is there any interest in/objection to moving to Maven? I already got
>> quite far (including the C# stuff). It would also be nice to have the
>> Grammatica JAR in Maven Central so that my Maven builds can use it
>> directly. Perhaps we could even create a Grammatica Maven plugin.
>> Grammatica-devel mailing list
>> [hidden email] >> http://lists.nongnu.org/mailman/listinfo/grammatica-devel >>
> Grammatica-devel mailing list
> [hidden email] > http://lists.nongnu.org/mailman/listinfo/grammatica-devel >