convention vs configuration---maven

Hi,

I was reading about Maven. Author says 'Maven uses convention over configuration'.

'Developers can build any given Maven project without need to understand how the individual plugins work. '
I have not understood clearly what it means. Is it not same with ANT builds as well.

please advise
Any links resources ideas highly appreciated. Thanks in advance
LVL 7
gudii9Asked:
Who is Participating?
 
mccarlIT Business Systems Analyst / Software DeveloperCommented:
convention over configuration
Basically just means that as far as possible, some sane default values have been chosen for plugin parameters. So for example, you don't need to tell the maven-compiler-plugin that your Java source files are in  "src/main/java". It is the default, and it is a well known default, so that you (or a tool) can just create those directories and place .java files within, and the build process will just work.

That is what the tag line is all about... "convention" ie. look in src/main/java, over "configuration" ie. rather than having to explicitly say that my source files are in src/main/java.

Note, that this doesn't mean that you can't configure the build process with different parameters, ie. you can put your source files elsewhere and configure the compiler to match.

The difference with Ant is that it's build file will explicitly state a lot (most) of the required parameters. Note though, that you probably don't see much of a difference if you are using some other tools on top of these, such as a modern IDE like Eclipse. It will hide a lot of the configuration, even for an Ant build.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.