[
http://jira.codehaus.org/browse/WAGON-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter moved WAGONSSH-38 to WAGON-159:
--------------------------------------------
Affects Version/s: (was: 1.0-alpha-6)
Component/s: (was: wagon-ssh)
wagon-ssh
Key: WAGON-159 (was: WAGONSSH-38)
Project: Maven Wagon (was: wagon-ssh)
> multi-project deploy issue
> --------------------------
>
> Key: WAGON-159
> URL: http://jira.codehaus.org/browse/WAGON-159
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-ssh
> Reporter: Jerome Lacoste
>
> I have a m2 plugin (webstart-maven-plugin) that I wish to deploy using scp to
> a remote server. The plugin code is split in several modules according to the
> following layout:
> pom.xml
> module1/
> module2/
> module3/
> plugin/pom.xml (maven-plugin packaging)
> plugin/pom.xml contains the <distributionManagement> and I am using both
> <repository> and <snapshotRepository>. My ~/.m2/settings.xml contains info
> for my server access.
> If I deploy from within the plugin directory, I have no problem.
> If I deploy from the root directory, 'mvn deploy' fails with the following
> error:
> [INFO] Failed to configure plugin parameters for:
> org.apache.maven.plugins:maven-deploy-plugin:2.1
> Cause: Class 'org.apache.maven.artifact.repository.ArtifactRepository' cannot
> be instantiated
> [INFO]
> ----------------------------------------------------------------------------
> [DEBUG] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Error configuring:
> org.apache.maven.plugins:maven-deploy-plugin. Reason: Unable
> to parse the created DOM for plugin configuration
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:560)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:472)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:451)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:303)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:270)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:139)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
> 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.apache.maven.plugins:maven-deploy-plugin. Reason: Unable to
> parse the created DOM for plugin configuration
> at
> org.apache.maven.plugin.DefaultPluginManager.populatePluginFields(DefaultPluginManager.java:1039)
> at
> org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:579)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:393)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:531)
> ... 16 more
> Caused by:
> org.codehaus.plexus.component.configurator.ComponentConfigurationException:
> Class 'org.apache.maven.artifact.repository.ArtifactRepository' cannot be
> instantiated
> at
> org.codehaus.plexus.component.configurator.converters.AbstractConfigurationConverter.instantiateObject(AbstractConfigurationConverter.java:121)
> at
> org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.fromConfiguration(ObjectWithFieldsConverter.java:88)
> 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:1033)
> ... 19 more
> Caused by: java.lang.InstantiationException:
> org.apache.maven.artifact.repository.ArtifactRepository
> at java.lang.Class.newInstance0(Class.java:335)
> at java.lang.Class.newInstance(Class.java:303)
> at
> org.codehaus.plexus.component.configurator.converters.AbstractConfigurationConverter.instantiateObject(AbstractConfigurationConverter.java:111)
> ... 24 more
> Error message looks like MNG-734
> Not sure if this setup is to be supported, but the exception is clearly not
> what I expected :)
> Just in case, I tried to place a <distributionManagement> block in both the
> pom.xml and the plugin/pom.xml, but that didn't help.
> Problem can be reproduced with the webstart-maven-plugin from the
> mojo-sandbox. Take it out, add a distribution section in your plugin/pom.xml
> and test.
--
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
