On Wed, Oct 20, 2010 at 8:12 AM, Michael McCallum <[email protected]> wrote: > You could try something like... > > mvn -s special-settings-file.xml verify install
haha. Hudson has a horrible bug involving -s that the maintainers keep claiming to fix and failing to fix. Perhaps some day. > > set that up for the jobs in hudson that should share snapshots... > > and for the others > > mvn verify > > So you end up with two sets of jobs > * those the build the head of an artifact against the heads of the others > * those that build the head of an artifact against the latest releases of the > others (assuming you use ranges of course) > > cheers > > Michael > > On Wednesday 20 October 2010 00:25:33 Benson Margulies wrote: >> If you are using 'downstream', how do you avoid the need to publish to >> at least a common local repo? >> >> I've been facing the following variation on this: >> >> I do not want to publish snapshots to nexus, since they mess up people >> who download stale ones into their development process. >> >> I do want to split a hudson build into multiple jobs with dependencies. >> >> Short of an extra repo in nexus that is used only for intra-hudson >> snapshots, I haven't thought of anything. Have you? >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
