Hi,
> When been over this several times on this list. You have to extract
> the configuration out of the binary. You mustn't have a Maven build
> that could generate different flavors of an artifact. Which one would
> you deploy to the repository?
Ok, this was a bit misleading by me. With "flavo
> We're having lots of projects building at least one EAR, and each EAR is
> deployed to the same application server(s), but in different flavors:
> developer (snapshot) build, integration build and/or release build. Using
> a CI server configured with special jobs doing these deployment tasks
> wo
Hi,
> > I'm using profiles at work for the sole purpose of deciding what to do
> > with the build artifact, i.e. activating different deployment targets
> > (application servers) for an EAR.
>
> I see this as a completely different task where you're simply using
> Maven as a utility tool. When us
