You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Allison, Bob" <ro...@qwest.com> on 2005/08/12 20:24:08 UTC

[m2] Problem (Bug?) Deploying Snapshot Jar

I'm building a small jar to extend log4j for our environment.  If the
version in pom.xml is "3.0", I get the following output from "m2
deploy":
[INFO] [jar:jar]
[INFO] Building jar:
/net/home/allisord/src/qaccess-3.0/3rd-party/log4j/target/log4j-3.0.jar
[INFO] [source:jar]
[INFO] Building jar:
/net/home/allisord/src/qaccess-3.0/3rd-party/log4j/target/log4j-3.0-sour
ces.jar
[INFO] [install:install]
[INFO] Installing
/net/home/allisord/src/qaccess-3.0/3rd-party/log4j/target/log4j-3.0.jar
to /home/allisord/.m2/repository/qaccess/log4j/3.0/log4j-3.0.jar
[INFO] Installing
/net/home/allisord/src/qaccess-3.0/3rd-party/log4j/target/log4j-3.0-sour
ces.jar to
/home/allisord/.m2/repository/qaccess/log4j/3.0/log4j-3.0-sources.jar
[INFO] [deploy:deploy]
Uploading:
scp://qadev-home.dev.qintra.com/home/qadev-home/m2//qaccess/log4j/3.0/lo
g4j-3.0.jar
15K uploaded
[INFO] Uploading project information for log4j 3.0
[INFO] Uploading project information for log4j 3.0
Uploading:
scp://qadev-home.dev.qintra.com/home/qadev-home/m2//qaccess/log4j/3.0/lo
g4j-3.0-sources.jar
14K uploaded

If I change the version to "3.0-SNAPSHOT" (like all of the Maven sources
are configured), I get the following:
[INFO] [jar:jar]
[INFO] Building jar:
/net/home/allisord/src/qaccess-3.0/3rd-party/log4j/target/log4j-3.0-SNAP
SHOT.jar
[INFO] [source:jar]
[INFO] Not producing source bundle for a SNAPSHOT build
[INFO] [install:install]
[INFO] Installing
/net/home/allisord/src/qaccess-3.0/3rd-party/log4j/target/log4j-3.0-SNAP
SHOT.jar to
/home/allisord/.m2/repository/qaccess/log4j/3.0-SNAPSHOT/log4j-3.0-SNAPS
HOT.jar
[INFO]
------------------------------------------------------------------------
----
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
----
[INFO] Diagnosis: Error configuring plugin for execution of
'deploy:deploy'.
[INFO]
------------------------------------------------------------------------
----
[ERROR] Cause:
org.apache.maven.plugin.MojoExecutionException: Error configuring plugin
for execution of 'deploy:deploy'.
        at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa
nager.java:342)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default
LifecycleExecutor.java:472)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec
ycle(DefaultLifecycleExecutor.java:445)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL
ifecycleExecutor.java:431)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
DefaultLifecycleExecutor.java:268)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec
ycleExecutor.java:127)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:186)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:292)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.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: Unable
to parse the created DOM for plugin configuration
        at
org.apache.maven.plugin.DefaultPluginManager.populatePluginFields(Defaul
tPluginManager.java:1022)
        at
org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPl
uginManager.java:522)
        at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa
nager.java:337)
        ... 15 more
Caused by:
org.codehaus.plexus.component.configurator.ComponentConfigurationExcepti
on: Class 'org.apache.maven.artifact.repository.ArtifactRepository'
cannot be instantiated
        at
org.codehaus.plexus.component.configurator.converters.AbstractConfigurat
ionConverter.instantiateObject(AbstractConfigurationConverter.java:120)
        at
org.codehaus.plexus.component.configurator.converters.composite.ObjectWi
thFieldsConverter.fromConfiguration(ObjectWithFieldsConverter.java:83)
        at
org.codehaus.plexus.component.configurator.converters.composite.ObjectWi
thFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java:11
8)
        at
org.codehaus.plexus.component.configurator.BasicComponentConfigurator.co
nfigureComponent(BasicComponentConfigurator.java:55)
        at
org.apache.maven.plugin.DefaultPluginManager.populatePluginFields(Defaul
tPluginManager.java:1017)
        ... 17 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.AbstractConfigurat
ionConverter.instantiateObject(AbstractConfigurationConverter.java:110)
        ... 21 more

This is on a fresh build from SVN this morning.  I cleaned out my local
repository, updated my SVN tree (to revision 232341), rebuilt m2, and
tried it again.  Same results.  Running as "m2 clean:clean deploy"
produces the same results.  If I run "m2 install" instead, the install
works fine but a subsequent deploy still fails the same way.

Am I missing something?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: [m2] Problem (Bug?) Deploying Snapshot Jar

Posted by Brett Porter <br...@apache.org>.
I think I narrowed this down to it not falling back to the default repo
as it should if there is no snapshot repo in the pom.

- Brett

Brett Porter wrote:

>Has it been put into JIRA?
>
>- Brett
>
>dan tran wrote:
>
>  
>
>>I am experiencing the same problem.  Hopefully will get fixed sooon.
>>
>>-Dan
>>
>> 
>>
>>    
>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>For additional commands, e-mail: dev-help@maven.apache.org
>
>
>  
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: [m2] Problem (Bug?) Deploying Snapshot Jar

Posted by Brett Porter <br...@apache.org>.
Has it been put into JIRA?

- Brett

dan tran wrote:

>I am experiencing the same problem.  Hopefully will get fixed sooon.
>
>-Dan
>
>  
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: [m2] Problem (Bug?) Deploying Snapshot Jar

Posted by dan tran <da...@gmail.com>.
I am experiencing the same problem.  Hopefully will get fixed sooon.

-Dan


On 8/12/05, Allison, Bob <ro...@qwest.com> wrote:
> I'm building a small jar to extend log4j for our environment.  If the
> version in pom.xml is "3.0", I get the following output from "m2
> deploy":
> [INFO] [jar:jar]
> [INFO] Building jar:
> /net/home/allisord/src/qaccess-3.0/3rd-party/log4j/target/log4j-3.0.jar
> [INFO] [source:jar]
> [INFO] Building jar:
> /net/home/allisord/src/qaccess-3.0/3rd-party/log4j/target/log4j-3.0-sour
> ces.jar
> [INFO] [install:install]
> [INFO] Installing
> /net/home/allisord/src/qaccess-3.0/3rd-party/log4j/target/log4j-3.0.jar
> to /home/allisord/.m2/repository/qaccess/log4j/3.0/log4j-3.0.jar
> [INFO] Installing
> /net/home/allisord/src/qaccess-3.0/3rd-party/log4j/target/log4j-3.0-sour
> ces.jar to
> /home/allisord/.m2/repository/qaccess/log4j/3.0/log4j-3.0-sources.jar
> [INFO] [deploy:deploy]
> Uploading:
> scp://qadev-home.dev.qintra.com/home/qadev-home/m2//qaccess/log4j/3.0/lo
> g4j-3.0.jar
> 15K uploaded
> [INFO] Uploading project information for log4j 3.0
> [INFO] Uploading project information for log4j 3.0
> Uploading:
> scp://qadev-home.dev.qintra.com/home/qadev-home/m2//qaccess/log4j/3.0/lo
> g4j-3.0-sources.jar
> 14K uploaded
> 
> If I change the version to "3.0-SNAPSHOT" (like all of the Maven sources
> are configured), I get the following:
> [INFO] [jar:jar]
> [INFO] Building jar:
> /net/home/allisord/src/qaccess-3.0/3rd-party/log4j/target/log4j-3.0-SNAP
> SHOT.jar
> [INFO] [source:jar]
> [INFO] Not producing source bundle for a SNAPSHOT build
> [INFO] [install:install]
> [INFO] Installing
> /net/home/allisord/src/qaccess-3.0/3rd-party/log4j/target/log4j-3.0-SNAP
> SHOT.jar to
> /home/allisord/.m2/repository/qaccess/log4j/3.0-SNAPSHOT/log4j-3.0-SNAPS
> HOT.jar
> [INFO]
> ------------------------------------------------------------------------
> ----
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> ----
> [INFO] Diagnosis: Error configuring plugin for execution of
> 'deploy:deploy'.
> [INFO]
> ------------------------------------------------------------------------
> ----
> [ERROR] Cause:
> org.apache.maven.plugin.MojoExecutionException: Error configuring plugin
> for execution of 'deploy:deploy'.
>        at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa
> nager.java:342)
>        at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default
> LifecycleExecutor.java:472)
>        at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec
> ycle(DefaultLifecycleExecutor.java:445)
>        at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL
> ifecycleExecutor.java:431)
>        at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
> DefaultLifecycleExecutor.java:268)
>        at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec
> ycleExecutor.java:127)
>        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:186)
>        at org.apache.maven.cli.MavenCli.main(MavenCli.java:292)
>        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>        at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
> a:39)
>        at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
> Impl.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: Unable
> to parse the created DOM for plugin configuration
>        at
> org.apache.maven.plugin.DefaultPluginManager.populatePluginFields(Defaul
> tPluginManager.java:1022)
>        at
> org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPl
> uginManager.java:522)
>        at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa
> nager.java:337)
>        ... 15 more
> Caused by:
> org.codehaus.plexus.component.configurator.ComponentConfigurationExcepti
> on: Class 'org.apache.maven.artifact.repository.ArtifactRepository'
> cannot be instantiated
>        at
> org.codehaus.plexus.component.configurator.converters.AbstractConfigurat
> ionConverter.instantiateObject(AbstractConfigurationConverter.java:120)
>        at
> org.codehaus.plexus.component.configurator.converters.composite.ObjectWi
> thFieldsConverter.fromConfiguration(ObjectWithFieldsConverter.java:83)
>        at
> org.codehaus.plexus.component.configurator.converters.composite.ObjectWi
> thFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java:11
> 8)
>        at
> org.codehaus.plexus.component.configurator.BasicComponentConfigurator.co
> nfigureComponent(BasicComponentConfigurator.java:55)
>        at
> org.apache.maven.plugin.DefaultPluginManager.populatePluginFields(Defaul
> tPluginManager.java:1017)
>        ... 17 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.AbstractConfigurat
> ionConverter.instantiateObject(AbstractConfigurationConverter.java:110)
>        ... 21 more
> 
> This is on a fresh build from SVN this morning.  I cleaned out my local
> repository, updated my SVN tree (to revision 232341), rebuilt m2, and
> tried it again.  Same results.  Running as "m2 clean:clean deploy"
> produces the same results.  If I run "m2 install" instead, the install
> works fine but a subsequent deploy still fails the same way.
> 
> Am I missing something?
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
> 
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org