Ok that makes sense. IMO, then since the sandbox parent is a snaphot and prevents accidental releases to ibiblio, then it doesn't hurt in some cases to have sandbox plugins be non-snapshot. It should be encouraged that they work this way, but not a requirement, it is after all, just a sandbox.
-----Original Message----- From: jerome lacoste [mailto:[EMAIL PROTECTED] Sent: Thursday, January 19, 2006 1:28 PM To: [email protected] Subject: Re: [mojo-dev] Re: [mojo-scm] [1276] trunk/mojo/mojo-sandbox/runtime-maven-plugin: fixed missing SNAPSHOT revs On 1/19/06, Brian E. Fox <[EMAIL PROTECTED]> wrote: > I'm not sure if it's an official policy or not, but it's how it was > explained to me when I added my plugins to the sandbox. You should > still be able to depend on the snapshot revisions without problems > though unless I'm missing something. If you have a non snapshot > revision, you still need to install it because it won't be deployed to ibiblio, right? Yes but I still use a repos on the LAN. But if I have plugin B depending on A, if I modify A in an incompatible way, I can deploy it to my LAN repository without affecting the others. If I use a single 1.0-SNAPSHOT version for both A & B, it gets picked up and break my plugin B. J
