..or my favorite: Change to the Maven Way(tm)! What you're doing is not, IMHO, the correct way. I guess you're not doing Maven deploys to a remote repo as you would end up with different flavors of a project's artifact? Which can't happen as releases mustn't change.
What you should do is to either separate each customer build with a classifier (one project for all customers) or one project for each customer. In the latter case you would build the "standard" artifact in one project and then do some kind of overlay in the Maven projects producing the customer artifacts. /Anders On Thu, Nov 11, 2010 at 07:56, Wayne Fay <wayne...@gmail.com> wrote: > > and copy them in as part of the hudson build. I guess we could put the > > settings.xml file for the hudson user in to source control, but having > all > > of that information from across all of our projects in one place is far > from > > Well, it seems like you have a few options... > > 1. One big settings.xml file > 2. Lots of settings.xml files and use -s parameter to mvn to pick the > right one to use > 3. Move all profiles to various pom.xml files > 4. Merge or rewrite the old code so Maven3 works with profiles.xml files > 5. Stick with Maven2 indefinitely > > There are probably other options I haven't considered as well. > > Wayne > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
