Loading Profile...
CHAMP
Criticism of Ant in Section 1.2 not accurate
On page 2, section 1.2, second paragraph, you write:
While this might seem
trivial, consider the fact that most Ant-based builds have to define the locations of
these directories in every subproject.
I don't think anyone with experience with Ant 1.6 or greater would design a build this way. Most organizations define a common source code layout, all common build tasks are placed in a master build file that defines these locations in a master property file.
The build files for individual projects typically contain little more than an import of the master build file. And of course the local build file can utilize a local property file before the import to override any values in the master property file.
I'm not saying ant is better than maven. Just suggesting that your criticism of ant isn't really accurate.
While this might seem
trivial, consider the fact that most Ant-based builds have to define the locations of
these directories in every subproject.
I don't think anyone with experience with Ant 1.6 or greater would design a build this way. Most organizations define a common source code layout, all common build tasks are placed in a master build file that defines these locations in a master property file.
The build files for individual projects typically contain little more than an import of the master build file. And of course the local build file can utilize a local property file before the import to override any values in the master property file.
I'm not saying ant is better than maven. Just suggesting that your criticism of ant isn't really accurate.
1
person likes this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
The company implemented this idea.
-
Inappropriate?Right, I see where you are coming from, and I acknowledge that the statement (as written) is a bit confusing. What I'm really trying to say is that Ant doesn't ship with any assumptions or conventions and that the main difference between Ant and Maven is that one has to supply explicit directory locations to Ant where the same build in Maven could just follow convention.
I've updated the section to read:
While this might seem
trivial, consider the fact that most Ant-based builds have to
define the locations of these directories. Ant doesn't ship with
any built-in idea of where source code or resources might be in a
project; you have to supply this information.
I’m thankful
EMPLOYEE
