I agree this probably does not address any burning issues or problems
but I do believe Maven is a good tool which can make build- and
release-related chores easier.
It would also help people like me who use Roller not so much as an
end-user product but as a framework to deliver Blogging solutions to
my clients. When a new version of Roller is released I could simply
diff project.xml (Maven configuration XML file) to see if any
dependencies were upgraded or added (or any other significant changes
occurred).
Max
On Sep 13, 2005, at 8:34 PM, Matt Raible wrote:
I don't see a problem with it - but if it ain't broke - why fix
it? ;-)
Matt
On 9/13/05, Rudman Max <[EMAIL PROTECTED]> wrote:
How do people feel about "Mavenizing" Roller? For those who are not
familiar with it, Maven is "a software project management and
comprehension tool". It's is somewhat similar to Ant, in fact it uses
Ant goals under the hood (though upcoming Maven2 does not), but it
also keeps metadata about the project which allows it to be much more
intelligent.
The difference between Ant and Maven is like that between a
procedural and a declarative language. Instead of telling Ant what
to do in order to build, you tell Maven what you want done and it
figures out what needs to be done based on the XML configuration
file. Maven automatically tracks and downloads dependencies for you,
versions the artifact, produces documentation website with JavaDocs
and unit-test coverage reports.
I've "mavenized" Roller 1.x branch and would be happy to contribute
that to the project. Let me know if there is any interest in that.
You can learn more about Maven at http://maven.apache.org
Max
