Re: Help with Maven 2 error!

2006-12-01 Thread Wayne Fay

Neither of those are errors. Both are warnings.

Where's the error?

Wayne

On 12/1/06, Shaun McGlinchey <[EMAIL PROTECTED]> wrote:

I have made no changes to my configuration, files of a Maven project which
was until recently working.

When trying to build the project I get the following error:

[WARNING] POM for 'org.jvnet.staxex:stax-ex:pom:1.0-SNAPSHOT:runtime' is
invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0
POM.
[WARNING] POM for 'com.sun.xml.stream.buffer:streambuffer:pom:0.3:runtime'
is invalid. It will be ignored for artifact resolution. Reason: Failed to
validate POM

Can anybody tell me what has caused this problem?

Thankyou
Shaun

_
Windows Live™ Messenger has arrived. Click here to download it for free!
http://imagine-msn.com/messenger/launch80/?locale=en-gb


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




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



Help with Maven 2 error!

2006-12-01 Thread Shaun McGlinchey
I have made no changes to my configuration, files of a Maven project which 
was until recently working.


When trying to build the project I get the following error:

[WARNING] POM for 'org.jvnet.staxex:stax-ex:pom:1.0-SNAPSHOT:runtime' is 
invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 
POM.
[WARNING] POM for 'com.sun.xml.stream.buffer:streambuffer:pom:0.3:runtime' 
is invalid. It will be ignored for artifact resolution. Reason: Failed to 
validate POM


Can anybody tell me what has caused this problem?

Thankyou
Shaun

_
Windows Live™ Messenger has arrived. Click here to download it for free! 
http://imagine-msn.com/messenger/launch80/?locale=en-gb



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



Re: Maven 2 error

2005-07-15 Thread Jason van Zyl
On Thu, 2005-07-14 at 21:52 +0200, solo turn wrote:
> i get something like this now with v alpha-3.
> 
> $ m2 -e archtype:create -DgroupID=ts -DartifactId=demoapp
> + Error stacktraces are turned on.

You have groupID there not groupId ...

-- 
jvz.

Jason van Zyl
jason at maven.org
http://maven.apache.org

We know what we are, but know not what we may be.

  -- Shakespeare


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



Re: Maven 2 error

2005-07-14 Thread John Casey

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1



solo turn wrote:



| 'org.apache.maven.plugins:maven-archtype-plugin': Cannot resolve

This appears to be a typo, probably from your command line or from your POM.

It should be maven-archetype-plugin, so if you're invoking directly from
the command line, use:

m2 archetype: 

HTH,
john
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFC1sNLK3h2CZwO/4URAiT7AKCm55NF84Np5griP+frjlGwLSRIYwCeMuiP
Z7wtx5f4x1pZpvKDazfU0cw=
=eca3
-END PGP SIGNATURE-

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



Re: Maven 2 error

2005-07-14 Thread solo turn
i get something like this now with v alpha-3.

$ m2 -e archtype:create -DgroupID=ts -DartifactId=demoapp
+ Error stacktraces are turned on.
[INFO] 

[INFO] Building Maven Default Project
[INFO] 

[INFO] maven-archtype-plugin: checking for updates from central-plugins
[INFO] Retrieving release information for maven-archtype-plugin
FATAL ERROR: Error executing Maven for a project
Error stacktrace:
org.apache.maven.reactor.ReactorException: Error executing project
within the reactor
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:190)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:269)
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:324)
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.lifecycle.LifecycleExecutionException:
Error resolving plugin version
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:537)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:149)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:133)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:103)
at org.apache.maven.DefaultMaven.processProject(DefaultMaven.java:261)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:180)
... 9 more
Caused by: org.apache.maven.plugin.version.PluginVersionResolutionException:
Error resolving version for
'org.apache.maven.plugins:maven-archtype-plugin': Cannot resolve
RELEASE version of this plugin.
at 
org.apache.maven.plugin.version.DefaultPluginVersionManager.resolveReleaseVersion(DefaultPluginVersionManager.java:570)
at 
org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:130)
at 
org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:192)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:528)


On 4/30/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> I have corrected the problem in the velocity metadata and am pushing
> it out now. It lists a lot of optional dependencies - for now they are
> commented out.
> 
> - Brett

> > >>m2 archetype:create -DgroupId=com.pcmsgroup.v21.common.logging
> > >>-DartifactId=v21-common-logging
> > >>
> > >>as detailed, and once I'd sorted my proxy settings, all
> > >>looked well, until I got the little stack trace at the end.
> > >>From what I could find on mailing lists it seems to be an
> > >>invalid or missing dependency, how can I fix it? Also where'd
> > >>the wiki go? FAQ's for M2 would be quite handy.
> > >>
> > >>Thanks
> > >>
> > >>Simon
> > >>
> > >>
> > >>org.apache.maven.reactor.ReactorException: Error executing
> > >>project within the reactor
> > >>at
> > >>org.apache.maven.DefaultMaven.execute(DefaultMaven.java:144)
> > >>at org.apache.maven.cli.MavenCli.main(MavenCli.java:233)
> > >>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > >>at
> > >>sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccess
> > >>orImpl.jav
> > >>a:39)
> > >>at
> > >>sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth
> > >>odAccessor
> > >>Impl.java:25)
> > >>at java.lang.reflect.Method.invoke(Method.java:324)
> > >>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.lifecycle.LifecycleExecutionException: Error
> > >>during lifecycle execution
> > >>at
> > >>org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(De
> > >>faultLifec
> > >>ycleExecutor.java:154)
> > >>at
> > >>org.apache.maven.DefaultMaven.processProject(DefaultMaven.java:212)
> > >>at
> > >>org.apache.maven.DefaultMaven.execute(DefaultMaven.java:136)
> > >>... 9 more
> > >>Caused by:
> > >>org.apache.maven.artifact.resolver.ArtifactRes

Re: Maven 2 error

2005-04-29 Thread Brett Porter
I have corrected the problem in the velocity metadata and am pushing
it out now. It lists a lot of optional dependencies - for now they are
commented out.

- Brett

On 4/30/05, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
> comment out the jdbc dependency in the velocity.pom in the m2
> repository. This will enable m2 to generate the project.
> 
> Martijn
> 
> 
> Simon Matic Langford wrote:
> 
> >alas, I'm trying to create the pom file using m2, so I don't have any
> >dependencies
> >yet, I don't even have a pom file.
> >
> >
> >
> >
> >>-Original Message-
> >>From: BADIHI David [mailto:[EMAIL PROTECTED]
> >>Sent: 29 April 2005 17:17
> >>To: Maven Users List
> >>Subject: RE: Maven 2 error
> >>
> >>
> >>Hi,
> >>
> >>You can put the missing jar in your repository, then in your
> >>POM file, indicate its name.
> >>
> >>Example :
> >>
> >>
> >>
> >>  struts
> >>  struts
> >>  1.1
> >>
> >>
> >>
> >>
> >>-Message d'origine-
> >>De : Simon Matic Langford [mailto:[EMAIL PROTECTED]
> >>Envoyé : vendredi 29 avril 2005 18:08
> >>À : users@maven.apache.org
> >>Objet : Maven 2 error
> >>
> >>Hi,
> >>
> >>I downloaded maven2 and tried to follow the getting started
> >>instructions, so I ran:
> >>
> >>m2 archetype:create -DgroupId=com.pcmsgroup.v21.common.logging
> >>-DartifactId=v21-common-logging
> >>
> >>as detailed, and once I'd sorted my proxy settings, all
> >>looked well, until I got the little stack trace at the end.
> >>From what I could find on mailing lists it seems to be an
> >>invalid or missing dependency, how can I fix it? Also where'd
> >>the wiki go? FAQ's for M2 would be quite handy.
> >>
> >>Thanks
> >>
> >>Simon
> >>
> >>
> >>org.apache.maven.reactor.ReactorException: Error executing
> >>project within the reactor
> >>at
> >>org.apache.maven.DefaultMaven.execute(DefaultMaven.java:144)
> >>at org.apache.maven.cli.MavenCli.main(MavenCli.java:233)
> >>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >>at
> >>sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccess
> >>orImpl.jav
> >>a:39)
> >>at
> >>sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth
> >>odAccessor
> >>Impl.java:25)
> >>at java.lang.reflect.Method.invoke(Method.java:324)
> >>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.lifecycle.LifecycleExecutionException: Error
> >>during lifecycle execution
> >>at
> >>org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(De
> >>faultLifec
> >>ycleExecutor.java:154)
> >>at
> >>org.apache.maven.DefaultMaven.processProject(DefaultMaven.java:212)
> >>at
> >>org.apache.maven.DefaultMaven.execute(DefaultMaven.java:136)
> >>... 9 more
> >>Caused by:
> >>org.apache.maven.artifact.resolver.ArtifactResolutionException
> >>: Error transitively resolving artifacts:
> >>at
> >>org.apache.maven.artifact.resolver.DefaultArtifactResolver.res
> >>olveTransi
> >>tively(DefaultArtifactResolver.java:191)
> >>at
> >>org.codehaus.plexus.DefaultArtifactEnabledContainer.addCompone
> >>nt(Default
> >>ArtifactEnabledContainer.java:183)
> >>at
> >>org.apache.maven.plugin.DefaultPluginManager.addPlugin(Default
> >>PluginMana
> >>ger.java:299)
> >>at
> >>org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(Defa
> >>ultPluginM
> >>anager.java:272)
> >>at
> >>org.apache.maven.plugin.DefaultPluginManager.verifyPluginForGo
> >>al(Default
> >>PluginManager.java:219)
> >>at
> >>org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyMojo
> >>Phase(Defa
> >>u

Re: Maven 2 error

2005-04-29 Thread Martijn Dashorst
comment out the jdbc dependency in the velocity.pom in the m2
repository. This will enable m2 to generate the project.

Martijn


Simon Matic Langford wrote:

>alas, I'm trying to create the pom file using m2, so I don't have any
>dependencies
>yet, I don't even have a pom file.
> 
>
>  
>
>>-Original Message-
>>From: BADIHI David [mailto:[EMAIL PROTECTED] 
>>Sent: 29 April 2005 17:17
>>To: Maven Users List
>>Subject: RE: Maven 2 error
>>
>>
>>Hi,
>>
>>You can put the missing jar in your repository, then in your 
>>POM file, indicate its name.
>>
>>Example :
>>
>>
>>
>>  struts
>>  struts
>>  1.1
>>
>>
>>
>>
>>-Message d'origine-
>>De : Simon Matic Langford [mailto:[EMAIL PROTECTED] 
>>Envoyé : vendredi 29 avril 2005 18:08
>>À : users@maven.apache.org
>>Objet : Maven 2 error
>>
>>Hi,
>>
>>I downloaded maven2 and tried to follow the getting started 
>>instructions, so I ran:
>>
>>m2 archetype:create -DgroupId=com.pcmsgroup.v21.common.logging
>>-DartifactId=v21-common-logging
>>
>>as detailed, and once I'd sorted my proxy settings, all 
>>looked well, until I got the little stack trace at the end. 
>>From what I could find on mailing lists it seems to be an 
>>invalid or missing dependency, how can I fix it? Also where'd 
>>the wiki go? FAQ's for M2 would be quite handy.
>>
>>Thanks
>>
>>Simon
>>
>>
>>org.apache.maven.reactor.ReactorException: Error executing 
>>project within the reactor
>>at 
>>org.apache.maven.DefaultMaven.execute(DefaultMaven.java:144)
>>at org.apache.maven.cli.MavenCli.main(MavenCli.java:233)
>>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>at
>>sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccess
>>orImpl.jav
>>a:39)
>>at
>>sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth
>>odAccessor
>>Impl.java:25)
>>at java.lang.reflect.Method.invoke(Method.java:324)
>>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.lifecycle.LifecycleExecutionException: Error 
>>during lifecycle execution
>>at
>>org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(De
>>faultLifec
>>ycleExecutor.java:154)
>>at
>>org.apache.maven.DefaultMaven.processProject(DefaultMaven.java:212)
>>at 
>>org.apache.maven.DefaultMaven.execute(DefaultMaven.java:136)
>>... 9 more
>>Caused by:
>>org.apache.maven.artifact.resolver.ArtifactResolutionException
>>: Error transitively resolving artifacts:
>>at
>>org.apache.maven.artifact.resolver.DefaultArtifactResolver.res
>>olveTransi
>>tively(DefaultArtifactResolver.java:191)
>>at
>>org.codehaus.plexus.DefaultArtifactEnabledContainer.addCompone
>>nt(Default
>>ArtifactEnabledContainer.java:183)
>>at
>>org.apache.maven.plugin.DefaultPluginManager.addPlugin(Default
>>PluginMana
>>ger.java:299)
>>at
>>org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(Defa
>>ultPluginM
>>anager.java:272)
>>at
>>org.apache.maven.plugin.DefaultPluginManager.verifyPluginForGo
>>al(Default
>>PluginManager.java:219)
>>at
>>org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyMojo
>>Phase(Defa
>>ultLifecycleExecutor.java:377)
>>at
>>org.apache.maven.lifecycle.DefaultLifecycleExecutor.processGoa
>>lChain(Def
>>aultLifecycleExecutor.java:353)
>>at
>>org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(De
>>faultLifec
>>ycleExecutor.java:136)
>>... 11 more
>>Caused by:
>>org.apache.maven.artifact.resolver.TransitiveArtifactResolutio
>>nException
>>: Error retrieving metadata [jdbc:jdbc:jar:2.0] :
>>at
>>org.apache.maven.artifact.resolver.DefaultArtifactResolver.col
>>lect(Defau
>>ltArtifactResolver.java:307)
>>at
>>org.apache.maven.artifact.resolver.DefaultArtifactResolver.res
>>olveTransi
>>tively(DefaultArtifactResolver.java:187)
>> 

RE: Maven 2 error

2005-04-29 Thread Simon Matic Langford
alas, I'm trying to create the pom file using m2, so I don't have any
dependencies
yet, I don't even have a pom file.
 

> -Original Message-
> From: BADIHI David [mailto:[EMAIL PROTECTED] 
> Sent: 29 April 2005 17:17
> To: Maven Users List
> Subject: RE: Maven 2 error
> 
> 
> Hi,
> 
> You can put the missing jar in your repository, then in your 
> POM file, indicate its name.
> 
> Example :
> 
> 
> 
>   struts
>   struts
>   1.1
> 
> 
> 
> 
> -Message d'origine-
> De : Simon Matic Langford [mailto:[EMAIL PROTECTED] 
> Envoyé : vendredi 29 avril 2005 18:08
> À : users@maven.apache.org
> Objet : Maven 2 error
> 
> Hi,
> 
> I downloaded maven2 and tried to follow the getting started 
> instructions, so I ran:
> 
> m2 archetype:create -DgroupId=com.pcmsgroup.v21.common.logging
> -DartifactId=v21-common-logging
> 
> as detailed, and once I'd sorted my proxy settings, all 
> looked well, until I got the little stack trace at the end. 
> From what I could find on mailing lists it seems to be an 
> invalid or missing dependency, how can I fix it? Also where'd 
> the wiki go? FAQ's for M2 would be quite handy.
> 
> Thanks
> 
> Simon
> 
> 
> org.apache.maven.reactor.ReactorException: Error executing 
> project within the reactor
> at 
> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:144)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:233)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccess
> orImpl.jav
> a:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth
> odAccessor
> Impl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> 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.lifecycle.LifecycleExecutionException: Error 
> during lifecycle execution
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(De
> faultLifec
> ycleExecutor.java:154)
> at
> org.apache.maven.DefaultMaven.processProject(DefaultMaven.java:212)
> at 
> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:136)
> ... 9 more
> Caused by:
> org.apache.maven.artifact.resolver.ArtifactResolutionException
> : Error transitively resolving artifacts:
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.res
> olveTransi
> tively(DefaultArtifactResolver.java:191)
> at
> org.codehaus.plexus.DefaultArtifactEnabledContainer.addCompone
> nt(Default
> ArtifactEnabledContainer.java:183)
> at
> org.apache.maven.plugin.DefaultPluginManager.addPlugin(Default
> PluginMana
> ger.java:299)
> at
> org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(Defa
> ultPluginM
> anager.java:272)
> at
> org.apache.maven.plugin.DefaultPluginManager.verifyPluginForGo
> al(Default
> PluginManager.java:219)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyMojo
> Phase(Defa
> ultLifecycleExecutor.java:377)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.processGoa
> lChain(Def
> aultLifecycleExecutor.java:353)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(De
> faultLifec
> ycleExecutor.java:136)
> ... 11 more
> Caused by:
> org.apache.maven.artifact.resolver.TransitiveArtifactResolutio
> nException
> : Error retrieving metadata [jdbc:jdbc:jar:2.0] :
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.col
> lect(Defau
> ltArtifactResolver.java:307)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.res
> olveTransi
> tively(DefaultArtifactResolver.java:187)
> ... 18 more
> Caused by:
> org.apache.maven.artifact.metadata.ArtifactMetadataRetrievalException:
> Unable to read the metadata file
> at
> org.apache.maven.artifact.MavenMetadataSource.retrieve(MavenMe
> tadataSour
> ce.java:89)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.col
> lect(Defau
> ltArtifactResolver.java:303)
> ... 19 more
> Caused by: org.apache.maven.project.ProjectBuildingException: 
> Unable to find artifact: jdbc:jdbc:pom:2.0
> at
> org.apache.maven.project.

RE: Maven 2 error

2005-04-29 Thread BADIHI David
Hi,

You can put the missing jar in your repository, then in your POM file, indicate 
its name.

Example :



  struts
  struts
  1.1




-Message d'origine-
De : Simon Matic Langford [mailto:[EMAIL PROTECTED] 
Envoyé : vendredi 29 avril 2005 18:08
À : users@maven.apache.org
Objet : Maven 2 error

Hi,

I downloaded maven2 and tried to follow the getting started instructions, so I 
ran:

m2 archetype:create -DgroupId=com.pcmsgroup.v21.common.logging
-DartifactId=v21-common-logging

as detailed, and once I'd sorted my proxy settings, all looked well, until I 
got the little stack trace at the end. From what I could find on mailing lists 
it seems to be an invalid or missing dependency, how can I fix it? Also where'd 
the wiki go? FAQ's for M2 would be quite handy.

Thanks

Simon


org.apache.maven.reactor.ReactorException: Error executing project within the 
reactor
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:144)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:233)
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:324)
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.lifecycle.LifecycleExecutionException: Error during 
lifecycle execution
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec
ycleExecutor.java:154)
at
org.apache.maven.DefaultMaven.processProject(DefaultMaven.java:212)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:136)
... 9 more
Caused by:
org.apache.maven.artifact.resolver.ArtifactResolutionException: Error 
transitively resolving artifacts:
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransi
tively(DefaultArtifactResolver.java:191)
at
org.codehaus.plexus.DefaultArtifactEnabledContainer.addComponent(Default
ArtifactEnabledContainer.java:183)
at
org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginMana
ger.java:299)
at
org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginM
anager.java:272)
at
org.apache.maven.plugin.DefaultPluginManager.verifyPluginForGoal(Default
PluginManager.java:219)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyMojoPhase(Defa
ultLifecycleExecutor.java:377)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.processGoalChain(Def
aultLifecycleExecutor.java:353)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec
ycleExecutor.java:136)
... 11 more
Caused by:
org.apache.maven.artifact.resolver.TransitiveArtifactResolutionException
: Error retrieving metadata [jdbc:jdbc:jar:2.0] :
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.collect(Defau
ltArtifactResolver.java:307)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransi
tively(DefaultArtifactResolver.java:187)
... 18 more
Caused by:
org.apache.maven.artifact.metadata.ArtifactMetadataRetrievalException:
Unable to read the metadata file
at
org.apache.maven.artifact.MavenMetadataSource.retrieve(MavenMetadataSour
ce.java:89)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.collect(Defau
ltArtifactResolver.java:303)
... 19 more
Caused by: org.apache.maven.project.ProjectBuildingException: Unable to find 
artifact: jdbc:jdbc:pom:2.0
at
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromReposit
ory(DefaultMavenProjectBuilder.java:167)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(
DefaultMavenProjectBuilder.java:149)
at
org.apache.maven.artifact.MavenMetadataSource.retrieve(MavenMetadataSour
ce.java:83)
... 20 more


The information contained in this e-mail is intended only for the person or 
entity to which it is addressed and may contain confidential and/or privileged 
material. If You are not the intended recipient of this e-mail, the use of this 
information or any disclosure, copying or distribution is Prohibited and may be 
unlawful. If you received this in error, please contact the sender and delete 
the material from any computer. The views expressed in this e-mail may not 
necessarily be the views of The PCMS Group plc and should not be taken as 
authority to carry out any instruction contained.
 


-
To unsubscribe, e-mail: [

Maven 2 error

2005-04-29 Thread Simon Matic Langford
Hi,

I downloaded maven2 and tried to follow the getting started
instructions, so I ran:

m2 archetype:create -DgroupId=com.pcmsgroup.v21.common.logging
-DartifactId=v21-common-logging

as detailed, and once I'd sorted my proxy settings, all looked well,
until I got the little stack trace at the end. From what I could
find on mailing lists it seems to be an invalid or missing dependency,
how can I fix it? Also where'd the wiki go? FAQ's for M2
would be quite handy.

Thanks

Simon


org.apache.maven.reactor.ReactorException: Error executing project
within the reactor
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:144)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:233)
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:324)
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.lifecycle.LifecycleExecutionException: Error
during lifecycle execution
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec
ycleExecutor.java:154)
at
org.apache.maven.DefaultMaven.processProject(DefaultMaven.java:212)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:136)
... 9 more
Caused by:
org.apache.maven.artifact.resolver.ArtifactResolutionException: Error
transitively resolving artifacts:
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransi
tively(DefaultArtifactResolver.java:191)
at
org.codehaus.plexus.DefaultArtifactEnabledContainer.addComponent(Default
ArtifactEnabledContainer.java:183)
at
org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginMana
ger.java:299)
at
org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginM
anager.java:272)
at
org.apache.maven.plugin.DefaultPluginManager.verifyPluginForGoal(Default
PluginManager.java:219)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyMojoPhase(Defa
ultLifecycleExecutor.java:377)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.processGoalChain(Def
aultLifecycleExecutor.java:353)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec
ycleExecutor.java:136)
... 11 more
Caused by:
org.apache.maven.artifact.resolver.TransitiveArtifactResolutionException
: Error retrieving metadata [jdbc:jdbc:jar:2.0] :
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.collect(Defau
ltArtifactResolver.java:307)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransi
tively(DefaultArtifactResolver.java:187)
... 18 more
Caused by:
org.apache.maven.artifact.metadata.ArtifactMetadataRetrievalException:
Unable to read the metadata file
at
org.apache.maven.artifact.MavenMetadataSource.retrieve(MavenMetadataSour
ce.java:89)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.collect(Defau
ltArtifactResolver.java:303)
... 19 more
Caused by: org.apache.maven.project.ProjectBuildingException: Unable to
find artifact: jdbc:jdbc:pom:2.0
at
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromReposit
ory(DefaultMavenProjectBuilder.java:167)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(
DefaultMavenProjectBuilder.java:149)
at
org.apache.maven.artifact.MavenMetadataSource.retrieve(MavenMetadataSour
ce.java:83)
... 20 more


The information contained in this e-mail is intended only for the person
or
entity to which it is addressed and may contain confidential and/or
privileged material. If You are not the intended recipient of this
e-mail,
the use of this information or any disclosure, copying or distribution
is
Prohibited and may be unlawful. If you received this in error, please
contact the sender and delete the material from any computer. The views
expressed in this e-mail may not necessarily be the views of The PCMS
Group
plc and should not be taken as authority to carry out any instruction
contained.