RE: Parent POM across projects and versions of dependencies

2006-06-14 Thread Jörg Schaible
Hi Juri, Artamonov, Juri wrote on Wednesday, June 14, 2006 12:02 PM: >> So either use a static version like 1.1 or bite the bullet. > This is why we use SNAPSHOT only, because the version of the > master POM is absolutely moot. If we release, we will have to > change SNAPSHOT to the next >release

Re: Parent POM across projects and versions of dependencies

2006-06-14 Thread Edwin Punzalan
Well, to minimize it, you can at least use the dependencyManagement section inside a parent pom. Artamonov, Juri wrote: So either use a static version like 1.1 or bite the bullet. This is why we use SNAPSHOT only, because the version of the master POM is absolutely moot. If we release, we w

RE: Parent POM across projects and versions of dependencies

2006-06-14 Thread Artamonov, Juri
>So either use a static version like 1.1 or bite the bullet. This is why we use >SNAPSHOT only, because the version of the master POM is absolutely moot. If we >release, we will have to change SNAPSHOT to the next >release version (e.g. >"42") in all POMs of that are part of the release For me