[EMAIL PROTECTED] schrieb:
Apologies. I was incorrect.
The real issue is that I have a parent POM that contains this plugin (and
the others), and even though the packaging of that parent is pom, it still
seems to want to invoke the execute methods of its contained plugins.
This, of course is another issue, specifically how does one have an
"abstract" parent pom.
<build><plugins> is for actually attaching plugins to the build
lifecycle. If you just want to define common configuration (version,
executions, ...) for a plugin use <pluginManagement>.
I gather, based on a Nabble search, that it
involves profiles in some manner. So I'll just wait on it for now.
Thanks again for the help
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?
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.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
