maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Grzegorz Borkowski (JIRA)" <>
Subject [jira] Created: (MCOMPILER-84) Simplify java version configuration by using project-level property
Date Sun, 09 Nov 2008 13:03:13 GMT
Simplify java version configuration by using project-level property

                 Key: MCOMPILER-84
             Project: Maven 2.x Compiler Plugin
          Issue Type: Improvement
            Reporter: Grzegorz Borkowski

I hate the fact that in each project I have to redefine the java source level for maven compiler,
from 1.3 to 1.5. Using 1.3 as default in this  day and age simply doesn't make sense. I reported
issue MCOMPILER-80 about it already. 
In the meantime, I have some more backword-compatible proposition: change maven compiler to
check for some project-level property, if this property is set, it is used for java source
and target level.
We nee to decide on property name, it can be called "java.version" or similar ("javaVersion"
When it is implemented, specifying java version would be much simplified:
Instead of:


We would have:


Much simpler and easier to remember!

BTW. I believe that java version level is really a part of project metadata, not simply some
plugin metadata. So in best case it should be made a part of POM definition, just like <artifactId>,
<version>, <name>, <packaging> itp. But it requires new XML schema for pom.xml,
so it is candidate for next version of maven. Using property doesn't require any change to
XML schema, so it may be implemented without waiting for new version of maven.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message