well, damn...
thank you Nick.
I finally found the source of my error: some problems in my Artifactory
configuration.

everything seems to be fine now.


Nick Stolwijk-3 wrote:
> 
> In which remote repository are you looking? As fas as I can see 
> classworlds:clasworlds:jar:1.1.-alpha-2 still exists [1] as does the 
> other one [2]
> 
> Hth,
> 
> Nick Stolwijk
> 
> [1] http://repo1.maven.org/maven2/classworlds/classworlds/1.1-alpha-2/
> [2] 
> http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-container-default/1.0-alpha-8/
> 
> nodje nodje wrote:
>> i'm probably the nth guy to ask this, but I'm totally  new to maven and
>> barely understand it:
>>
>> i cannot 'mvn test', I get:
>>
>> [INFO] Error to resolving surefire provider dependency: Missing:
>> ----------
>> 1) classworlds:classworlds:jar:1.1-alpha-2
>>
>>   Try downloading the file manually from the project website.
>>
>>   Then, install it using the command:
>>       mvn install:install-file -DgroupId=classworlds
>> -DartifactId=classworlds \
>>           -Dversion=1.1-alpha-2 -Dpackaging=jar -Dfile=/path/to/file
>> Alternatively, if you host your own repository you can deploy the file
>> there:       mvn deploy:deploy-file -DgroupId=classworlds
>> -DartifactId=classworlds \
>>           -Dversion=1.1-alpha-2 -Dpackaging=jar -Dfile=/path/to/file \
>>            -Durl=[url] -DrepositoryId=[id]
>>
>>   Path to dependency:
>>         1) dummy:dummy:jar:1.0
>>         2) org.apache.maven.surefire:surefire-booter:jar:2.3
>>         3) org.codehaus.plexus:plexus-archiver:jar:1.0-alpha-7
>>         4) org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8
>>         5) classworlds:classworlds:jar:1.1-alpha-2
>>
>> 2) org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8
>>
>>   Try downloading the file manually from the project website.
>>
>>   Then, install it using the command:
>>       mvn install:install-file -DgroupId=org.codehaus.plexus
>> -DartifactId=plexus-container-default \
>>           -Dversion=1.0-alpha-8 -Dpackaging=jar -Dfile=/path/to/file
>> Alternatively, if you host your own repository you can deploy the file
>> there:       mvn deploy:deploy-file -DgroupId=org.codehaus.plexus
>> -DartifactId=plexus-container-default \
>>           -Dversion=1.0-alpha-8 -Dpackaging=jar -Dfile=/path/to/file \
>>            -Durl=[url] -DrepositoryId=[id]
>>
>>   Path to dependency:
>>         1) dummy:dummy:jar:1.0
>>         2) org.apache.maven.surefire:surefire-booter:jar:2.3
>>         3) org.codehaus.plexus:plexus-archiver:jar:1.0-alpha-7
>>         4) org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8
>>
>> Fair enough, I've been looking for them myself. These versions don't
>> exist
>> yet or anymore: classworks only have a 1.1-alpha2-NO_SYSTEM_EXIT and
>> plexus-container-default alphas gose from v9 to v32.
>>
>> What the hell? Isn't this the most basic lyfecycle step of maven? How
>> come
>> this is not working? Am I entitled to modify the POMs myself?
>> I'm probably missing the point somewhere but this is this just a very
>> hard
>> to start with maven...
>>
>> thanks for any help!
>>   
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/mvn-test-%3A-surefire-dependency-problem-tf4473898s177.html#a12772282
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Reply via email to