jstrachan 98525aa613 Defaulted the compile target to 1.1. If a build is done on JDK 1.4 then it defaults to JDK 1.4, which means on some JVM's (e.g. IBM's JDK 1.3) the code won't work! Even if you're not using any JDK 1.4 features. The generated bytecode can contain some JDK 1.4 specific methods! ...

So as a safety measure, I've defaulted the target to 1.1 by default (which is the default setting for JDK 1.1, 1.2 and 1.3 anyway). 

You can still overload this value on a project by project basis - this just prevents this possible bug hitting Maven users.


git-svn-id: https://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk@113388 13f79535-47bb-0310-9956-ffa450edef68

2003-04-26 09:56:23 +00:00

..

xdocs

Defaulted the compile target to 1.1. If a build is done on JDK 1.4 then it defaults to JDK 1.4, which means on some JVM's (e.g. IBM's JDK 1.3) the code won't work! Even if you're not using any JDK 1.4 features. The generated bytecode can contain some JDK 1.4 specific methods!

2003-04-26 09:56:23 +00:00

.cvsignore

Initial revision

2003-01-24 03:44:26 +00:00

plugin.jelly

Defaulted the compile target to 1.1. If a build is done on JDK 1.4 then it defaults to JDK 1.4, which means on some JVM's (e.g. IBM's JDK 1.3) the code won't work! Even if you're not using any JDK 1.4 features. The generated bytecode can contain some JDK 1.4 specific methods!

2003-04-26 09:56:23 +00:00

plugin.properties

Defaulted the compile target to 1.1. If a build is done on JDK 1.4 then it defaults to JDK 1.4, which means on some JVM's (e.g. IBM's JDK 1.3) the code won't work! Even if you're not using any JDK 1.4 features. The generated bytecode can contain some JDK 1.4 specific methods!

2003-04-26 09:56:23 +00:00

project.properties

Added license property

2003-02-10 08:26:57 +00:00

project.xml

o Resolving all snapshots in plugins

2003-04-09 01:06:49 +00:00