Does using the parent tag require the project to be in a repository?
I planned on having this "suitepom" accessible via CVS but not
something that is going to be installed in our company repo. I may be
way off base though.
Also, how would you pass something through like a version? The
version tag is required in the child pom so you can't leave it out,
and if I do ${version} it doesn't pick that up from the definition in
the master pom, it just uses "${version}" literally.
On May 2, 2007, at 5:17 PM, Wayne Fay wrote:
Put the shared properties in profiles in the parent pom, include the
children as <modules/> in the parent pom, and use the parent tag in
the children to share properties with all your poms.
Or is there a specific reason this is not sufficient?
Wayne
On 5/2/07, Jared Blitzstein <[EMAIL PROTECTED]> wrote:
I have 5 projects that I want to build as a suite. I created a
multi-
module to do this and it's fine out of the box for just calling the
sub projects. But I need to be able to set variables in the multi-
module to pass in like the version, profile, and some other basic
things. But I also need to make sure each of these projects can live
on their own. I've read http://www.sonatype.com/book/pom-
relationships.html as well as the getting-started on mavens website
but they don't speak to what I'm trying to do. Can anyone point me in
the right direction?
---------------------------------------------------------------------
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]
