Scenario: (all projects mentioned below are fictitious.. blah blah)
I am working on jFnord, an open source project with at least three other active developers. I am the primary developer of FnordJMX, which depends on the SNAPSHOT version of SpicyJMX. I go on a three week holiday for Christmas. SpicyJMX developers release a few new SNAPSHOTs. The other jFnord developers try to work on the CVS version, and it fails to build.
In this case, I think resolving snapshots is the best course of action.
-- Ryan Hoegg ISIS Networks http://www.isisnetworks.net
Sonnek, Ryan wrote:
Understood. I think that this plugin is strictly for developers use on
their local respository, and any files on the remote repository must be
handled with great care.
Although, I personally question the usefulness of having multiple archived
snapshots on the remote repository. If you are developing an application
with a SNAPSHOT dependency, you are essentially on the bleeding edge anyways
and putting yourself at risk of suffering changes from the other project
(versus waiting for a stable release). I honestly don't see when you would
want to use the "resolve-snapshots" goal to change from a SNAPSHOT release
to a TIMESTAMPED release. IMO, you should be using the snapshot OR an
official release.
Ryan
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
