my.group.id
> some-project
>
>
>
>
> This build fails.. maven doesn't resolve the properties in 'some-project'
> (in this case, version.test) & therefore tries to find
> my.group.id:test-program:${version.test} ins
On Wed, Aug 27, 2008 at 12:24 AM, Sven Vlieghe <[EMAIL PROTECTED]> wrote:
> That I could, however we have this policy that we cannot have snapshot
> dependencies on released projects. I'll verify if this is the same for
> snapshot parents. If so, the snapshot parent will be the way to go.
You'll
ue, you're more
than welcome!
Sven Vlieghe
--
View this message in context:
http://www.nabble.com/Resolving-dependency-properties-tp19162134p19175944.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]
On Tue, Aug 26, 2008 at 10:30 AM, Sven Vlieghe <[EMAIL PROTECTED]>wrote:
> 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 ver
gt;
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
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 f
hanks in advance,
Sven
--
View this message in context:
http://www.nabble.com/Resolving-dependency-properties-tp19162134p19162134.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [
