On Wed, Jan 28, 2009 at 8:16 AM, Richard Rodseth <[email protected]> wrote:
> I didn't realize profiles were the place for this. Are the ${} properties
> here and in the flex-mojos samples passed in as -D options on the CI build
> plan?
The profile is passed in (-Prelease) but the ${} options are defined
in the properties section of the parent pom. We don't do custom builds
for different sdks (except flexcover, see below), but when we upgrade
a version, it's easier to put the version in a single property and use
the ${} variables everywhere else so you don't have search/replace
bugs in your build.
Profiles are useful any time you want to override a few settings, but
leave the rest the same. In this case, for development builds (the
default profile), we have debug and verbose stack traces on, and we
only build 2 of our 11 languages (to save time).
When we release to production we want all 11 languages and debug and
stack traces off. So we use profiles to handle that.
For example, right now we define these profiles:
automation (adds all the automation swcs to the build path)
allLocales (builds all 11 locales)
release (see above)
flexcover (switches the flex sdk property to point to our custom flexcover sdk)
So to do an automation build with all locales, we do
-Pautomation,allLocales or when a developer is testing a locale on his
box, he'll pass -PallLocales on the command line to get all locales
instead of the default 2, etc.
HTH,
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/
-~----------~----~----~----~------~----~------~--~---
