"...But at the same time I would never want another department to break my build by deploying a snapshot I'm not ready for. "
IMHO, I think our approach excels in making sure this doesn't happen. First and foremost, if this version range issue can be fixed, snapshots will never be considered valid unless explicitly asked for. Therefore snapshot deploys will never be a problem for me. Currently I can't even release because snapshots are not filtered out. "... Did we not start this whole discussion because you wanted artifact resolution to not work transparently with snapshots? i.e. you have to explicitly mention snapshots in the ranges as defined the original maven2 dependency spec." Yes exactly, if I don't explicitly mention a snapshot on either end of an inclusive version range I don't want snapshots to be part of my build. "...BTW snapshots are not filtered/faulted by the release plugin when defined in ranges, it would appear to work on the defined not resolved dependencies... you have to use the enforcer plugin which works on the resolved tree." Hum, not sure. I briefly looked at the enforcer plugin and it didn't seem like it was something that should be required use here; i.e. to fix this issue. In summary, I think your process and mine are similar yet different. Similar in that we have lots of projects and internal dependencies and we want projects to 'automatically' use later versions. Different in that I move all the 'bad releases' to snapshots which essentially go away when not needed anymore. I vote we fix this issue such that version ranges work for both of us (and others), if this requires a command line option (or something) that is fine with me. BTW, our CI server does clean deploys on all SVN checkins; releases never occur unless we push the release button. Michael McCallum-3 wrote: > > All fair comments. We don't release documentation for each release. > site-deploys are independent. And we have perhaps fewer people. > > But at the same time I would never want another department to break my > build > by deploying a snapshot I'm not ready for. > > Quite possibly we could make more use of snapshots. Did we not start this > whole discussion because you wanted artifact resolution to not work > transparently with snapshots? i.e. you have to explicitly mention > snapshots > in the ranges as defined the original maven2 dependency spec. > > BTW snapshots are not filtered/faulted by the release plugin when defined > in > ranges, it would appear to work on the defined not resolved > dependencies... > you have to use the enforcer plugin which works on the resolved tree. > > cheers > > -- > Michael McCallum > Enterprise Engineer > mailto:[EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Version-ranges-and-snapshots-tp11464715s177p14689271.html Sent from the Maven Developers mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
