You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by ro...@aciworldwide.com on 2007/10/04 20:52:00 UTC
Build plugin without using it
How does one go about calling mvn install for packaging type maven-plugin
without actually executing the plugin?
I only want to install it. I want others to actually use it.
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.
Re: Build plugin without using it
Posted by Gisbert Amm <gi...@webde.de>.
robert.egan@aciworldwide.com wrote:
> Tim Kettler <ti...@udo.edu> wrote on 10/05/2007 01:41:33 AM:
>
>><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>.
>>
>
> That puts a new spin on things and simplifies my life quite a bit. Why
> isn't this essential tidbit mentioned on any of the plugin how-to pages,
> or did I just miss it?
Don't just wonder. Report it in JIRA as a possible documentation
enhancement. Or, even better, provide a documentation patch.
-Gisbert
--
Gisbert Amm
Softwareentwickler Infrastruktur
Telefon: (0721) 91374 - 4224
Telefax: (0721) 91374 - 2740
E-Mail: gisbert.amm@1und1.de
Internet: www.1und1.de
1&1 Internet AG
Elgendorfer Strasse 57
56410 Montabaur
Amtsgericht Montabaur HRB 6484
Vorstand: Henning Ahlert, Ralph Dommermuth, Matthias Ehrlich, Andreas
Gauger, Thomas Gottschlich, Matthias Greve, Robert Hoffmann, Norbert
Lang, Achim Weiss
Aufsichtsratsvorsitzender: Michael Scheeren
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Build plugin without using it
Posted by ro...@aciworldwide.com.
Tim Kettler <ti...@udo.edu> wrote on 10/05/2007 01:41:33 AM:
>
> <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>.
>
Thanks!
That puts a new spin on things and simplifies my life quite a bit. Why
isn't this essential tidbit mentioned on any of the plugin how-to pages,
or did I just miss it?
Robert Egan
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.
Re: Build plugin without using it
Posted by Tim Kettler <ti...@udo.edu>.
robert.egan@aciworldwide.com 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" <ws...@gmail.com> wrote on 10/04/2007 02:59:29 PM:
>
>> On 10/4/07, robert.egan@aciworldwide.com <ro...@aciworldwide.com>
> 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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Build plugin without using it
Posted by ro...@aciworldwide.com.
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. 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" <ws...@gmail.com> wrote on 10/04/2007 02:59:29 PM:
> On 10/4/07, robert.egan@aciworldwide.com <ro...@aciworldwide.com>
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.
Re: Build plugin without using it
Posted by ro...@aciworldwide.com.
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" <ws...@gmail.com> wrote on 10/04/2007 02:59:29 PM:
> On 10/4/07, robert.egan@aciworldwide.com <ro...@aciworldwide.com>
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.
Re: Build plugin without using it
Posted by Wendy Smoak <ws...@gmail.com>.
On 10/4/07, robert.egan@aciworldwide.com <ro...@aciworldwide.com> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org