> I've successfully setup an in-house remote repository along > with a central Maven distribution provided via our source > control system. At this time, I can update a jar in the > maven distribution's plugin folder, and then when someone > runs a build, they'll get the latest version installed if > they don't have it.
How does this work? > I've been trying to follow the changes > going on with regard to the separation of the plugins from > the core and auto-downloading of plugins from multiple > locations. In this new scheme, is there a way I can still > control the downloading of plugins (to only pull from our > in-house repository, for example)? > The plugin changes mean two things: firstly you can enforce a plugin version per projeect by specifying a dependency. That will be retrieved from the repository in the same way as any other versioned artifact. Secondly, you have a goal to help download and install manually: plugin:download. The downside of plugin:download is that it doesn't clear out every user's local plugin cache, so they end up with multiple versions when they change. The recent code changes I've made that are currently uncommitted will only load the plugins present in $MAVEN_HOME, regardless of what versions are in the cache (although it stil extracts them to the local cache). - Brett
