Sorry, I guess I didn't explain. The configuration settings need to
be version controlled and the hudson server runs the builds for the
whole company.
As it stands now, we pull the profiles.xml files from a different svn
repo 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 ideal.
-Scott
On Nov 10, 2010, at 7:57 PM, Wayne Fay wrote:
want this information added in to our pom directly. Modifying
settings.xml
in a hudson build seems like a bad idea, since then if multiple
hudson
builds are run at once, they would impact eachother.
I don't understand this comment. You should be able to copy all your
profiles into one settings.xml file and then use various activation
options to turn one or another on for a given build.
http://maven.apache.org/settings.html
Wayne
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
