[
http://jira.codehaus.org/browse/MCOMPILER-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=242303#action_242303
]
Stephen Bannasch commented on MCOMPILER-114:
--------------------------------------------
The forensics on the maven-generated version of the class files above was
generated with v2.0.2 of the compiler plugin.
In that example (where there was a partial reduction in compiled class size) I
was passing in the debug=false parameter on the command line:
{noformat}
$ mvn clean; mvn -Dmaven.compiler.debug=true
{noformat}
I just tried with v2.3.2 of the compiler plugin and running the same command
from a shell now produces compiled code with *all* the additional debug
resources.
Setting {{<compilerArgument>-g:none</compilerArgument>}} still results in
compilation without adding debug resources when using v2.3.2 of the compiler
plugin
> Setting the debug option to false still compiles the code with line numbers
> resulting in increased class file.
> --------------------------------------------------------------------------------------------------------------
>
> Key: MCOMPILER-114
> URL: http://jira.codehaus.org/browse/MCOMPILER-114
> Project: Maven 2.x Compiler Plugin
> Issue Type: Bug
> Affects Versions: 2.1
> Environment: Windows XP Professional Version 5.1.2600 Service Pack 3
> Build 2600, Dell OptiPlex GX280, Total Physical Memory 4,096.00 MB
> Reporter: Grzegorz Solecki
> Attachments: TestApp.zip
>
>
> Given the following example:
> {code:title=Bar.java|borderStyle=solid}
> public class Main {
> public static void main(String[] args) {
> for (StackTraceElement stackTraceElement :
> Thread.currentThread().getStackTrace())
> System.out.println(stackTraceElement);
> }
> }
> {code}
> and pom.xml
> {code:xml}
> <project xmlns="http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
> <modelVersion>4.0.0</modelVersion>
> <groupId>com.greg</groupId>
> <artifactId>TestApp</artifactId>
> <version>1</version>
> <build>
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-compiler-plugin</artifactId>
> <configuration>
> <debug>none</debug>
> <source>1.5</source>
> <target>1.5</target>
> </configuration>
> </plugin>
> </plugins>
> </build>
> </project>
> {code}
> after compiling and running we get:
> {panel:title=cmd}
> {noformat}
> {TestApp}\target\classes>dir Main.class
> 05/02/2010 XX:XX 564 Main.class
> {TestApp}\target\classes>java -cp . Main
> java.lang.Thread.dumpThreads(Native Method)
> java.lang.Thread.getStackTrace(Thread.java:1383)
> Main.main(Main.java:3)
> {noformat}
> {panel}
> *NOTE !!!: the number of line (Main.java:3) has been shown*
> However when you compile the same java code using the javac we get:
> {panel:title=cmd}
> {noformat}
> {TestApp}\src\main\java>javac -g:none -source 1.5 -target 1.5 Main.java
> {TestApp}\src\main\java>dir Main.class
> 05/02/2010 XX:XX 477 Main.class
> {TestApp}\src\main\java>java -cp . Main
> java.lang.Thread.dumpThreads(Native Method)
> java.lang.Thread.getStackTrace(Thread.java:1383)
> Main.main(Unknown Source){noformat}
> {panel}
> *NOTE !!!: the number of line has not been shown*
> Please find the whole sample project in Eclipse that uses m2eclipse plugin,
> that is configured for using external maven 2.2.1
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
