> 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: [email protected] For additional commands, e-mail: [email protected]
