Martin Ritchie wrote:
2008/12/2 Rafael Schloming <[EMAIL PROTECTED]>:
Martin Ritchie wrote:
2008/12/2 Rafael Schloming <[EMAIL PROTECTED]>:
It's been noted in several different threads now that the maven poms
currently checked into SVN are out of date, don't work, and are confusing
people new to the project.
So far the only reason given for retaining them is the convenience of
being
able to use them to generate IDEA/Eclipse project files. IMHO it would be
preferable to simply check in a standard set of project files, and keep
any
mechanism used to build them outside of SVN.
I'd like to propose removing the pom files before the next RC. Please let
me
know if you have any objections.
--Rafael
Can we also remember to check in pom files for the client and common
modules so we can still publish our client library to a maven repo.
Something we haven't done yet but should be on our list of goals.
Was it not originally on our list of tasks for the new ant build system?
I'm confused. Is this an objection to removing the maven buildfiles?
--Rafael
Its not an objection if we have the ability to create poms for the
client/common modules from ant.
We probably don't even need to auto generate them as a first cut
though that of course would be way better so we don't have lot of
testing overhead at release time when we find the files have rotted.
I'll take a crack at auto generating them if someone can give me a
working example of what they're supposed to look like.
--Rafael
