Wendy Smoak-3 wrote:
>
> On Tue, Aug 26, 2008 at 6:31 AM, Sven Vlieghe <[EMAIL PROTECTED]>
> wrote:
>
>> I am trying to centralize the version-numbers of all
>> projects/dependencies
>> in our system. My approach for this, is to centralize the
>> settings.xml-file
>> & add all versions as profile-properties. This worked perfectly at first
>> sight, but resulted in errors when trying to use the project as a
>> dependency.
> ...
>> Anyone sees what I'm doing wrong?
>
> The settings.xml file is intended for developer-specific
> configuration... the version number of a project definitely belongs in
> the pom.
>
> You can establish an organization-level pom that all your projects
> inherit from and specify things that are truly common across all your
> projects there, then come down to project-level parent poms for things
> that are project-specific, etc.
>
> --
> Wendy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
I agree, that was a setup I was originally planning to do. However, each
time a dependency-version increases, this would result in having to increase
the base-pom too. That pom would have to be released to a final version, and
all existing projects would have to update their reference to it.
Sven
--
View this message in context:
http://www.nabble.com/Resolving-dependency-properties-tp19162134p19163185.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]
