|
»
Created: (MNG-4426) No javac errors in console when error stacktraces are turned on
|
View:
New views
7 Messages
—
Rating Filter:
Alert me
|
 |
Created: (MNG-4426) No javac errors in console when error stacktraces are turned on
by JIRA jira@codehaus.org
::
Rate this Message:
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 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 |
|
|
Updated: (MNG-4426) No javac errors in console when error stacktraces are turned on
by JIRA jira@codehaus.org
::
Rate this Message:
[ http://jira.codehaus.org/browse/MNG-4426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann updated MNG-4426: ----------------------------------- Attachment: MNG-4426.zip I couldn't reproduce this, the attached demo project outputs {noformat} [ERROR] [0] org.apache.maven.plugin.CompilationFailureException: Compilation failure M:\MNG-4426\src\main\java\Main.java:[3,20] ';' expected at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:516) {noformat} upon "mvn compile". > 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 > Attachments: 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 |
|
|
Closed: (MNG-4426) No javac errors in console when error stacktraces are turned on
by JIRA jira@codehaus.org
::
Rate this Message:
[ http://jira.codehaus.org/browse/MNG-4426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-4426. ---------------------------------- Resolution: Cannot Reproduce Assignee: Benjamin Bentmann Feel free to re-open with an updated test project that exhibits your issue. > 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 > Attachments: 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 |
|
|
Reopened: (MNG-4426) No javac errors in console when error stacktraces are turned on
by JIRA jira@codehaus.org
::
Rate this Message:
[ http://jira.codehaus.org/browse/MNG-4426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Benedict reopened MNG-4426: -------------------------------- Re-opening with reproducible test case. > 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 > Attachments: 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 |
|
|
Updated: (MNG-4426) No javac errors in console when error stacktraces are turned on
by JIRA jira@codehaus.org
::
Rate this Message:
[ http://jira.codehaus.org/browse/MNG-4426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Benedict updated MNG-4426: ------------------------------- Attachment: MNG-4426.zip Benjamin, I used your test case and couldn't reproduce my problem -- every compiler error was caught. So I went back and reproduced my original problem as I discovered in my real projects. I was missing a dependency at compile-time although my file was syntactically valid. > 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 > 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 |
|
|
Closed: (MNG-4426) No javac errors in console when error stacktraces are turned on
by JIRA jira@codehaus.org
::
Rate this Message:
[ 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 |
|
|
Updated: (MNG-4426) Some javac errors not shown in console when error stacktraces are turned on
by JIRA jira@codehaus.org
::
Rate this Message:
[ http://jira.codehaus.org/browse/MNG-4426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Benedict updated MNG-4426: ------------------------------- Issue Type: Bug (was: Improvement) Summary: Some javac errors not shown in console when error stacktraces are turned on (was: No javac errors in console when error stacktraces are turned on) > Some javac errors not shown in console when error stacktraces are turned on > --------------------------------------------------------------------------- > > Key: MNG-4426 > URL: http://jira.codehaus.org/browse/MNG-4426 > Project: Maven 2 > Issue Type: Bug > 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 |
| Free embeddable forum powered by Nabble | Forum Help |
