Hi Wendy, On Mon, 2008-03-24 at 13:19 -0700, Wendy Smoak wrote: > On Mon, Mar 24, 2008 at 1:16 PM, buzzterrier <[EMAIL PROTECTED]> wrote: > > > Thx for the reply. I did define a custom pom, that declared the > > dependencies, e.g. > ... > > but when I deploy this pom to the internal repository the dependencies are > > stripped out and I am left with: > > What command did you use? > > My guess is that you left out -DpomFile=... and you're getting the > automatically generated pom. > > http://maven.apache.org/plugins/maven-install-plugin/install-file-mojo.html >
I've tried it, and that works too. However it seems a very odd UI for the deploy plugin. The "file" property is mandatory, so when deploying just a POM, doesn't it make sense to set -Dfile to point to the pom.xml, and -Dpackaging=pom? And when doing that, it then seems very odd to have to set the optional -DpomFile parameter. In fact, I would bet that maven then scps the pom file twice; once as the "deployed file" and once as the "deployed pom". Not fatal, but definitely odd. Wouldn't it make more sense to disable generatePom when -Dpackaging=pom is set? Regards, Simon --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
