maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Bentmann (JIRA)" <j...@codehaus.org>
Subject [jira] Closed: (MNG-4426) No javac errors in console when error stacktraces are turned on
Date Wed, 04 Nov 2009 12:53:55 GMT

     [ http://jira.codehaus.org/browse/MNG-4426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Benjamin Bentmann closed MNG-4426.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 3.0-alpha-3

Fixed in [r832729|http://svn.apache.org/viewvc?view=revision&revision=832729].

> No javac errors in console when error stacktraces are turned on
> ---------------------------------------------------------------
>
>                 Key: MNG-4426
>                 URL: http://jira.codehaus.org/browse/MNG-4426
>             Project: Maven 2
>          Issue Type: Improvement
>          Components: Errors
>    Affects Versions: 3.0-alpha-3
>         Environment: Apache Maven 3.0-SNAPSHOT (r831593; 2009-10-31 16:50:46-0500)
> Java version: 1.6.0_16
> Java home: d:\jdk1.6.0_16\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
>            Reporter: Paul Benedict
>            Assignee: Benjamin Bentmann
>             Fix For: 3.0-alpha-3
>
>         Attachments: MNG-4426.zip, MNG-4426.zip
>
>
> This only occurs when -e option is specified. When my build failure happened, this was
the output:
> [ERROR] [0]
> org.apache.maven.plugin.CompilationFailureException: Compilation failure
>        at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:516)
>        at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:114)
>        at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:105)
>        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:547)
>        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:317)
>        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:233)
>        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:102)
>        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:421)
>        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:156)
>        at org.apache.maven.cli.MavenCli.main(MavenCli.java:121)
>        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>        at java.lang.reflect.Method.invoke(Method.java:597)
>        at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>        at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>        at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>        at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> [ERROR]
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [0] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> Is this a feature or a bug? I thought it was the latter. Without the option, the compiling
errors are again printed.

-- 
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

        

Mime
View raw message