Search the forum for "profile".
You will see people in all kinds of difficulty and dead-ends caused by
trying to use profiles.
There are (apparently) some actual uses for profiles but far more cases
of misuse.
We have never used profiles but from watching the forum for 4+years, my
advice is to get your builds working well without profiles and then see
if there is an opportunity for optimization with profiles.
Profiles are processed at a certain point in the maven build process so
there are things that you can not do with them.
Maven supports a certain build philosophy and will defeat anyone who
tries to go against this.
Try to go down the simplest road and let Maven do its thing.
Version ranges are another bad idea. There is no reason not to pick a
version of a dependency. You are only going to have 1 version at
run-time anyway and it might as well be one that you pick and have tested.
If you search the forum, you will find problems and silliness caused by
the use of version ranges.
I hope that this helps.
Ron
On 16/03/2012 1:18 PM, [email protected] wrote:
Not good.
Dependency versions should be deterministic. For the same reason avoid
version ranges.
That's pretty definitive, and I think I agree on a gut level. Can you
articulate any specific issues? I'd appreciate it if you could.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
Ron Wheeler
President
Artifact Software Inc
email: [email protected]
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
