I figured it out. I included a <build></build> section in one of my parent
poms as a way of setting the different properties controlling the build of
the plugins.
<project>
...
<build>
<directory>${buildtools.custom.dir}/build/${project.name}</directory>
<sourceDirectory>${buildtools.plugin.dir}/${project.name}</sourceDirectory>
<outputDirectory>${buildtools.custom.dir}/build/${project.name}</outputDirectory>
</build>
...
</project>
Replacing that section with these three properties fixed it for all of my
plugins
<properties>
<build.directory>${buildtools.custom.dir}/build/${project.name}</build.directory>
<build.sourceDirectory>${buildtools.plugin.dir}/${project.name}</build.sourceDirectory>
<build.outputDirectory>${buildtools.custom.dir}/build/${project.name}</build.outputDirectory>
</properties>
Is this "expected" behavior or have I stumbled across a previously untried
combination of elements?
Thanks
Robert Egan
"Wendy Smoak" <[EMAIL PROTECTED]> wrote on 10/04/2007 02:59:29 PM:
> On 10/4/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]>
wrote:
>
> > How does one go about calling mvn install for packaging type
maven-plugin
> > without actually executing the plugin?
>
> Just 'mvn install' should work... I'm curious what makes you think
otherwise?
>
> --
> Wendy
>
This email message and any attachments may contain confidential,
proprietary or non-public information. The information is intended solely
for the designated recipient(s). If an addressing or transmission error
has misdirected this email, please notify the sender immediately and
destroy this email. Any review, dissemination, use or reliance upon this
information by unintended recipients is prohibited. Any opinions
expressed in this email are those of the author personally.
