Bommels05/maven-plugins
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
1,024 Commits 1 Branch 0 Tags
Commit Graph

4 Commits

Author SHA1 Message Date
jvanzyl
6801d9ed62 o RC1 Refactoring 
PR:
Obtained from:
Submitted by:
Reviewed by:


git-svn-id: https://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk@113732 13f79535-47bb-0310-9956-ffa450edef68
 2003-07-27 23:34:00 +00:00
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
bwalding
bd50b92f40 o Give the ability to set a Main-Class attribute in the manifest 
git-svn-id: https://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk@113192 13f79535-47bb-0310-9956-ffa450edef68
 2003-03-26 10:27:17 +00:00
jvanzyl
530c640d4f Initial revision 
git-svn-id: https://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk@112724 13f79535-47bb-0310-9956-ffa450edef68
 2003-01-24 03:44:26 +00:00