Jared,
I've used the solution mentioned by Brett on large projects and it works
well. I also place a project.xml and project.properties in the Maven cvs/svn
module that holds configuration data common to all applications on a
project. Applications then extend this project-level pom with <extends>${
maven.home}/project.xml</extends>
I would be interested to hear how this issue is being addressed with M2. One
solution would be to have a small M2 core that is used to bootstrap your
project's POM, which extends a POM located on a web server. E.g. <extends>
http://mylocalserver/projectX/project.xml</extends> I believe this is a
feature request that has already been submitted for M1 but I am not sure how
this would work for associated project.properties files. With M2 this should
become simpler as all configuration data is stored in the POM. Please
correct me if I am wrong.
Thomas
On 8/22/05, Buntingster <[EMAIL PROTECTED]> wrote:
>
> 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]
>
>
