because downstream is the trigger, the build checks everything out and uses an uber-aggregator build so that all the artifacts will be in the reactor which is how "mvn verify" can work (no need for clean because I do a clean checkout for every build)
On 19 October 2010 12:25, Benson Margulies <[email protected]> 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]
