[ http://jira.codehaus.org/browse/MNG-345?page=comments#action_40308 ]
     
Brett Porter commented on MNG-345:
----------------------------------

ah, yes. Maybe ErrorDiagnoser. Here is what I get, but would prefer a BUILD 
FAILURE:

[INFO] 
----------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] 
----------------------------------------------------------------------------
[ERROR] Cause:
org.apache.maven.plugin.MojoExecutionException: Error configuring plugin for 
execution of 'jar:jar'.
        at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:430)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.processGoals(DefaultLifecycleExecutor.java:169)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:90)
        at org.apache.maven.DefaultMaven.processProject(DefaultMaven.java:253)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:167)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:246)
        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:585)
        at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:303)
        at org.codehaus.classworlds.Launcher.launch(Launcher.java:243)
        at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:416)
        at org.codehaus.classworlds.Launcher.main(Launcher.java:363)
Caused by: org.apache.maven.plugin.PluginConfigurationException: Unable to 
parse the created DOM for plugin configuratio
n
        at 
org.apache.maven.plugin.DefaultPluginManager.populatePluginFields(DefaultPluginManager.java:553)
        at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:400)
        ... 13 more
Caused by: 
org.codehaus.plexus.component.configurator.ComponentConfigurationException: 
Class 'org.apache.maven.plugin.ja
r.JarMojo' does not contain a field named 'addClasspath'
        at 
org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.getFieldByName(Obje
ctWithFieldsConverter.java:176)
        at 
org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.processConfiguratio
n(ObjectWithFieldsConverter.java:112)
        at 
org.codehaus.plexus.component.configurator.BasicComponentConfigurator.configureComponent(BasicComponentConfig
urator.java:54)
        at 
org.apache.maven.plugin.DefaultPluginManager.populatePluginFields(DefaultPluginManager.java:548)
        ... 14 more


> bad plugin configuration errors out
> -----------------------------------
>
>          Key: MNG-345
>          URL: http://jira.codehaus.org/browse/MNG-345
>      Project: Maven 2
>         Type: Sub-task
>   Components: maven-core
>     Versions: 2.0-alpha-1
>     Reporter: Brett Porter
>     Assignee: John Casey
>      Fix For: 2.0-alpha-3

>
>
> you get a trace from component composition if you mis type a configuration, 
> instead of a helpful error.
> eg, for jar Plugin:
> <configuration>
>   <addClassPath>true<addClasspath>
> </configuration>

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


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to