> > 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?
Sorry...this might have sounded more exciting than it actually is. It's pretty low-tech right now. I've essentially got the entire Maven distribution in a SourceSafe folder. Before running a build, the latest changes to this folder are retrieved (in case of plugin additions/changes). During the Maven build process, it apparently checks the timestamp on the files in the plugin directory of the distribution and updates the user's plugin cache, so it provides the automatic updating for me. I'd certainly rather see it automatically pull any plugin changes from my in-house repository as I could then ensure that new plugins are retrieved without the user having to update the build folder. However, I don't want it going out on the internet to retrieve any of these files... > 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. Any way to make it automatically download the latest? Or would that be a snapshot? -- Sean T. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
