We are looking at standardizing our builds on Maven. We will have one
server performing builds for our "official" artifacts. However, all of
our developers will also need to be able to build locally for their own
purposes. We will be setting up an internal repository for our
libraries, and we will also have need to write several custom plugins
for some of our business requirements.
We will initially be using maven 1 - while we are definitely considering
maven 2, politics do not allow us to use an unreleased project, and we
are in desperate need of the dependency management features provided by
maven. So, hopefully my solution (at least conceptually) can be applied
to both maven 1 and maven 2.
My question is this: is there any good way to be sure that my developers
are running in the same maven environment as our build server? By this
I mean primarily the plugins (and their versions) that are installed.
This becomes especially critical when we have internal plugins that will
be modified on a more frequent basis.
My current thought is to publish the info available in "maven -i" on a
central web server, and then write a custom plugin (update-maven-env)
that our developers can run that will retrieve this information and
retrieve and update the appropriate plugins.
I was wondering if anyone has any thoughts on this, if there is already
a solution out there? Any assistance would be greatly appreciated.
Thanks.
-Jared
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
