AFAIK, we don't use groovy maven plugin.
In which module does this happen ?

On Nov 30, 2007 10:20 PM, Eduardo Burgos <[EMAIL PROTECTED]> wrote:

> And here is a stack trace if needed.
>
>
> Cause: When configuring a basic element the configuration cannot contain
> any
> child elements. Configuration element 'source'.
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Error configuring:
> org.codehaus.mojo:groovy-maven-plugin. Reason: Unable to parse the created
> DOM for plugin configuration
>        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
> (
> DefaultLifecycleExecutor.java:568)
>        at
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle
> (DefaultLifecycleExecutor.java:480)
>        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
> DefaultLifecycleExecutor.java:459)
>        at
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
> (DefaultLifecycleExecutor.java:311)
>        at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
> DefaultLifecycleExecutor.java:278)
>        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
> DefaultLifecycleExecutor.java:143)
>        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
>        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
>        at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
>        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
> :315)
>        at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>        at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java
> :430)
>        at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.PluginConfigurationException: Error
> configuring: org.codehaus.mojo:groovy-maven-plugin. Reason: Unable to
> parse
> the created DOM for plugin configuration
>        at
> org.apache.maven.plugin.DefaultPluginManager.populatePluginFields
> (DefaultPluginManager.java:1157)
>        at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(
> DefaultPluginManager.java:618)
>        at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
> DefaultPluginManager.java:425)
>        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
> (
> DefaultLifecycleExecutor.java:539)
>        ... 16 more
> Caused by:
> org.codehaus.plexus.component.configurator.ComponentConfigurationException
> :
> When configuring a basic element the configuration cannot contain any
> child
> elements. Configuration element 'source'.
>        at
>
> org.codehaus.plexus.component.configurator.converters.basic.AbstractBasicConverter.fromConfiguration
> (AbstractBasicConverter.java:53)
>        at
>
> org.codehaus.plexus.component.configurator.converters.ComponentValueSetter.configure
> (ComponentValueSetter.java:247)
>        at
>
> org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.processConfiguration
> (ObjectWithFieldsConverter.java:137)
>        at
>
> org.codehaus.plexus.component.configurator.BasicComponentConfigurator.configureComponent
> (BasicComponentConfigurator.java:56)
>        at
> org.apache.maven.plugin.DefaultPluginManager.populatePluginFields
> (DefaultPluginManager.java:1151)
>        ... 19 more
>
>
>
>
>
>
> On Nov 30, 2007 5:16 PM, Eduardo Burgos <[EMAIL PROTECTED]> wrote:
>
> > Still the same error guillaume, I deleted my repository.
> >
> >
> > [INFO]
> > ------------------------------------------------------------------------
> > [ERROR] BUILD ERROR
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] Failed to configure plugin parameters for:
> > org.codehaus.mojo:groovy-maven-plugin:1.0-beta-3-SNAPSHOT
> >
> >
> >
> > Cause: When configuring a basic element the configuration cannot contain
> > any child elements. Configuration element 'source'.
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] For more information, run Maven with the -e switch
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] Total time: 85 minutes 17 seconds
> > [INFO] Finished at: Fri Nov 30 16:23:41 AST 2007
> > [INFO] Final Memory: 93M/167M
> > [INFO]
> > ------------------------------------------------------------------------
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > On Nov 30, 2007 9:07 AM, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
> >
> > > I've retried without any problems on windows from a clean repo and
> clean
> > > checkout on maven 2.0.8 :-(
> > > Anybody else can reproduce the problem ?
> > >
> > > On Nov 30, 2007 10:02 AM, lhe77 < [EMAIL PROTECTED]> wrote:
> > >
> > > >
> > > > Guillaume,
> > > >
> > > > after deleting the whole local repo I get (and I remember that I had
> > > this
> > > > some time ago as well)
> > > > the following error:
> > > >
> > > > [INFO]
> > > >
> > > >
> > >
> ----------------------------------------------------------------------------
> > > > [INFO] Building ServiceMix :: Core
> > > > [INFO]    task-segment: [install]
> > > > [INFO]
> > > >
> > > >
> > >
> ----------------------------------------------------------------------------
> > > > [INFO] [checkstyle:checkstyle {execution: validate}]
> > > > [INFO] Source directory does not exist - skipping report.
> > > > [INFO] Preparing pmd:check
> > > > [INFO] [pmd:pmd]
> > > > [INFO] [pmd:check {execution: validate}]
> > > > [INFO] [build:copy {execution: default}]
> > > > [INFO] [site:attach-descriptor]
> > > > [INFO] [install:install]
> > > > [INFO] Installing
> > > /home/lhe/workspace/smix/apache_servicemix/core/pom.xml
> > > > to
> > > >
> /home/lhe/.m2/repository/org/apache/servicemix/core/3.3-SNAPSHOT/core-
> > > > 3.3-SNAPSHOT.pom
> > > > [INFO]
> > > >
> > > >
> > >
> ----------------------------------------------------------------------------
> > > > [INFO] Building ServiceMix :: JBI
> > > > [INFO]    task-segment: [install]
> > > > [INFO]
> > > >
> > > >
> > >
> ----------------------------------------------------------------------------
> > >
> > > > [INFO] [checkstyle:checkstyle {execution: validate}]
> > > > [INFO]
> > > >
> > >
> ------------------------------------------------------------------------
> > > > [ERROR] BUILD ERROR
> > > > [INFO]
> > > >
> > >
> ------------------------------------------------------------------------
> > > > [INFO] An error has occurred in Checkstyle report generation.
> > > >
> > > > Embedded error: Unable to process header location.
> > > > Unable to find location 'LICENSE.txt' as URL, File or Resource.
> > > > [INFO]
> > > >
> > >
> ------------------------------------------------------------------------
> > > > [INFO] For more information, run Maven with the -e switch
> > > > [INFO]
> > > >
> > >
> ------------------------------------------------------------------------
> > > > [INFO] Total time: 7 minutes 36 seconds
> > > > [INFO] Finished at: Fri Nov 30 09:58:03 CET 2007
> > > > [INFO] Final Memory: 24M/97M
> > > > [INFO]
> > > >
> > >
> ------------------------------------------------------------------------
> > > >
> > > > I know, it is possible to append -Pnochecks at the end of the mvn
> > > comand,
> > > > but is it possible to finally fix this?
> > > >
> > > > Thanks in advance,
> > > > Lars
> > > >
> > > > --
> > > > View this message in context:
> > > >
> > >
> http://www.nabble.com/build-error-3.3-SNAPSHOT-tf4892607s12049.html#a14042398
> > > > Sent from the ServiceMix - User mailing list archive at Nabble.com.
> > > >
> > > >
> > >
> > >
> > > --
> > > Cheers,
> > > Guillaume Nodet
> > > ------------------------
> > > Blog: http://gnodet.blogspot.com/
> > >
> >
> >
>



-- 
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/

Reply via email to