>
>
> Yes, so you create a parent pom with common settings, and the pom for
> each individual project has it's libs and dependencies. If there are a
> few libs that all Flex projects use, you can put them in the parent
> pom if you like.


Yup, that's what I've got now, and eliminating all the duplication was a
beautiful thing.

>
> All artifacts that are dependencies of another project should be in
> there, as well as any that are distributed. An aggregator pom doesn't
> need to be in there, but any parent pom should.


Yes, at this time my libs are not used by others, but they *could* be. Until
they are, I'm happy to have an aggregator for my SWF.


> > For the moment I'm leaning towards <relativePath> in the <parent> tag.
>
> I'm not sure what this buys you, and it does tie you to a particular
> file system layout (projects are not independently buildable unless
> the relative parent pom is also in the repo). Sometimes though, it can
> yield some flexibility.
>
>
The relative parent will be in the subversion repo (in the parent directory,
alongside the aggregate pom). I think the only thing it buys me is not
having to merge the concepts of parent and aggregator.  I admit to
wavering...

But if the aggregator doubles as super-pom, it too needs to be in the
subversion repository, or the nexus/artifactory repository.

If the two are kept separate, I can at any time upload the super pom to the
Nexus/Artifactory repository and point other teams/projects at it. Or let
them copy it without being confused by the project-specific modules. On the
other hande the modules portion is pretty trivial. Like I said, I admit to
wavering...

--~--~---------~--~----~------------~-------~--~----~
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/
-~----------~----~----~----~------~----~------~--~---

Reply via email to