There's parent in the sense of a pom having a <parent> tag.
<parent>
<groupId>info.flex-mojos</groupId>
<artifactId>flex-super-pom</artifactId>
<version>2.0.3</version>
</parent>
And then there's the <modules> tag.
<modules>
<module>Lib1</module>
<module>Lib2</module>
<module>App</module>
</modules>
Presumably if I have a profile in the pom containing <modules>, its settings
will only apply if I build from that pom. In other words, if I want to be
able to build each artifact independently but still have project-wide
settings, I would need to have a custom parent pom, loaded into
Nexus/Artifactory. I assume that's just a matter of using the repository gui
to upload a pom file (which could contain nothing more that a profile and a
<parent> as above) and giving it the type "pom". Am I on the right track?
On Fri, Feb 13, 2009 at 5:25 AM, Logan Allred <[email protected]> wrote:
>
> On Mon, Feb 9, 2009 at 3:08 PM, Richard Rodseth <[email protected]>
> wrote:
> > Yes, thanks. So the -f option does the trick.
> >
> > However, it seems to me that one should strive to have each artifact
> > buildable from within its own directory, which would suggest putting
> default
> > settings in a parent pom (in Nexus/Artifactory) rather than in the
> > root/master pom. Agree?
>
> Sorry, the -f is just a shortcut for:
> cd components/libraryA
> mvn install
>
> All of our modules are independently buildable without the parent (as
> long as the parent is in the local repo).
>
> Logan
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Flex Mojos" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/flex-mojos?hl=en?hl=en
http://blog.flex-mojos.info/
-~----------~----~----~----~------~----~------~--~---
