t makes it
> possible to checkin the current settings.xml and the full build log when
> doing a release. Just to get the full trace of a build.
>
>
> Thank you all again for your answers!
> Cheers,
> Oskar
>
>
>
> --
attern-to-setup-common-organization-specific-data-in-single-pom--tp26723137p26739437.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional c
There are also solutions with a maven plugin downloading and installing
settings.xml. Such a plugin is included in Nexus Pro, but it shouldn't be
too hard to write yourself (or is there an oss version already?).
/Anders
On Thu, Dec 10, 2009 at 16:35, Wayne Fay wrote:
> > One way is to define a
> 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.
I've heard of
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
