Just so this is on the mailing list so others can benefit from my
research I plan on trying to use this:
http://mojo.codehaus.org/properties-maven-plugin/usage.html
If it does not work, I will write a plugin that does what I need to
allow me to pull properties from an external file. Persona
On Thu, Nov 11, 2010 at 8:29 AM, Anders Hammar wrote:
> Change to the Maven Way(tm)!
That clearly depends on how you define this term. Personally, I don't
see any contradiction between Maven's approach and profile files. In
contrary, I am quite unhappy that they are gone. They have been
incredib
Thanks for the tips Wayne and Anders.
I think I have two main options:
1. Use mvn -s with a settings.xml for each config I need. I didn't
know this option existed, so thanks for the pointer Wayne. This lets
me basically treat my settings.xml as my profiles.xml file.
2. Modify our build
..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
> 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.x
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
> 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 setti
Hi,
I am trying to upgrade a maven 2.x build system to a maven 3.x build
system and have run in to a problem with the fact that profiles.xml is
no longer supported. Our current build iconfigures the built .ear
file based on build properties supplied in profiles.xml. These
properties are
