Someone before suggested making a sort of internal release. Along those lines, I do the following:
1. Add my own distributionManagement info to the pom.xml, overriding the default info from Apache. This way I can deploy it easily to our internal repository with 'mvn deploy'. 2. Change the version from x.x-SNAPSHOT to x.x-<subversion#> (also from the earlier suggestion). Now you don't have to worry about snapshot versions and repositories, just refer to it with the explicit version number like you would any other plugin. If you can get your other dependencies from your internal repository okay, you should have no problem getting to this one. Chris Hilton > -----Original Message----- > From: Doug Douglass [mailto:[EMAIL PROTECTED] > Sent: Thursday, 08 June, 2006 14:37 > To: Maven Users List > Subject: working with custom-built org.apache.maven.plugins > > I'm struggling with an issue regarding custom-built versions > of maven plugins in the org.apache.maven.plugins groupId. > Specifically, I've built a custom 2.1-SNAPSHOT version of > maven-pmd-plugin that includes > http://jira.codehaus.org/browse/MPMD-33. The plugin builds, > installs and runs correctly (on any machine that has done > 'mvn install'). > > The problems arise when trying to deploy to our corporate > snapshot repo so the plugin version can be accessed by other > developers and our CI machines: > > 1. I haven't found a way to deploy directly via 'mvn > deploy'. Maven honors the POM distributionManagement, which > attempts to deploy to the official Apache snapshot repository. > > 2. Using 'mvn deploy:deploy-file -D...' to deploy the > plugin works, in that the POM and JAR are deployed, but maven > fails to use them as the POM has a '-1' suffix to the > version, while the JAR has a '-2' suffix. Renaming the files > manually in the repository might fix this, but I can't be > sure due to.... > > 3. Maven appears to only attempt to download > org.apache.maven.pluginsfrom the "central" repo (we use a mirror of > ibiblio) and never searches our > corp repo even though our corp/parent POM has it listed as a > pluginRepository with snapshots set to true. > > > So, how are people handling these problems: > > Would adding our corp. repo as a mirror of "central" fix #3? > Should this be necessary? > > What about deployment? It seems like either > deploy:deploy-file is broken (I doubt this as we use it all > the time for 3rd party stuff, but maybe broken when using > SNAPSHOTs) or that deploy:deploy should have the same > repositoryId and url parameters as deploy-file added to it. > > All thoughts are appreciated. > > Doug > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
