On 09/09/2010, at 9:23 PM, Benjamin Bentmann wrote: > Brett Porter wrote: > >> - Deployment by Maven 3 clients will also make it only consumable with Maven >> 3 clients. > > I can't follow, I just rechecked and the new metadata is parsed by Maven > 2.0.10+ and allows it to resolve SNAPSHOTs deployed by Maven 3.
Sorry, I edited and moved the context away without re-reading. If you follow a process such as: 1) deploy -bin.tar.gz 1.4-SNAPSHOT 2) deploy -bin.zip 1.4-SNAPSHOT At this point, the first is version, say, 1.4-20100909.032808-1-bin.tar.gz and the second 1.4-20100909.080603-2-bin.zip. There's potentially a POM for both, or just the first depending on how you did it. The main snapshot information reads 20100909.080603-2. Maven 2 will be unable to resolve the originally deployed classifier because of the mismatched timestamp. That's actually the same result that Maven 2 users get now if they try this - but the person deploying with Maven 3 may not realise the solution that works for them won't work for Maven 2 users they have, in potentially confusing ways. The same would go for any tool that assumes they need to be the same, or those that expect the timestamps of POMs and current artifacts to line up. My gut says that the snapshot version should be the same, but it has catches and after thinking through it your solution makes more sense to me. I just wanted to walk through it in case you had additional thoughts to share or if anyone caught another edge case. As we know, once the metadata is there we have to support it for some time :) - Brett -- Brett Porter [email protected] http://brettporter.wordpress.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
