Emmanuel Bourg schrieb:
[EMAIL PROTECTED] wrote:
Modified: jakarta/commons/proper/configuration/trunk/project.properties
URL:
http://svn.apache.org/viewcvs/jakarta/commons/proper/configuration/trunk/project.properties?rev=354834&r1=354833&r2=354834&view=diff
==============================================================================
--- jakarta/commons/proper/configuration/trunk/project.properties
(original)
+++ jakarta/commons/proper/configuration/trunk/project.properties Wed
Dec 7 11:30:00 2005
@@ -34,7 +34,9 @@
maven.jar.override=on
maven.jar.resources=conf/resources.jar
+maven.dist.src.assembly.dir=${maven.dist.assembly.dir}/src/${maven.final.name}-src
+
maven.compile.target = 1.3
-maven.compile.source = 1.3
+maven.compile.fork = true
Was the removal of 'maven.compile.source' necessary to compile with the
JDK 1.3 ? Without this property the project can't be compiled with Java
5, I get the following error :
java:compile:
[echo] Compiling to F:\dev\configuration/target/classes
[javac] Compiling 53 source files to F:\dev\configuration\target\classes
[javac] javac: target release 1.3 conflicts with default source release 1.5
That would be nice to find a trick working for all JDKs (after the 1.2
release).
Emmanuel Bourg
Yes, unfortunately this was necessary. If the maven.compile.source
property is provided, maven passes the source switch to the compiler,
which is not understood by javac in JDK 1.3.
Maybe we could remove the maven.compile.target property, too, and update
the building documentation that these properties could be defined in a
local build.properties if somebody has special needs?
Oliver
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
