Installing new artifacts in production environment

Hello!

That's the situation: we've got a production environment where we run Maven to deploy new applications in a WebSphere (among other things: reporting,etc), but it's quite often that we install new versions of our plugins and archetypes (). My questions are two:

1º We are defining a process for installing this kind of changes, and creating a script for it. Is there any matter we should take in to account? For example, anything about concurrency - you know, a project could be asking for a plugin while this plugin is being replaced.

2º About installing a plugin or archetype with a bug fixed, would you recomend me to install archetypes and plugins that have new code with the same version number in order to avoid changing the version in every project's pom or is it better to keep the same version number and let the projects have old versions until somebody change their pom's?

Thank you very much.

You are asking about installing the artifacts into WebSphere, is that right? You are not asking about installing artifacts into the Maven repository, is that right? If my assumptions are correct, this question is better asked in the WebSphere forum, in which case I will move it.

No. I'm talking about installing artifacts into the Maven repository keeping in mind there may be many user accessing the same system to use Maven (same artifacts I'm installing).

But furhter, some of the tasks Maven may be doing at any time is to deploy projects in this machine's WebSphere, which should be taken into account as far as someone could install a plugin overwriting another one that's deploying an app in WebSphere at the same time. These are the matters I'm trying to deal with.

Thank you very much.