Hello? I wonder if there is any pattern in Maven defining how to setup common organization specific data. What I mean is that I only want to define my distribution management in one place, I only want to setup specific deploy paths in one place etc., etc.
One way is to define a lot of properties in a settings.xml - but then the user has to define all these properties himself. When properties are changing, then we have a mess. Even worse, there is no version tracking of properties using this solution. That is not good enough. One other way would be to use a global parent. Going that way it is possible to inherit all common data. But the disadvantage is that I cannot change the values without updating the same version of the parent in the repository (because Maven does not manage to resolve version ranges for the parent pom). So, is there any other suggestions? Can I import the data using version scopes. I like to be able to define exact versions of what I include in my builds but when it comes to build/deploy specific data, then I would like to be able to change this for all users in one place. Any advice to solve this problem is really appreciated! Cheers, Oskar -- View this message in context: http://old.nabble.com/Pattern-to-setup-common-organization-specific-data-in-single-pom--tp26723137p26723137.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
