Strange problem with .m2 folder
Hi folks, I've just come across what seems to be some very strange behaviour in Maven. I'll try to explain as best I can the situation but it's a bit involved. So, I started out with this set up working which was working perfectly: maven 3.0.2 installed in d:\development\maven maven projects installed in c:\users\me\documents\NetBeansProjects .m2 directory in c:\users\me\.m2 nexus 1.9 used as a proxy for all the external repositories we use. everything built fine with a mvn clean install both from inside NetBeans and from the command line. Today I decided to re-home my Documents folder onto the company NAS. So I right click on the folder select location and change it to h:\documents. Much file copying later and everything is moved over. Since file compilation would be too slow over the network I move the NetBeans projects folder onto D so now I have this: maven 3.0.2 installed in d:\development\maven maven projects installed in d:\development\NetBeansProjects .m2 directory in c:\users\me\.m2 nexus 1.9 used as a proxy for all the external repositories we use. my documents folder at h:\documents Now here's where the problems start. When I tried to do a clean and build maven re-downloaded everything and I got a bunch of warnings about not being able to find various POM files. This confused the hell out of me since as far as I could tell nothing do to with maven had changed. Then I noticed that in my H drive I now had a shiny new .m2 directory. A little head scratching later and I realized that the warnings were because there was no settings.xml file in the h:\.m2 directory. Once I'd copied it over from c:\users\me\.m2 everything built fine. My question though is why did my maven create a new .m2 folder for me? I can only assume that it must be using the location of the my documents folder as it's queue for where to put the .m2 folder but surely it should be based on the root folder of the user account by default. Is it possible to force use c:\users\me\.m2 again as builds are now much slower since it has to drag all the jar's over the network each time? Thanks
Re: Strange problem with .m2 folder
Today I decided to re-home my Documents folder onto the company NAS. So I right click on the folder select location and change it to h:\documents. Much file copying later and everything is moved over. Since file compilation would be too slow over the network I move the NetBeans projects folder onto D so now I have this: What does set show for USERPROFILE, HOMEDRIVE, and HOMEPATH. Those are managed by Windows and IIRC they are read/used by Maven to determine where to put the .m2 directory etc. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Strange problem with .m2 folder
USERPROFILE=C:\Users\Graham Smith HOMEDRIVE=C: HOMEPATH=\Users\Graham Smith Exactly as I would expect. I'm running Win 7 btw. D:\Development\NetBeansProjects\core On 11 April 2011 19:47, Wayne Fay wayne...@gmail.com wrote: Today I decided to re-home my Documents folder onto the company NAS. So I right click on the folder select location and change it to h:\documents. Much file copying later and everything is moved over. Since file compilation would be too slow over the network I move the NetBeans projects folder onto D so now I have this: What does set show for USERPROFILE, HOMEDRIVE, and HOMEPATH. Those are managed by Windows and IIRC they are read/used by Maven to determine where to put the .m2 directory etc. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Strange problem with .m2 folder
on the root folder of the user account by default. Is it possible to force use c:\users\me\.m2 again as builds are now much slower since it has to drag all the jar's over the network each time? You can adjust the location of your repo in settings.xml, and it will use c:\... instead. As for your problem, I'm honestly unsure what to make of it right this minute. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Strange problem with .m2 folder
Thanks for your help, I think I've figured out what the problem is. I omitted to mention that I also re-homed my Desktop folder at the same time I re-homed my documents folder as I didn't think it was relevant. It would appear that there is a bug in the JVM that has been around for 6+ years now. Apparently the JVM determines the value of user.home by which should point at the root of the users profile directory by looking at the registry key: [HKEY_CURRENT_USER\Software\ customer \Windows\CurrentVersion\Explorer\Shell Folders\Desktop] and then taking the parent folder. In my case (and many others) that doesn't produce the expected result. http://bugs.sun.com/view_bug.do?bug_id=4787931 http://bugs.sun.com/view_bug.do?bug_id=4787931Looks like I'll be moving my desktop folder back in the morning... On 11 April 2011 19:59, Wayne Fay wayne...@gmail.com wrote: on the root folder of the user account by default. Is it possible to force use c:\users\me\.m2 again as builds are now much slower since it has to drag all the jar's over the network each time? You can adjust the location of your repo in settings.xml, and it will use c:\... instead. As for your problem, I'm honestly unsure what to make of it right this minute. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Strange problem with .m2 folder
It would appear that there is a bug in the JVM that has been around for 6+ years now. Apparently the JVM determines the value of user.home by which should point at the root of the users profile directory by looking at the registry key: [HKEY_CURRENT_USER\Software\ customer \Windows\CurrentVersion\Explorer\Shell Folders\Desktop] and then taking the parent folder. In my case (and many others) that doesn't produce the expected result. Perhaps this should be coded differently in Maven? There is a work-around suggested in that bug report: J2SE 1.5 will have a working System.getenv(String), so users can simply do a System.getenv(USERPROFILE) directly. I agree this is not intuitive. Obviously, most people are just using the system-default homedir and user dir etc so they don't run into this. But we could probably handle this better in Maven. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Problem w/M2 plugin--- Fixed
Hi,
I figured out the problem with the unable to read file error. I realized
that my file wasn't corrupted; I was just using an out-of-date maven 2.0
cargo plugin. I made the following change to my pom.xml file after making a
copy of my old codehaus directory; I changed:
urlhttp://cargo.codehaus.org/dist2-snapshot/url
To
urlhttp://snapshots.repository.codehaus.org/url
Then I ran the mvn package command. I found in Maven 2.0 that you have to
run some commands several times in order for a file to run correctly so
after running the command 4 times the package ran correctly. FYI, the error
message I was getting was an I/O Exception error so it just had to get all
of the information to run properly. Thank you for your help. Also, it is
hard to corrupt the codehaus file since maven creates it automatically with
the url.
Thanks again Wendy for your help and I hope that this message helps someone
else who has a message like this.
Matilda
-Original Message-
From: Wendy Smoak [mailto:[EMAIL PROTECTED]
Sent: Friday, July 14, 2006 11:24 AM
To: Maven Users List
Subject: Re: Problem w/M2 plugin
On 7/14/06, Matilda Robert [EMAIL PROTECTED] wrote:
Is anyone having problems with accessing information using maven 2.0 this
morning? I am getting the following error:
Project ID: org.codehaus.cargo-maven2-plugin
Reason: Error getting POM for 'org.codehaus.cargo:cargo-maven2-plugin'
from
the repository: Unable to read local copy of metadata: Cannot read
metadata
from 'C:\Folder File name
\username\.m2\repository\org\codehaus\cargo\cargo-maven2-plugin\maven-metada
ta-cargo m2 snapshot repository.xml': entity reference name can not
contain
character =' (position: TEXT seen
...dehaus.org/pages/editpage.action?spaceKey=${space.spaceKey}title=...
Yes, something similar happened here yesterday. It looks like you
have corrupted metadata in your local repository. This worked:
Delete Cargo from your local repository,
rm -rf $M2_REPO/org/codehaus/cargo
and then double-check the remote repo you're using to get the Cargo
snapshots. This one is working for me (up to yesterday I was using a
different one,):
http://snapshots.repository.codehaus.org
Then again, I build Cargo from source locally, so that may also have
fixed it. :)
HTH,
--
Wendy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
Attention:
Any views expressed in this message are those of the individual
sender, except where the message states otherwise and the sender is
authorized to state them to be the views of any such entity. The
information contained in this message and or attachments is
intended only for the person or entity to which it is addressed and
may contain confidential and/or privileged material. If you
received this in error, please contact the sender and delete the
material from any system and destroy any copies.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Problem w/M2 plugin
Hi all,
Is anyone having problems with accessing information using maven 2.0 this
morning? I am getting the following error:
Project ID: org.codehaus.cargo-maven2-plugin
Reason: Error getting POM for 'org.codehaus.cargo:cargo-maven2-plugin' from
the repository: Unable to read local copy of metadata: Cannot read metadata
from 'C:\Folder File name
\username\.m2\repository\org\codehaus\cargo\cargo-maven2-plugin\maven-metada
ta-cargo m2 snapshot repository.xml': entity reference name can not contain
character =' (position: TEXT seen
...dehaus.org/pages/editpage.action?spaceKey=${space.spaceKey}title=...
@210:120)
org.codehaus.cargo:cargo-maven2-plugin:pom:LATEST
For example, I get this error after running a mvn cargo:clean command.
Please let me know if anyone else is having this problem.
Thanks in advanced,
Matilda
-
Attention:
Any views expressed in this message are those of the individual
sender, except where the message states otherwise and the sender is
authorized to state them to be the views of any such entity. The
information contained in this message and or attachments is
intended only for the person or entity to which it is addressed and
may contain confidential and/or privileged material. If you
received this in error, please contact the sender and delete the
material from any system and destroy any copies.
Re: Problem w/M2 plugin
On 7/14/06, Matilda Robert [EMAIL PROTECTED] wrote:
Is anyone having problems with accessing information using maven 2.0 this
morning? I am getting the following error:
Project ID: org.codehaus.cargo-maven2-plugin
Reason: Error getting POM for 'org.codehaus.cargo:cargo-maven2-plugin' from
the repository: Unable to read local copy of metadata: Cannot read metadata
from 'C:\Folder File name
\username\.m2\repository\org\codehaus\cargo\cargo-maven2-plugin\maven-metada
ta-cargo m2 snapshot repository.xml': entity reference name can not contain
character =' (position: TEXT seen
...dehaus.org/pages/editpage.action?spaceKey=${space.spaceKey}title=...
Yes, something similar happened here yesterday. It looks like you
have corrupted metadata in your local repository. This worked:
Delete Cargo from your local repository,
rm -rf $M2_REPO/org/codehaus/cargo
and then double-check the remote repo you're using to get the Cargo
snapshots. This one is working for me (up to yesterday I was using a
different one,):
http://snapshots.repository.codehaus.org
Then again, I build Cargo from source locally, so that may also have
fixed it. :)
HTH,
--
Wendy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Problem w/M2 plugin
Thanks Wendy,
I will try it out.
Matilda
-Original Message-
From: Wendy Smoak [mailto:[EMAIL PROTECTED]
Sent: Friday, July 14, 2006 11:24 AM
To: Maven Users List
Subject: Re: Problem w/M2 plugin
On 7/14/06, Matilda Robert [EMAIL PROTECTED] wrote:
Is anyone having problems with accessing information using maven 2.0 this
morning? I am getting the following error:
Project ID: org.codehaus.cargo-maven2-plugin
Reason: Error getting POM for 'org.codehaus.cargo:cargo-maven2-plugin'
from
the repository: Unable to read local copy of metadata: Cannot read
metadata
from 'C:\Folder File name
\username\.m2\repository\org\codehaus\cargo\cargo-maven2-plugin\maven-metada
ta-cargo m2 snapshot repository.xml': entity reference name can not
contain
character =' (position: TEXT seen
...dehaus.org/pages/editpage.action?spaceKey=${space.spaceKey}title=...
Yes, something similar happened here yesterday. It looks like you
have corrupted metadata in your local repository. This worked:
Delete Cargo from your local repository,
rm -rf $M2_REPO/org/codehaus/cargo
and then double-check the remote repo you're using to get the Cargo
snapshots. This one is working for me (up to yesterday I was using a
different one,):
http://snapshots.repository.codehaus.org
Then again, I build Cargo from source locally, so that may also have
fixed it. :)
HTH,
--
Wendy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
Attention:
Any views expressed in this message are those of the individual
sender, except where the message states otherwise and the sender is
authorized to state them to be the views of any such entity. The
information contained in this message and or attachments is
intended only for the person or entity to which it is addressed and
may contain confidential and/or privileged material. If you
received this in error, please contact the sender and delete the
material from any system and destroy any copies.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem with M2 on Windows Servers - running tests
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Stephen, However, for two of our Windows systems, when we try and build the project using Maven 2, we get the following error. We are able to perform an mvn clean successfully on those machines, and also Java compilation succeeds. It's just running the tests that fails. When the tests fail, under the target directory exists a classes and a test-classes subdirectory, but no report directory. Have you tried to run mvn -e -X to see some debug messages? Perhaps there you'll see some more hints...? Have you checked whether these two Windows boxes have a different configuration than the other machines? I.e. different Java version, installation, Maven settings, ...? Any help you can give would be much appreciated. If the configuration is the same: Can you execute some of the JUnit tests per hand on these two machines? Thorsten -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (MingW32) iD8DBQFEIqNpQvObkgCcDe0RAtJxAKCiZ/NX2zvZm4rRDrJxtnmil40yVQCgkw25 gg2QA6pNPyJRxS3zKR6n4kY= =/TBO -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problem with M2 on Windows Servers - running tests
Hello,
We have a Java-based maven multi-project for which we've been using
Maven 1.0 successfully for several months.
We've recently upgraded to Maven 2.0.2, and for some of our systems, the
upgrade went successfully.
However, for two of our Windows systems, when we try and build the
project using Maven 2, we get the
following error. We are able to perform an mvn clean successfully on
those machines, and also
Java compilation succeeds. It's just running the tests that fails. When
the tests fail, under the target
directory exists a classes and a test-classes subdirectory, but no
report directory.
Any help you can give would be much appreciated.
Stephen
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Web Service Framework for CME
[INFO] WSF Common
[INFO] WSF Provider Interface
[INFO] WSF Hibernate Provider
[INFO] WSF Model
[INFO] WSF Object Server Provider
[INFO] WSF Object Server Plugin
[INFO] WSF Axis Demo Library
[INFO] WSF Service Common
[INFO] Axis integration
[INFO] WSF Hibernate Demo Web-Application
[INFO] WSF Object Server Demo Web-Application
[INFO] WSF System Tests Common
[INFO] WSF System Tests Hibernate
[INFO] WSF System Tests Obs
[INFO] WSF System Tests
[INFO]
[INFO] Building Web Service Framework for CME
[INFO]task-segment: [install]
[INFO]
[INFO] Skipping missing optional mojo:
org.apache.maven.plugins:maven-site-plugin:attach-descriptor
[INFO] [source:jar {execution: default}]
[INFO] NOT adding java-sources to attached artifacts for packaging:
'pom'.
[INFO] [install:install]
[INFO] Installing D:\project\wsf\pom.xml to C:\Documents and
Settings\stgest\.m2\repository\com\hp\ov\obs\obs-wsf\1.0pre6-SNAPSHOT\ob
s-wsf-1.0pre6-SNAPSHOT.pom
[INFO]
[INFO] Building WSF Common
[INFO]task-segment: [install]
[INFO]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [surefire:test]
[INFO] Setting reports dir:
D:\project\wsf\obs-ws-common\target/surefire-reports
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] There are some test failure.
[INFO]
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: There are some
test failure.
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default
LifecycleExecutor.java:556)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec
ycle(DefaultLifecycleExecutor.java:472)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL
ifecycleExecutor.java:451)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle
Failures(DefaultLifecycleExecutor.java:303)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
DefaultLifecycleExecutor.java:270)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec
ycleExecutor.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.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.MojoExecutionException: There are
some test failure.
at
org.apache.maven.test.SurefirePlugin.execute(SurefirePlugin.java:384)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa
nager.java:415)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default
LifecycleExecutor.java:531)
... 16 more
[INFO]
[INFO] Total time: 5 seconds
[INFO] Finished at: Wed Mar 22 14:17:55 MST 2006
[INFO] Final Memory: 4M/8M
FW: Problem with M2 on Windows Servers - running tests
-Original Message-
From: Gest, Stephen B
Sent: Wednesday, March 22, 2006 2:29 PM
To: 'users@maven.apache.org'
Subject: Problem with M2 on Windows Servers - running tests
Hello,
Here is additional information regarding the error:
Executing mvn -X install gives the following:
+ Error stacktraces are turned on.
[DEBUG] Building Maven user-level plugin registry from: 'C:\Documents
and Settings\stgest\.m2\plugin-registry.xml'
[DEBUG] Building Maven global-level plugin registry from: 'D:\Maven
2.0.2\conf\plugin-registry.xml'
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Web Service Framework for CME
[INFO] WSF Common
[INFO] WSF Provider Interface
[INFO] WSF Hibernate Provider
[INFO] WSF Model
[INFO] WSF Object Server Provider
[INFO] WSF Object Server Plugin
[INFO] WSF Axis Demo Library
[INFO] WSF Service Common
[INFO] Axis integration
[INFO] WSF Hibernate Demo Web-Application
[INFO] WSF Object Server Demo Web-Application
[INFO] WSF System Tests Common
[INFO] WSF System Tests Hibernate
[INFO] WSF System Tests Obs
[INFO] WSF System Tests
[INFO]
[INFO] Building Web Service Framework for CME
[INFO]task-segment: [install]
[INFO]
[DEBUG] maven-site-plugin: resolved to version 2.0-beta-4 from
repository central
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-site-plugin:maven-plugin:2.0-beta-4
[INFO] Skipping missing optional mojo:
org.apache.maven.plugins:maven-site-plugin:attach-descriptor
[DEBUG] maven-install-plugin: resolved to version 2.0 from repository
central
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-install-plugin:maven-plugin:2.0
[DEBUG] maven-compiler-plugin: resolved to version 2.0 from repository
central
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-compiler-plugin:maven-plugin:2.0
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-surefire-plugin:maven-plugin:2.1.2
[DEBUG] maven-source-plugin: resolved to version 2.0 from repository
central
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-source-plugin:maven-plugin:2.0
[DEBUG] org.apache.maven.plugins:maven-source-plugin:maven-plugin:2.0
(selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-project:jar:2.0
[DEBUG] org.apache.maven:maven-project:jar:2.0 (selected for runtime)
[DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 (selected for
runtime)
[DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8
(selected for runtime)
[DEBUG] classworlds:classworlds:jar:1.1-alpha-2 (selected for
runtime)
[DEBUG] junit:junit:jar:3.8.1 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
org.apache.maven:maven-artifact:jar:2.0
[DEBUG] org.apache.maven:maven-artifact:jar:2.0 (selected for
runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
org.apache.maven:maven-model:jar:2.0
[DEBUG] org.apache.maven:maven-model:jar:2.0 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
org.apache.maven:maven-artifact-manager:jar:2.0
[DEBUG] org.apache.maven:maven-artifact-manager:jar:2.0 (selected
for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
org.apache.maven:maven-repository-metadata:jar:2.0
[DEBUG] org.apache.maven:maven-repository-metadata:jar:2.0
(selected for runtime)
[DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5
(selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-profile:jar:2.0
[DEBUG] org.apache.maven:maven-profile:jar:2.0 (selected for
runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
org.apache.maven:maven-plugin-api:jar:2.0
[DEBUG] org.apache.maven:maven-plugin-api:jar:2.0 (selected for
runtime)
[DEBUG] org.codehaus.plexus:plexus-archiver:jar:1.0-alpha-3 (selected
for runtime)
[DEBUG] classworlds:classworlds:jar:1.1-alpha-2 (selected for
runtime)
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-source-plugin:2.0:jar' --
[DEBUG] (f) attach = true
[DEBUG] (f) compileSourceRoots = [D:\project\wsf\src\main\java]
[DEBUG] (f) finalName = obs-wsf-1.0pre6-SNAPSHOT
[DEBUG] (f) outputDirectory = D:\project\wsf\target
[DEBUG] (f) packaging = pom
[DEBUG] (f) project = [EMAIL PROTECTED]
[DEBUG] -- end configuration --
[INFO] [source:jar {execution: default}]
[INFO] NOT adding java-sources to attached artifacts for packaging:
'pom'.
[DEBUG] org.apache.maven.plugins:maven-install-plugin:maven-plugin:2.0
(selected for runtime)
[DEBUG] org.apache.maven:maven-artifact-manager:jar:2.0 (selected for
runtime)
[DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 (selected for
runtime)
[DEBUG
Re: FW: Problem with M2 on Windows Servers - running tests
Have you tried building these same exact projects etc on another system ie Linux, Unix, or Mac OS X? If not, can you please try this, to ensure that your problems are limited to Win32? I would generally expect that your problems are related to the spaces in folder names... C:\Documents And Settings\... D:\Maven 202\... Wayne On 3/22/06, Gest, Stephen B [EMAIL PROTECTED] wrote: -Original Message- From: Gest, Stephen B Sent: Wednesday, March 22, 2006 2:29 PM To: 'users@maven.apache.org' Subject: Problem with M2 on Windows Servers - running tests Hello, Here is additional information regarding the error: Executing mvn -X install gives the following: + Error stacktraces are turned on. [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and Settings\stgest\.m2\plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: 'D:\Maven 2.0.2\conf\plugin-registry.xml' [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] Web Service Framework for CME [INFO] WSF Common [INFO] WSF Provider Interface [INFO] WSF Hibernate Provider [INFO] WSF Model [INFO] WSF Object Server Provider [INFO] WSF Object Server Plugin [INFO] WSF Axis Demo Library [INFO] WSF Service Common [INFO] Axis integration [INFO] WSF Hibernate Demo Web-Application [INFO] WSF Object Server Demo Web-Application [INFO] WSF System Tests Common [INFO] WSF System Tests Hibernate [INFO] WSF System Tests Obs [INFO] WSF System Tests [INFO] [INFO] Building Web Service Framework for CME [INFO]task-segment: [install] [INFO] [DEBUG] maven-site-plugin: resolved to version 2.0-beta-4 from repository central [DEBUG] Retrieving parent-POM from the repository for project: null:maven-site-plugin:maven-plugin:2.0-beta-4 [INFO] Skipping missing optional mojo: org.apache.maven.plugins:maven-site-plugin:attach-descriptor [DEBUG] maven-install-plugin: resolved to version 2.0 from repository central [DEBUG] Retrieving parent-POM from the repository for project: null:maven-install-plugin:maven-plugin:2.0 [DEBUG] maven-compiler-plugin: resolved to version 2.0 from repository central [DEBUG] Retrieving parent-POM from the repository for project: null:maven-compiler-plugin:maven-plugin:2.0 [DEBUG] Retrieving parent-POM from the repository for project: null:maven-surefire-plugin:maven-plugin:2.1.2 [DEBUG] maven-source-plugin: resolved to version 2.0 from repository central [DEBUG] Retrieving parent-POM from the repository for project: null:maven-source-plugin:maven-plugin:2.0 [DEBUG] org.apache.maven.plugins:maven-source-plugin:maven-plugin:2.0 (selected for runtime) [DEBUG] Retrieving parent-POM from the repository for project: null:maven-project:jar:2.0 [DEBUG] org.apache.maven:maven-project:jar:2.0 (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8 (selected for runtime) [DEBUG] classworlds:classworlds:jar:1.1-alpha-2 (selected for runtime) [DEBUG] junit:junit:jar:3.8.1 (selected for runtime) [DEBUG] Retrieving parent-POM from the repository for project: org.apache.maven:maven-artifact:jar:2.0 [DEBUG] org.apache.maven:maven-artifact:jar:2.0 (selected for runtime) [DEBUG] Retrieving parent-POM from the repository for project: org.apache.maven:maven-model:jar:2.0 [DEBUG] org.apache.maven:maven-model:jar:2.0 (selected for runtime) [DEBUG] Retrieving parent-POM from the repository for project: org.apache.maven:maven-artifact-manager:jar:2.0 [DEBUG] org.apache.maven:maven-artifact-manager:jar:2.0 (selected for runtime) [DEBUG] Retrieving parent-POM from the repository for project: org.apache.maven:maven-repository-metadata:jar:2.0 [DEBUG] org.apache.maven:maven-repository-metadata:jar:2.0 (selected for runtime) [DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5 (selected for runtime) [DEBUG] Retrieving parent-POM from the repository for project: null:maven-profile:jar:2.0 [DEBUG] org.apache.maven:maven-profile:jar:2.0 (selected for runtime) [DEBUG] Retrieving parent-POM from the repository for project: org.apache.maven:maven-plugin-api:jar:2.0 [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0 (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-archiver:jar:1.0-alpha-3 (selected for runtime) [DEBUG] classworlds:classworlds:jar:1.1-alpha-2 (selected for runtime) [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-source-plugin:2.0:jar' -- [DEBUG] (f) attach = true [DEBUG] (f) compileSourceRoots = [D:\project\wsf\src\main\java] [DEBUG] (f) finalName = obs-wsf-1.0pre6-SNAPSHOT [DEBUG] (f) outputDirectory = D:\project\wsf\target
RE: FW: Problem with M2 on Windows Servers - running tests
Yes, the same project works successfully on Unix and Linux systems, and also one other Windows system. The project was used in Maven 1.1, with the success, using th same kinds of directory names: C:\Documents And Settings\... D:\Maven 1.1\... Also, if we run mvn install -Dmaven.test.skip=true, then the project builds successfully. I would think that if it were a path issue with spaces, that the compilation would also fail, unless it is specific to the surefire plugin, which was not in Maven 1.1 Stephen -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 22, 2006 3:34 PM To: Maven Users List Subject: Re: FW: Problem with M2 on Windows Servers - running tests Have you tried building these same exact projects etc on another system ie Linux, Unix, or Mac OS X? If not, can you please try this, to ensure that your problems are limited to Win32? I would generally expect that your problems are related to the spaces in folder names... C:\Documents And Settings\... D:\Maven 202\... Wayne On 3/22/06, Gest, Stephen B [EMAIL PROTECTED] wrote: -Original Message- From: Gest, Stephen B Sent: Wednesday, March 22, 2006 2:29 PM To: 'users@maven.apache.org' Subject: Problem with M2 on Windows Servers - running tests Hello, Here is additional information regarding the error: Executing mvn -X install gives the following: + Error stacktraces are turned on. [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and Settings\stgest\.m2\plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: 'D:\Maven 2.0.2\conf\plugin-registry.xml' [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] Web Service Framework for CME [INFO] WSF Common [INFO] WSF Provider Interface [INFO] WSF Hibernate Provider [INFO] WSF Model [INFO] WSF Object Server Provider [INFO] WSF Object Server Plugin [INFO] WSF Axis Demo Library [INFO] WSF Service Common [INFO] Axis integration [INFO] WSF Hibernate Demo Web-Application [INFO] WSF Object Server Demo Web-Application [INFO] WSF System Tests Common [INFO] WSF System Tests Hibernate [INFO] WSF System Tests Obs [INFO] WSF System Tests [INFO] [INFO] Building Web Service Framework for CME [INFO]task-segment: [install] [INFO] [DEBUG] maven-site-plugin: resolved to version 2.0-beta-4 from repository central [DEBUG] Retrieving parent-POM from the repository for project: null:maven-site-plugin:maven-plugin:2.0-beta-4 [INFO] Skipping missing optional mojo: org.apache.maven.plugins:maven-site-plugin:attach-descriptor [DEBUG] maven-install-plugin: resolved to version 2.0 from repository central [DEBUG] Retrieving parent-POM from the repository for project: null:maven-install-plugin:maven-plugin:2.0 [DEBUG] maven-compiler-plugin: resolved to version 2.0 from repository central [DEBUG] Retrieving parent-POM from the repository for project: null:maven-compiler-plugin:maven-plugin:2.0 [DEBUG] Retrieving parent-POM from the repository for project: null:maven-surefire-plugin:maven-plugin:2.1.2 [DEBUG] maven-source-plugin: resolved to version 2.0 from repository central [DEBUG] Retrieving parent-POM from the repository for project: null:maven-source-plugin:maven-plugin:2.0 [DEBUG] org.apache.maven.plugins:maven-source-plugin:maven-plugin:2.0 (selected for runtime) [DEBUG] Retrieving parent-POM from the repository for project: null:maven-project:jar:2.0 [DEBUG] org.apache.maven:maven-project:jar:2.0 (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8 (selected for runtime) [DEBUG] classworlds:classworlds:jar:1.1-alpha-2 (selected for runtime) [DEBUG] junit:junit:jar:3.8.1 (selected for runtime) [DEBUG] Retrieving parent-POM from the repository for project: org.apache.maven:maven-artifact:jar:2.0 [DEBUG] org.apache.maven:maven-artifact:jar:2.0 (selected for runtime) [DEBUG] Retrieving parent-POM from the repository for project: org.apache.maven:maven-model:jar:2.0 [DEBUG] org.apache.maven:maven-model:jar:2.0 (selected for runtime) [DEBUG] Retrieving parent-POM from the repository for project: org.apache.maven:maven-artifact-manager:jar:2.0 [DEBUG] org.apache.maven:maven-artifact-manager:jar:2.0 (selected for runtime) [DEBUG] Retrieving parent-POM from the repository for project: org.apache.maven:maven-repository-metadata:jar:2.0 [DEBUG] org.apache.maven:maven-repository-metadata:jar:2.0 (selected for runtime) [DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5 (selected for runtime) [DEBUG] Retrieving parent-POM from the repository for project: null:maven-profile:jar:2.0
FW: Problem with M2 on Windows Servers - running tests
Hello, This problem is what is reported under SUREFIRE-30. I made the code changes listed to the SurefireBooter class, updated the jar file, and now I am able to successfully run the project tests. Stephen Previous Posting === -Original Message- From: Gest, Stephen B Sent: Wednesday, March 22, 2006 3:26 PM To: 'users@maven.apache.org' Subject: FW: Problem with M2 on Windows Servers - running tests -Original Message- From: Gest, Stephen B Sent: Wednesday, March 22, 2006 2:29 PM To: 'users@maven.apache.org' Subject: Problem with M2 on Windows Servers - running tests Hello, Here is additional information regarding the error: Executing mvn -X install gives the following: + Error stacktraces are turned on. [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and Settings\stgest\.m2\plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: 'D:\Maven 2.0.2\conf\plugin-registry.xml' [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] Web Service Framework for CME [INFO] WSF Common [INFO] WSF Provider Interface [INFO] WSF Hibernate Provider [INFO] WSF Model [INFO] WSF Object Server Provider [INFO] WSF Object Server Plugin [INFO] WSF Axis Demo Library [INFO] WSF Service Common [INFO] Axis integration [INFO] WSF Hibernate Demo Web-Application [INFO] WSF Object Server Demo Web-Application [INFO] WSF System Tests Common [INFO] WSF System Tests Hibernate [INFO] WSF System Tests Obs [INFO] WSF System Tests [INFO] [INFO] Building Web Service Framework for CME [INFO]task-segment: [install] [INFO] [DEBUG] maven-site-plugin: resolved to version 2.0-beta-4 from repository central [DEBUG] Retrieving parent-POM from the repository for project: null:maven-site-plugin:maven-plugin:2.0-beta-4 [INFO] Skipping missing optional mojo: org.apache.maven.plugins:maven-site-plugin:attach-descriptor [DEBUG] maven-install-plugin: resolved to version 2.0 from repository central [DEBUG] Retrieving parent-POM from the repository for project: null:maven-install-plugin:maven-plugin:2.0 [DEBUG] maven-compiler-plugin: resolved to version 2.0 from repository central [DEBUG] Retrieving parent-POM from the repository for project: null:maven-compiler-plugin:maven-plugin:2.0 [DEBUG] Retrieving parent-POM from the repository for project: null:maven-surefire-plugin:maven-plugin:2.1.2 [DEBUG] maven-source-plugin: resolved to version 2.0 from repository central [DEBUG] Retrieving parent-POM from the repository for project: null:maven-source-plugin:maven-plugin:2.0 [DEBUG] org.apache.maven.plugins:maven-source-plugin:maven-plugin:2.0 (selected for runtime) [DEBUG] Retrieving parent-POM from the repository for project: null:maven-project:jar:2.0 [DEBUG] org.apache.maven:maven-project:jar:2.0 (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8 (selected for runtime) [DEBUG] classworlds:classworlds:jar:1.1-alpha-2 (selected for runtime) [DEBUG] junit:junit:jar:3.8.1 (selected for runtime) [DEBUG] Retrieving parent-POM from the repository for project: org.apache.maven:maven-artifact:jar:2.0 [DEBUG] org.apache.maven:maven-artifact:jar:2.0 (selected for runtime) [DEBUG] Retrieving parent-POM from the repository for project: org.apache.maven:maven-model:jar:2.0 [DEBUG] org.apache.maven:maven-model:jar:2.0 (selected for runtime) [DEBUG] Retrieving parent-POM from the repository for project: org.apache.maven:maven-artifact-manager:jar:2.0 [DEBUG] org.apache.maven:maven-artifact-manager:jar:2.0 (selected for runtime) [DEBUG] Retrieving parent-POM from the repository for project: org.apache.maven:maven-repository-metadata:jar:2.0 [DEBUG] org.apache.maven:maven-repository-metadata:jar:2.0 (selected for runtime) [DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5 (selected for runtime) [DEBUG] Retrieving parent-POM from the repository for project: null:maven-profile:jar:2.0 [DEBUG] org.apache.maven:maven-profile:jar:2.0 (selected for runtime) [DEBUG] Retrieving parent-POM from the repository for project: org.apache.maven:maven-plugin-api:jar:2.0 [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0 (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-archiver:jar:1.0-alpha-3 (selected for runtime) [DEBUG] classworlds:classworlds:jar:1.1-alpha-2 (selected for runtime) [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-source-plugin:2.0:jar' -- [DEBUG] (f) attach = true [DEBUG] (f) compileSourceRoots = [D:\project\wsf\src\main\java] [DEBUG] (f) finalName = obs-wsf-1.0pre6-SNAPSHOT [DEBUG] (f) outputDirectory = D:\project\wsf\target [DEBUG] (f) packaging = pom [DEBUG] (f) project
Problem with M2 build
Hi, I'm affraid that there's a problem with m2 build. I checked out m2 from repository, executed m2-bootstrap-all.bat and it failed with the following error: org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the plugin manager executi ng goal 'org.apache.maven.plugins:maven-plugin-plugin:2.0.1-SNAPSHOT:updateRegis try': Unable to find the mojo 'org.apache.maven.plugins:maven-plugin-plugin:2.0.1-SNAPSHOT:updateRegis try' in the plugin 'org.apache.maven.plugins:maven-plugin-plugin' at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default LifecycleExecutor .java:523) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec ycle(DefaultLifec ycleExecutor.java:469) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL ifecycleExecutor. java:448) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle Failures(DefaultL ifecycleExecutor.java:301) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleE xecutor.java:268) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec ycleExecutor.java :137) 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.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.PluginManagerException: Unable to find the mojo 'org.apache.maven .plugins:maven-plugin-plugin:2.0.1-SNAPSHOT:updateRegistry' in the plugin 'org.apache.maven.plugins: maven-plugin-plugin' at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPl uginManager.java: 533) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa nager.java:390) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default LifecycleExecutor .java:519) ... 16 more Caused by: org.codehaus.plexus.component.repository.exception.ComponentLookupExcept ion: Unable to lo okup component 'org.apache.maven.plugin.Mojoorg.apache.maven.plugins:maven-plugin-plugi n:2.0.1-SNAPS HOT:updateRegistry', it could not be created at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer .java:331) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer .java:436) at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPl uginManager.java: 524) ... 18 more Caused by: org.codehaus.plexus.component.factory.ComponentInstantiationException: Could not instanci ate component: role: 'null', implementation: 'org.apache.maven.plugin.plugin.UpdatePluginRegistryMoj o' at org.codehaus.plexus.component.factory.java.JavaComponentFactory.makeExce ption(JavaCompone ntFactory.java:77) at org.codehaus.plexus.component.factory.java.JavaComponentFactory.newInsta nce(JavaComponent Factory.java:54) at org.codehaus.plexus.DefaultPlexusContainer.createComponentInstance(Defau ltPlexusContainer .java:1454) at org.codehaus.plexus.component.manager.AbstractComponentManager.createCom ponentInstance(Ab stractComponentManager.java:93) at org.codehaus.plexus.component.manager.PerLookupComponentManager.getCompo nent(PerLookupCom ponentManager.java:48) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer .java:327) ... 20 more Caused by: java.lang.ClassNotFoundException: org.apache.maven.plugin.plugin.UpdatePluginRegistryMojo at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at org.codehaus.classworlds.RealmClassLoader.loadClassDirect(RealmClassLoad er.java:195) at org.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassRealm.j ava:255) at org.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassRealm.j ava:274) at org.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassRealm.j ava:274) at org.codehaus.plexus.component.factory.java.JavaComponentFactory.newInsta nce(JavaComponent Factory.java:30) ... 24
Re: Problem with M2 build
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 One such failure is normal (yeah, I know it's strange)...but the bootstrap should continue, and the plugin-plugin will be rebuilt along with the rest of maven-plugins in the next step. Do you find that this is not happening? - -j Janecek Jan wrote: | Hi, | | I'm affraid that there's a problem with m2 build. I checked out m2 from | repository, executed m2-bootstrap-all.bat and it failed with the | following error: | | org.apache.maven.lifecycle.LifecycleExecutionException: Internal error | in the plugin manager executi | ng goal | 'org.apache.maven.plugins:maven-plugin-plugin:2.0.1-SNAPSHOT:updateRegis | try': Unable to find | the mojo | 'org.apache.maven.plugins:maven-plugin-plugin:2.0.1-SNAPSHOT:updateRegis | try' in the plugin | 'org.apache.maven.plugins:maven-plugin-plugin' | at | org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default | LifecycleExecutor | .java:523) | at | org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec | ycle(DefaultLifec | ycleExecutor.java:469) | at | org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL | ifecycleExecutor. | java:448) | at | org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle | Failures(DefaultL | ifecycleExecutor.java:301) | at | org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( | DefaultLifecycleE | xecutor.java:268) | at | org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec | ycleExecutor.java | :137) | 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.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.PluginManagerException: Unable to | find the mojo 'org.apache.maven | .plugins:maven-plugin-plugin:2.0.1-SNAPSHOT:updateRegistry' in the | plugin 'org.apache.maven.plugins: | maven-plugin-plugin' | at | org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPl | uginManager.java: | 533) | at | org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa | nager.java:390) | at | org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default | LifecycleExecutor | .java:519) | ... 16 more | Caused by: | org.codehaus.plexus.component.repository.exception.ComponentLookupExcept | ion: Unable to lo | okup component | 'org.apache.maven.plugin.Mojoorg.apache.maven.plugins:maven-plugin-plugi | n:2.0.1-SNAPS | HOT:updateRegistry', it could not be created | at | org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer | .java:331) | at | org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer | .java:436) | at | org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPl | uginManager.java: | 524) | ... 18 more | Caused by: | org.codehaus.plexus.component.factory.ComponentInstantiationException: | Could not instanci | ate component: role: 'null', implementation: | 'org.apache.maven.plugin.plugin.UpdatePluginRegistryMoj | o' | at | org.codehaus.plexus.component.factory.java.JavaComponentFactory.makeExce | ption(JavaCompone | ntFactory.java:77) | at | org.codehaus.plexus.component.factory.java.JavaComponentFactory.newInsta | nce(JavaComponent | Factory.java:54) | at | org.codehaus.plexus.DefaultPlexusContainer.createComponentInstance(Defau | ltPlexusContainer | .java:1454) | at | org.codehaus.plexus.component.manager.AbstractComponentManager.createCom | ponentInstance(Ab | stractComponentManager.java:93) | at | org.codehaus.plexus.component.manager.PerLookupComponentManager.getCompo | nent(PerLookupCom | ponentManager.java:48) | at | org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer | .java:327) | ... 20 more | Caused by: java.lang.ClassNotFoundException: | org.apache.maven.plugin.plugin.UpdatePluginRegistryMojo | | at java.net.URLClassLoader$1.run(URLClassLoader.java:200) | at java.security.AccessController.doPrivileged(Native Method) | at java.net.URLClassLoader.findClass(URLClassLoader.java:188
Problem with M2
Hi,
Hope this is the correct list for M2?
I downloaded the 2.0 release yesterday, but am having some problems
getting it to work - when I try to run a build it bombs out with missing
dependencies on stuff that (I assume) must be plug-in dependencies,
notably some xerces jars, the Servlet 2.4 jar (??!?), and 'tagsoup'. I
can't find these in the M2 repository either. Am I going mad?
A typical session goes:
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO]
[INFO] Building Jepi
[INFO]task-segment: [compile]
[INFO]
[WARNING] POM for: 'commons-io:commons-io:pom:1.0' does not appear to be
valid. Its will be ignored for artifact resolution.
Reason: Failed to validate POM
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
Downloading:
http://repo1.maven.org/maven2/xerces/xmlParserAPIs/2.6.1/xmlParserAPIs-2.6.1.pom
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/servletapi/servlet/2.4/servlet-2.4.pom
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/xerces/xercesImpl/2.2.1/xercesImpl-2.2.1.pom
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/icu4j/icu4j/2.6.1/icu4j-2.6.1.pom
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/tagsoup/tagsoup/0.9.7/tagsoup-0.9.7.pom
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
[WARNING]
Artifact junit:junit:jar:3.8.1 retains local scope 'test'
overriding broader scope 'compile'
given by a dependency. If this is not intended, modify or remove
the local scope.
[WARNING] POM for: 'picocontainer:picocontainer:pom:1.2-beta-1' does not
appear to be valid. Its will be ignored for artifact resolution.
Reason: The POM expression: ${picocontainer.version} could not be
evaluated. Reason:
picocontainer:picocontainer:jar:${picocontainer.version} references itself.
[WARNING] POM for: 'nanocontainer:nanocontainer:pom:1.0-RC-1' does not
appear to be valid. Its will be ignored for artifact resolution.
Reason: The POM expression: ${nanocontainer.version} could not be
evaluated. Reason:
nanocontainer:nanocontainer:jar:${nanocontainer.version} references itself.
Downloading:
http://repo1.maven.org/maven2/log4j/log4j/1.2.6/log4j-1.2.6.jar
342K downloaded
Downloading:
http://repo1.maven.org/maven2/commons-collections/commons-collections/2.1/commons-collections-2.1.jar
161K downloaded
Downloading:
http://repo1.maven.org/maven2/xerces/xerces/2.2.1/xerces-2.2.1.jar
815K downloaded
Downloading:
http://repo1.maven.org/maven2/servletapi/servlet/2.4/servlet-2.4.jar
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
GroupId: servletapi
ArtifactId: servlet
Version: 2.4
Reason: Unable to download the artifact from any repository
servletapi:servlet:2.4:jar
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
[INFO]
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Unable to download
the artifact from any repository
servletapi:servlet:2.4:jar
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:528)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:469)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:448)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:301)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:268)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:137)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
Re: Problem with M2
Sun jars like servletapi and jta are not in central repo...
you should download them from sun website and install in your repo using
install:install-file.
The download of artifacts is not sorted in any way so each run, you
download of artifacts is different. The build will download artifacts
until it reaches the sun jar and then fails.
Ross Bamford wrote:
Hi,
Hope this is the correct list for M2?
I downloaded the 2.0 release yesterday, but am having some problems
getting it to work - when I try to run a build it bombs out with
missing dependencies on stuff that (I assume) must be plug-in
dependencies, notably some xerces jars, the Servlet 2.4 jar (??!?),
and 'tagsoup'. I can't find these in the M2 repository either. Am I
going mad?
A typical session goes:
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO]
[INFO] Building Jepi
[INFO]task-segment: [compile]
[INFO]
[WARNING] POM for: 'commons-io:commons-io:pom:1.0' does not appear to
be valid. Its will be ignored for artifact resolution.
Reason: Failed to validate POM
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
Downloading:
http://repo1.maven.org/maven2/xerces/xmlParserAPIs/2.6.1/xmlParserAPIs-2.6.1.pom
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/servletapi/servlet/2.4/servlet-2.4.pom
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/xerces/xercesImpl/2.2.1/xercesImpl-2.2.1.pom
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/icu4j/icu4j/2.6.1/icu4j-2.6.1.pom
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/tagsoup/tagsoup/0.9.7/tagsoup-0.9.7.pom
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
[WARNING]
Artifact junit:junit:jar:3.8.1 retains local scope 'test'
overriding broader scope 'compile'
given by a dependency. If this is not intended, modify or
remove the local scope.
[WARNING] POM for: 'picocontainer:picocontainer:pom:1.2-beta-1' does
not appear to be valid. Its will be ignored for artifact resolution.
Reason: The POM expression: ${picocontainer.version} could not be
evaluated. Reason:
picocontainer:picocontainer:jar:${picocontainer.version} references
itself.
[WARNING] POM for: 'nanocontainer:nanocontainer:pom:1.0-RC-1' does
not appear to be valid. Its will be ignored for artifact resolution.
Reason: The POM expression: ${nanocontainer.version} could not be
evaluated. Reason:
nanocontainer:nanocontainer:jar:${nanocontainer.version} references
itself.
Downloading:
http://repo1.maven.org/maven2/log4j/log4j/1.2.6/log4j-1.2.6.jar
342K downloaded
Downloading:
http://repo1.maven.org/maven2/commons-collections/commons-collections/2.1/commons-collections-2.1.jar
161K downloaded
Downloading:
http://repo1.maven.org/maven2/xerces/xerces/2.2.1/xerces-2.2.1.jar
815K downloaded
Downloading:
http://repo1.maven.org/maven2/servletapi/servlet/2.4/servlet-2.4.jar
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
GroupId: servletapi
ArtifactId: servlet
Version: 2.4
Reason: Unable to download the artifact from any repository
servletapi:servlet:2.4:jar
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
[INFO]
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Unable to
download the artifact from any repository
servletapi:servlet:2.4:jar
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:528)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:469)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:448)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:301)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:268)
at
Re: Problem with M2
(apologies if this post is duped - I sent from incorrect address first
time and it didn't come up)
On Fri, 21 Oct 2005 10:19:00 +0100, Edwin Punzalan [EMAIL PROTECTED]
wrote:
Sun jars like servletapi and jta are not in central repo...
you should download them from sun website and install in your repo using
install:install-file.
Thanks for your help! My project doesn't use Servlet API of any
description, so it must be a plugin dep. In that case it looks like
someone's fd up somewhere, because Servlet 2.3 _is_ distributed (I
assume so - it's in my M2 repo already). Maybe someone's updated their
plugin to Servlets 2.4 and not told anyone?
Anyway, I've done as you suggested (actually just got it from M1 on
ibiblio), but the other Jars I mentioned are
now stopping the build. The session is pretty much exactly as below,
except that the fatal error now mentions icu4j:icu4j:2.6.1:jar
The download of artifacts is not sorted in any way so each run, you
download of artifacts is different. The build will download artifacts
until it reaches the sun jar and then fails.
I see. Makes sense :)
Thanks again,
Ross
Ross Bamford wrote:
Hi,
Hope this is the correct list for M2?
I downloaded the 2.0 release yesterday, but am having some problems
getting it to work - when I try to run a build it bombs out with
missing dependencies on stuff that (I assume) must be plug-in
dependencies, notably some xerces jars, the Servlet 2.4 jar (??!?),
and 'tagsoup'. I can't find these in the M2 repository either. Am I
going mad?
A typical session goes:
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO]
[INFO] Building Jepi
[INFO]task-segment: [compile]
[INFO]
[WARNING] POM for: 'commons-io:commons-io:pom:1.0' does not appear to
be valid. Its will be ignored for artifact resolution.
Reason: Failed to validate POM
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
Downloading:
http://repo1.maven.org/maven2/xerces/xmlParserAPIs/2.6.1/xmlParserAPIs-2.6.1.pom
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/servletapi/servlet/2.4/servlet-2.4.pom
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/xerces/xercesImpl/2.2.1/xercesImpl-2.2.1.pom
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/icu4j/icu4j/2.6.1/icu4j-2.6.1.pom
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/tagsoup/tagsoup/0.9.7/tagsoup-0.9.7.pom
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
[WARNING]
Artifact junit:junit:jar:3.8.1 retains local scope 'test'
overriding broader scope 'compile'
given by a dependency. If this is not intended, modify or
remove the local scope.
[WARNING] POM for: 'picocontainer:picocontainer:pom:1.2-beta-1' does
not appear to be valid. Its will be ignored for artifact resolution.
Reason: The POM expression: ${picocontainer.version} could not be
evaluated. Reason:
picocontainer:picocontainer:jar:${picocontainer.version} references
itself.
[WARNING] POM for: 'nanocontainer:nanocontainer:pom:1.0-RC-1' does not
appear to be valid. Its will be ignored for artifact resolution.
Reason: The POM expression: ${nanocontainer.version} could not be
evaluated. Reason:
nanocontainer:nanocontainer:jar:${nanocontainer.version} references
itself.
Downloading:
http://repo1.maven.org/maven2/log4j/log4j/1.2.6/log4j-1.2.6.jar
342K downloaded
Downloading:
http://repo1.maven.org/maven2/commons-collections/commons-collections/2.1/commons-collections-2.1.jar
161K downloaded
Downloading:
http://repo1.maven.org/maven2/xerces/xerces/2.2.1/xerces-2.2.1.jar
815K downloaded
Downloading:
http://repo1.maven.org/maven2/servletapi/servlet/2.4/servlet-2.4.jar
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
GroupId: servletapi
ArtifactId: servlet
Version: 2.4
Reason: Unable to download the artifact from any repository
servletapi:servlet:2.4:jar
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
[INFO]
[INFO] Trace
Re: Problem with M2
On Fri, 21 Oct 2005 10:19:00 +0100, Edwin Punzalan [EMAIL PROTECTED]
wrote:
Sun jars like servletapi and jta are not in central repo...
you should download them from sun website and install in your repo using
install:install-file.
My project doesn't use Servlet API of any description, so it must be a
plugin dep. In that case it looks like someone's fd up somewhere,
because Servlet 2.3 _is_ distributed (I assume so - it's in my M2 repo
already). Maybe someone's updated their plugin to Servlets 2.4 and not
told anyone?
In any event, I've done as you suggested (actually just got it from M1 on
ibiblio), but the other Jars I mentioned are now stopping the build. The
session is exactly as below, except that the fatal error now mentions
icu4j:icu4j:2.6.1:jar
The download of artifacts is not sorted in any way so each run, you
download of artifacts is different. The build will download artifacts
until it reaches the sun jar and then fails.
Ross Bamford wrote:
Hi,
Hope this is the correct list for M2?
I downloaded the 2.0 release yesterday, but am having some problems
getting it to work - when I try to run a build it bombs out with
missing dependencies on stuff that (I assume) must be plug-in
dependencies, notably some xerces jars, the Servlet 2.4 jar (??!?),
and 'tagsoup'. I can't find these in the M2 repository either. Am I
going mad?
A typical session goes:
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO]
[INFO] Building Jepi
[INFO]task-segment: [compile]
[INFO]
[WARNING] POM for: 'commons-io:commons-io:pom:1.0' does not appear to
be valid. Its will be ignored for artifact resolution.
Reason: Failed to validate POM
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
Downloading:
http://repo1.maven.org/maven2/xerces/xmlParserAPIs/2.6.1/xmlParserAPIs-2.6.1.pom
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/servletapi/servlet/2.4/servlet-2.4.pom
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/xerces/xercesImpl/2.2.1/xercesImpl-2.2.1.pom
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/icu4j/icu4j/2.6.1/icu4j-2.6.1.pom
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/tagsoup/tagsoup/0.9.7/tagsoup-0.9.7.pom
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
[WARNING]
Artifact junit:junit:jar:3.8.1 retains local scope 'test'
overriding broader scope 'compile'
given by a dependency. If this is not intended, modify or
remove the local scope.
[WARNING] POM for: 'picocontainer:picocontainer:pom:1.2-beta-1' does
not appear to be valid. Its will be ignored for artifact resolution.
Reason: The POM expression: ${picocontainer.version} could not be
evaluated. Reason:
picocontainer:picocontainer:jar:${picocontainer.version} references
itself.
[WARNING] POM for: 'nanocontainer:nanocontainer:pom:1.0-RC-1' does not
appear to be valid. Its will be ignored for artifact resolution.
Reason: The POM expression: ${nanocontainer.version} could not be
evaluated. Reason:
nanocontainer:nanocontainer:jar:${nanocontainer.version} references
itself.
Downloading:
http://repo1.maven.org/maven2/log4j/log4j/1.2.6/log4j-1.2.6.jar
342K downloaded
Downloading:
http://repo1.maven.org/maven2/commons-collections/commons-collections/2.1/commons-collections-2.1.jar
161K downloaded
Downloading:
http://repo1.maven.org/maven2/xerces/xerces/2.2.1/xerces-2.2.1.jar
815K downloaded
Downloading:
http://repo1.maven.org/maven2/servletapi/servlet/2.4/servlet-2.4.jar
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
GroupId: servletapi
ArtifactId: servlet
Version: 2.4
Reason: Unable to download the artifact from any repository
servletapi:servlet:2.4:jar
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
[INFO]
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Unable to
download the artifact from any repository
servletapi:servlet:2.4:jar
from the specified remote repositories:
central
Re: Problem with M2
H
icu4j is not in central repo... the name could be incorrect or the
developers have not given their artifacts yet.
Ross Bamford wrote:
On Fri, 21 Oct 2005 10:19:00 +0100, Edwin Punzalan
[EMAIL PROTECTED] wrote:
Sun jars like servletapi and jta are not in central repo...
you should download them from sun website and install in your repo
using install:install-file.
My project doesn't use Servlet API of any description, so it must be
a plugin dep. In that case it looks like someone's fd up
somewhere, because Servlet 2.3 _is_ distributed (I assume so - it's
in my M2 repo already). Maybe someone's updated their plugin to
Servlets 2.4 and not told anyone?
In any event, I've done as you suggested (actually just got it from M1
on ibiblio), but the other Jars I mentioned are now stopping the
build. The session is exactly as below, except that the fatal error
now mentions icu4j:icu4j:2.6.1:jar
The download of artifacts is not sorted in any way so each run, you
download of artifacts is different. The build will download
artifacts until it reaches the sun jar and then fails.
Ross Bamford wrote:
Hi,
Hope this is the correct list for M2?
I downloaded the 2.0 release yesterday, but am having some
problems getting it to work - when I try to run a build it bombs
out with missing dependencies on stuff that (I assume) must be
plug-in dependencies, notably some xerces jars, the Servlet 2.4
jar (??!?), and 'tagsoup'. I can't find these in the M2 repository
either. Am I going mad?
A typical session goes:
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO]
[INFO] Building Jepi
[INFO]task-segment: [compile]
[INFO]
[WARNING] POM for: 'commons-io:commons-io:pom:1.0' does not appear
to be valid. Its will be ignored for artifact resolution.
Reason: Failed to validate POM
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
Downloading:
http://repo1.maven.org/maven2/xerces/xmlParserAPIs/2.6.1/xmlParserAPIs-2.6.1.pom
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/servletapi/servlet/2.4/servlet-2.4.pom
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/xerces/xercesImpl/2.2.1/xercesImpl-2.2.1.pom
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/icu4j/icu4j/2.6.1/icu4j-2.6.1.pom
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/tagsoup/tagsoup/0.9.7/tagsoup-0.9.7.pom
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
[WARNING]
Artifact junit:junit:jar:3.8.1 retains local scope 'test'
overriding broader scope 'compile'
given by a dependency. If this is not intended, modify or
remove the local scope.
[WARNING] POM for: 'picocontainer:picocontainer:pom:1.2-beta-1'
does not appear to be valid. Its will be ignored for artifact
resolution.
Reason: The POM expression: ${picocontainer.version} could not be
evaluated. Reason:
picocontainer:picocontainer:jar:${picocontainer.version} references
itself.
[WARNING] POM for: 'nanocontainer:nanocontainer:pom:1.0-RC-1' does
not appear to be valid. Its will be ignored for artifact resolution.
Reason: The POM expression: ${nanocontainer.version} could not be
evaluated. Reason:
nanocontainer:nanocontainer:jar:${nanocontainer.version} references
itself.
Downloading:
http://repo1.maven.org/maven2/log4j/log4j/1.2.6/log4j-1.2.6.jar
342K downloaded
Downloading:
http://repo1.maven.org/maven2/commons-collections/commons-collections/2.1/commons-collections-2.1.jar
161K downloaded
Downloading:
http://repo1.maven.org/maven2/xerces/xerces/2.2.1/xerces-2.2.1.jar
815K downloaded
Downloading:
http://repo1.maven.org/maven2/servletapi/servlet/2.4/servlet-2.4.jar
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
GroupId: servletapi
ArtifactId: servlet
Version: 2.4
Reason: Unable to download the artifact from any repository
servletapi:servlet:2.4:jar
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
[INFO]
[INFO] Trace
Re: Problem with M2
On Fri, 21 Oct 2005 11:28:50 +0100, Edwin Punzalan [EMAIL PROTECTED]
wrote:
H
icu4j is not in central repo... the name could be incorrect or the
developers have not given their artifacts yet.
That's what I guessed. So the question is - is everyone who installs M2 on
a fresh machine seeing the same thing?
Can anyone suggest a workaround, short of manually finding and installing
the missing jars? Should I wait for the repo to be updated? Can I not use
the M1 repo with M2? I could do with getting it going because we want to
look into a M2 version of the Java.net plugin, and I have next week free.
Ross Bamford wrote:
On Fri, 21 Oct 2005 10:19:00 +0100, Edwin Punzalan
[EMAIL PROTECTED] wrote:
Sun jars like servletapi and jta are not in central repo...
you should download them from sun website and install in your repo
using install:install-file.
My project doesn't use Servlet API of any description, so it must be a
plugin dep. In that case it looks like someone's fd up somewhere,
because Servlet 2.3 _is_ distributed (I assume so - it's in my M2 repo
already). Maybe someone's updated their plugin to Servlets 2.4 and not
told anyone?
In any event, I've done as you suggested (actually just got it from M1
on ibiblio), but the other Jars I mentioned are now stopping the
build. The session is exactly as below, except that the fatal error
now mentions icu4j:icu4j:2.6.1:jar
The download of artifacts is not sorted in any way so each run, you
download of artifacts is different. The build will download
artifacts until it reaches the sun jar and then fails.
Ross Bamford wrote:
Hi,
Hope this is the correct list for M2?
I downloaded the 2.0 release yesterday, but am having some problems
getting it to work - when I try to run a build it bombs out with
missing dependencies on stuff that (I assume) must be plug-in
dependencies, notably some xerces jars, the Servlet 2.4 jar (??!?),
and 'tagsoup'. I can't find these in the M2 repository either. Am I
going mad?
A typical session goes:
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO]
[INFO] Building Jepi
[INFO]task-segment: [compile]
[INFO]
[WARNING] POM for: 'commons-io:commons-io:pom:1.0' does not appear
to be valid. Its will be ignored for artifact resolution.
Reason: Failed to validate POM
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
Downloading:
http://repo1.maven.org/maven2/xerces/xmlParserAPIs/2.6.1/xmlParserAPIs-2.6.1.pom
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/servletapi/servlet/2.4/servlet-2.4.pom
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/xerces/xercesImpl/2.2.1/xercesImpl-2.2.1.pom
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/icu4j/icu4j/2.6.1/icu4j-2.6.1.pom
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/tagsoup/tagsoup/0.9.7/tagsoup-0.9.7.pom
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
[WARNING]
Artifact junit:junit:jar:3.8.1 retains local scope 'test'
overriding broader scope 'compile'
given by a dependency. If this is not intended, modify or
remove the local scope.
[WARNING] POM for: 'picocontainer:picocontainer:pom:1.2-beta-1' does
not appear to be valid. Its will be ignored for artifact resolution.
Reason: The POM expression: ${picocontainer.version} could not be
evaluated. Reason:
picocontainer:picocontainer:jar:${picocontainer.version} references
itself.
[WARNING] POM for: 'nanocontainer:nanocontainer:pom:1.0-RC-1' does
not appear to be valid. Its will be ignored for artifact resolution.
Reason: The POM expression: ${nanocontainer.version} could not be
evaluated. Reason:
nanocontainer:nanocontainer:jar:${nanocontainer.version} references
itself.
Downloading:
http://repo1.maven.org/maven2/log4j/log4j/1.2.6/log4j-1.2.6.jar
342K downloaded
Downloading:
http://repo1.maven.org/maven2/commons-collections/commons-collections/2.1/commons-collections-2.1.jar
161K downloaded
Downloading:
http://repo1.maven.org/maven2/xerces/xerces/2.2.1/xerces-2.2.1.jar
815K downloaded
Downloading:
http://repo1.maven.org/maven2/servletapi/servlet/2.4/servlet-2.4.jar
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
[INFO]
Re: Problem with M2
On Fri, 21 Oct 2005 11:42:22 +0100, Ross Bamford [EMAIL PROTECTED] wrote: Can anyone suggest a workaround, short of manually finding and installing the missing jars? Okay I think I found what I need now in the docs, and I can manually do the remainder. I wasn't fully appreciating the impact of transitive dependencies - still thinking Maven 1 :) Thanks again, Ross -- Ross Bamford - [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem with m2 clean:clean package
You must upgrade to the Maven 2.0 RC build. - Brett On 10/15/05, Bill Siggelkow [EMAIL PROTECTED] wrote: I am new user of Maven 2 (and have only dabbled with Maven 1). I was following the instructions from the getting started page and ran into the following error when I tried to run 'm2 clean:clean package' on the webapp archetype I created. I am using the maven-2.0-beta-3. Here's the stack trace ... Exception in thread main java.lang.NoSuchMethodError: org.codehaus.plexus.util.FileUtils.getDefaultExcludesAsList()Ljava/ util/List; at org.apache.maven.plugin.war.AbstractWarMojo.getExcludes (AbstractWarMojo.java:157) at org.apache.maven.plugin.war.AbstractWarMojo.getWarFiles (AbstractWarMojo.java:310) at org.apache.maven.plugin.war.AbstractWarMojo.copyResources (AbstractWarMojo.java:227) at org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp (AbstractWarMojo.java:196) at org.apache.maven.plugin.war.WarMojo.performPackaging (WarMojo.java:108) at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:86) at org.apache.maven.plugin.DefaultPluginManager.executeMojo (DefaultPluginManager.java:417) This would seem to be from an incorrect jar for Plexus. Any help would be appreciated. -Bill Siggelkow - 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]
Problem with m2 clean:clean package
I am new user of Maven 2 (and have only dabbled with Maven 1). I was following the instructions from the getting started page and ran into the following error when I tried to run 'm2 clean:clean package' on the webapp archetype I created. I am using the maven-2.0-beta-3. Here's the stack trace ... Exception in thread main java.lang.NoSuchMethodError: org.codehaus.plexus.util.FileUtils.getDefaultExcludesAsList()Ljava/ util/List; at org.apache.maven.plugin.war.AbstractWarMojo.getExcludes (AbstractWarMojo.java:157) at org.apache.maven.plugin.war.AbstractWarMojo.getWarFiles (AbstractWarMojo.java:310) at org.apache.maven.plugin.war.AbstractWarMojo.copyResources (AbstractWarMojo.java:227) at org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp (AbstractWarMojo.java:196) at org.apache.maven.plugin.war.WarMojo.performPackaging (WarMojo.java:108) at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:86) at org.apache.maven.plugin.DefaultPluginManager.executeMojo (DefaultPluginManager.java:417) This would seem to be from an incorrect jar for Plexus. Any help would be appreciated. -Bill Siggelkow - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
