On Wed, Jan 28, 2009 at 9:11 AM, Richard Rodseth <[email protected]> wrote: > Thanks, that does help. I am still using the flex-mojos super pom from its > public location. Would I copy it (or inherit from it) and upload my own > super-pom manually to Artifactory? Do you have a different super-pom for > libraries vs applications? At this time, I have several libraries, but none > are re-deployed to the Artifactory repository. I have a "master" pom that > uses the <modules> tag, and the individual libraries/apps have dependencies > on the libraries they need.
We don't use the flex-mojos super-pom because our organization mandates that we use theirs, so we have a parent/root pom for all of the flex projects in our group that extends the org's super-pom. In that pom we have all of our flex settings, and then our library and application poms inherit from that same root flex pom. We've copied all the relevant settings from the flex-mojos super-pom into our root flex pom, and it does get put in our Nexus repository. You can still inherit the flex-mojos super-pom and declare your own properties to override the sdk versions and stuff. Any time I've put a version number or a setting in more than one place, I tend to make a property for it to avoid them getting out of synch, but it doesn't happen too often--we have 3 properties in our root pom (flex sdk version, flex-mojos version, and an internal property). 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/ -~----------~----~----~----~------~----~------~--~---
