[Logo]
Forums Register Login
Properties to replace version numbers
I am in a team of 2.
in my previous company when using maven every major library had a version number in the parent POM, and these variables were used in every other POM.
My co-worker thinks this is a waste of time.

Can you either help me convince him i am right, or explain why you think I am wrong.

as an example

Don't know, but welcome to the Ranch

Are you the same Wendy Gibbons who used to be active a long time ago?
I like this way myself, but I do think it can be a bit overkill. At work we use it mostly for libraries that are prone to regular updates (like the ones we write ourselves), and for sets of libraries like Jackson.

So I'd say this is just personal preference, and there is no right answer.
As soon as you need more than one dependency entry in your pom for the same library then keeping the version as a property makes sense. Otherwise it comes down to convention and team preference. Do it one way, or do it the other way, but try not to do it both ways.
 

Campbell Ritchie wrote:Don't know, but welcome to the Ranch

Are you the same Wendy Gibbons who used to be active a long time ago?



yes, but I don't have access to that email anymore, so can't reset the password.
 

Tim Cooke wrote:Do it one way, or do it the other way, but try not to do it both ways.



You are right, that is a very good point. I will ponder on that

This thread has been viewed 262 times.

All times above are in ranch (not your local) time.
The current ranch time is
Oct 17, 2018 07:57:56.