Hi Baptiste, Baptiste MATHUS wrote:
> 2010/12/16 Jörg Schaible <[email protected]> > >> Hi Baptiste, >> >> Baptiste MATHUS wrote: >> >> > But then how do you handle releases of the referencing projects? A >> > clean release must never reference any snapshot, I don't see how you do >> > it. >> >> Hmm, Jörg Hohwiller pointed out that *he* does not release those >> artifacts. So is this a question to my reply in the original thread? >> > > True, I guess I mixed the Jörgs, sorry ;-). > The question stays valid though, but it might not be the exact same > problem as yours. The company POM defined all versions of plugins and artifacts in management sections. If a component/project has to be released, it will set the versions of all required SNAPSHOT dependencies in the company POM to the final version, release the company pom (e.g. version 200 and setting again SNAPSHOT as next version), release the dependencies and the component/project using that version of the company POM as parent. Note, the dependencyManagement of the company POM can contain all kind of SNAPSHOT versions as long as they are not used in the release process. After the release and a new deployment of the company POM, all projects that depend on the SNAPSHOT of the company POM will use automatically the new released stuff (if they depend on it). - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
