Yeah, I see the problem - getBaseVersion isn't returning the -SNAPSHOT,
but the timestamped one. Will fix, but the timestamps are lined up now.
BTW, you can use both repositories - you don't need to remove the
codehaus one for cobertura.
- Brett
Gordon Henriksen wrote:
Snapshot 20060501.153032-1 works. Thanks!
On May 1, 2006, at 10:56 AM, Gordon Henriksen wrote:
On May 1, 2006, at 4:57 AM, Brett Porter wrote:
Make sure you are using cvs.apache.org/maven-snapshot-repository as a
snapshot repository, not snapshots.maven.codehaus.org.
That's how the test project was configured. My live project also
includes codehaus.org for Cobertura support. However, I'll sacrifice
Cobertura for TestNG at the moment.
I blew away my local repository just to make sure there wasn't any
overlap.
Try again now (I've upgraded to the release version of test NG).
No improvement. I still get to the same point of failure—just that I
don't have to manually deploy TestNG to get there, now. The missing
surefire-testng snapshot now at 2.0-20060501.085606-5. That isn't
coming from
http://cvs.apache.org/maven-snapshot-repository/org/apache/maven/surefire/surefire-testng/2.0-SNAPSHOT/maven-metadata.xml:
<?xml version="1.0" encoding="UTF-8"?><metadata>
<groupId>org.apache.maven.surefire</groupId>
<artifactId>surefire-testng</artifactId>
<version>2.0-SNAPSHOT</version>
<versioning>
<snapshot>
<timestamp>20060501.085606</timestamp>
<buildNumber>3</buildNumber>
</snapshot>
<lastUpdated>20060501085948</lastUpdated>
</versioning>
</metadata>
Note the discrepency; mvn wants build number 5, but the testng
provider is only at build 3. When I grep my repository for the
timestamp and build 5…
$ cd ~/.m2/repository
$ grep -rl 2.0-20060501.085606-5 *
org/apache/maven/surefire/surefire-api/2.0-SNAPSHOT/surefire-api-2.0-20060501.085606-5.pom
org/apache/maven/surefire/surefire-api/2.0-SNAPSHOT/surefire-api-2.0-SNAPSHOT.pom
org/apache/maven/surefire/surefire-booter/2.0-SNAPSHOT/surefire-booter-2.0-20060501.085606-5.pom
org/apache/maven/surefire/surefire-booter/2.0-SNAPSHOT/surefire-booter-2.0-SNAPSHOT.pom
Is surefire-api or surefire-booter trying to load a matching revision
of the surefire-testng provider at runtime…? Sorry if that's nonsense;
I just don't see where this version number is originating, since it's
not obvious to me how it could be derived from the Maven dependency
graph.
— G
— G
---------------------------------------------------------------------
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]
