On 5/9/07, Graham Leggett <[EMAIL PROTECTED]> wrote:
let's use the maven way - something you learn once, and apply everywhere.
"Learn once, apply everywhere", that reminds me something :)
Maybe our next marketing slogan, who knows.
Stéphane
Regards,
Graham
--
--
On Wed, May 9, 2007 12:30 pm, Siegfried Goeschl wrote:
> +) a related problem is that many companies hire juniors for this
> setting up and maintaining a build system - it is not real programming
> after all ... :-) ... later on the know better
I've seen over an over again how a lack of basic sof
Hi folks,
after setting up and maintaining complex build environments using ANT
and Maven for a couple of years I have some thought about the topic
+) "a fool with a tool is still a fool" - if a complex build system is
falling apart it has most of the times nothing to do with the underlying
tool
I agree with Graham's assessment that the bigger the project, the more
useful. However, it does come with a price. You've got to get used to the
idea of hard-versioning artifacts and moving toward controlled releases.
And a number of the plugins are pretty...interesting...to use.
I'm of the opi
I like to compare it to pure JDBC vs. Object relational tools.
With OR you lose control of the small details but overall you get a
better, simpler solution, worrying on the aspects you really care
about
On 5/8/07, Graham Leggett <[EMAIL PROTECTED]> wrote:
On Mon, May 7, 2007 6:24 pm, Peter Kahn
On Mon, May 7, 2007 6:24 pm, Peter Kahn wrote:
> How does maven's declarative convention over configuration stack up
> against scripted solutions like buildr, groovy/ant or scons when it
> comes to maintenance costs for large projects?
Scripted systems have an Achilles heel - build systems are no
Hello,
I have been using maven for several years now, and switch from custom
grown ant scripts to maven1.0 in 200? (can't recall exactly the
year). The reason we switched is the usual one:
- growing complexity and fragmentation of scripts
- uniformity and "industrialisation"
- standard way of b
I had worked before extensively with Ant, and I create a complete
end-to-end build system. When I started to work with Maven, I noticed
that I was able to version dependencies in a more organized manner, and
that I was able to establish a folder structure which all projects
shared. The site creat
How does maven's declarative convention over configuration stack up against
scripted solutions like buildr, groovy/ant or scons when it comes to
maintenance costs for large projects? Is there anyone out there who is
involved with a large complex project who can weigh in on how sustainable
maven h
