Re: Parent POM across projects

Hi Mark, I have read through all conversations within this thread and it still looks like we still have to go to each individual project to modify the version number when parent pom updates its version. I have posted the exact same question in a separate thread

RE: Parent POM across projects

Hi Mark, Mark Chaimungkalanont wrote on Wednesday, June 14, 2006 10:26 AM: Guys Gals, I think I'm missing something fairly fundamental here. I have a setup where there's a parent project, atlassian-base with some common settings on it. This project has many sub-projects which declares

Re: Parent POM across projects

Jörg, Thanks for the reply! So what is the difference between: versionSNAPSHOT/version and versionlatest/version Basically I've been naming the atlassian-base snapshots as: 1.1-SNAPSHOT 1.2-SNAPSHOT etc. and so whenever I rev atlassian-base, I need to change all the child projects as

Re: Parent POM across projects

I think people here use the release plugin and it takes care of those tedious jobs for you. I haven't used it though. Mark Chaimungkalanont wrote: Jörg, Thanks for the reply! So what is the difference between: versionSNAPSHOT/version and versionlatest/version Basically I've been

RE: Parent POM across projects

Edwin Punzalan wrote on Wednesday, June 14, 2006 11:00 AM: I think people here use the release plugin and it takes care of those tedious jobs for you. No, this works only if your parent POM is part of your project. In case of a company wide super POM, this does not apply. I haven't used it

RE: Parent POM across projects

Hi Mark, Mark Chaimungkalanont wrote on Wednesday, June 14, 2006 10:54 AM: Jörg, Thanks for the reply! So what is the difference between: versionSNAPSHOT/version and versionlatest/version Basically I've been naming the atlassian-base snapshots as: 1.1-SNAPSHOT

RE: Parent POM across projects

Jörg Schaible wrote on Wednesday, June 14, 2006 11:30 AM: Mark Chaimungkalanont wrote on Wednesday, June 14, 2006 10:54 AM: I'm thinking this *should* be a fairly common use-case, and wondered what other solutions there are. Not that I don't understand your pain: MRELEASE-96 - Jörg

RE: Parent POM across projects and versions of dependencies

need to change the version 50 times!!! Best regards, Juri. -Original Message- From: Jorg Schaible [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 12:30 PM To: Maven Users List Subject: RE: Parent POM across projects Hi Mark, Mark Chaimungkalanont wrote

Re: Parent POM across projects and versions of dependencies

: Wednesday, June 14, 2006 12:30 PM To: Maven Users List Subject: RE: Parent POM across projects Hi Mark, Mark Chaimungkalanont wrote on Wednesday, June 14, 2006 10:54 AM: Jörg, Thanks for the reply! So what is the difference between: versionSNAPSHOT/version and versionlatest/version

RE: Parent POM across projects and versions of dependencies

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

Jörg, Thanks a ton for the info, really appreciate it. I guess I'll stick to using SNAPSHOT as the parent POM's version then. From your comment at http://jira.codehaus.org/browse/MRELEASE-96, it seems that we were dealing with exactly the same dilemma! Thanks again! Mark C Jörg Schaible