J�rg, > I still don't get, where the problem is. If you wanna have a dependency on > the timestamped version, set the content of the version tag in the POM to the > > timestamp.
Well ... I don't want a dependency on a timestamp, that's the whole point. Let me explain. If have a module named ABC which is used by other modules. We currently support version 1.1.x and version 2.0.x of the module, located in two different CVS branches. Teams are currently working on the 1.1.5 and 2.0.7 releases which are also used by other teams. If I do jar:inststall-snapshot of ABC, I have the following : - ABC-SNAPSHOT.jar -> Doh, is it a snapshot of 1.1.x or 2.0.x ??? - ABC-2004-02-05... -> fine but I don't want to change my dependency every time the team deploys a new snapshot, I want to retrieve it automaticaly (that is what this SNAPSHOT thing is all about, right?) So here's why having 1.1.5-SNAPSHOT and 2.0.7-SNAPSHOT is a good thing (BTW, this problem prevents us currently to use the install-snapshot functionnalty so +1 for the feature request). As a workaround, we set the version to 1.1.5-SNAPSHOT and 2.0.7-SNAPSHOT respectively and we use the jar:install goal. Cheers, St�phane --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
