Weird pom in snapshots

[adrian.brock]

I just did a snapshot and its totally screwed up
http://snapshots.jboss.org/maven2/org/jboss/microcontainer/jboss-kernel/2.0.0-SNAPSHOT/jboss-kernel-2.0.0-20080320.221228-112.pom

At least I think it was me, maybe somebody else is playing?

What does this wagondev stuff mean/imply?

[pgier]

Sorry, that was me again. I seem to have the touch of destruction lately :(
I'm trying to deploy the snapshot-temp version of mc now. Is that in the REFACTORING branch?

[adrian.brock]

"pgier" wrote:
Sorry, that was me again. I seem to have the touch of destruction lately :(
I'm trying to deploy the snapshot-temp version of mc now. Is that in the REFACTORING branch?

No, I was going to update your branch once I had the proper releases.
Saves me figuring out how to do a mvn release manually. ;-)

[adrian.brock]

I've redone the snapshots looks a lot better now:-)
http://snapshots.jboss.org/maven2/org/jboss/microcontainer/jboss-kernel/2.0.0-SNAPSHOT/jboss-kernel-2.0.0-20080320.230503-113.pom

[pgier]

"pgier" wrote:
Sorry, that was me again. I seem to have the touch of destruction lately :(
I'm trying to deploy the snapshot-temp version of mc now. Is that in the REFACTORING branch?

No, I was going to update your branch once I had the proper releases.
Saves me figuring out how to do a mvn release manually. ;-)

Which branch do you mean? The maven-thirdpary one? If you just update trunk it would be better for me. Then I'll just create a new branch off that one to continue with the thirdparty stuff.

[adrian.brock]

"pgier" wrote:

"pgier" wrote:
Sorry, that was me again. I seem to have the touch of destruction lately :(
I'm trying to deploy the snapshot-temp version of mc now. Is that in the REFACTORING branch?

No, I was going to update your branch once I had the proper releases.
Saves me figuring out how to do a mvn release manually. ;-)

Which branch do you mean? The maven-thirdpary one? If you just update trunk it would be better for me. Then I'll just create a new branch off that one to continue with the thirdparty stuff.

Ok, saves me some work then. ;-)

[adrian.brock]

I've found a different problem.

How does it work out which snapshot is the latest?

I've got a problem where it should be using snapshot 144
http://snapshots.jboss.org/maven2/org/jboss/microcontainer/jboss-dependency/2.0.0-SNAPSHOT/jboss-dependency-2.0.0-20080320.225014-144.pom
but its actually using snapshot 143 from 4 minutes earlier (but note the time part of the id is before the snapshot number)
http://snapshots.jboss.org/maven2/org/jboss/microcontainer/jboss-dependency/2.0.0-SNAPSHOT/jboss-dependency-2.0.0-20080320.230503-143.pom

[adrian.brock]

Bizarrely, after doing another snapshot we now have two #144 ;-)

[pgier]

I've found a different problem.

How does it work out which snapshot is the latest?

I've got a problem where it should be using snapshot 144
http://snapshots.jboss.org/maven2/org/jboss/microcontainer/jboss-dependency/2.0.0-SNAPSHOT/jboss-dependency-2.0.0-20080320.225014-144.pom
but its actually using snapshot 143 from 4 minutes earlier (but note the time part of the id is before the snapshot number)
http://snapshots.jboss.org/maven2/org/jboss/microcontainer/jboss-dependency/2.0.0-SNAPSHOT/jboss-dependency-2.0.0-20080320.230503-143.pom

Maven looks at the metadata file it says which one is the latest. I think I was trying to deploy at the same time as you, so that's how there ended up with some incorrect metadata.