Hi Ryan,
So what you are trying to achieve is control the ordering of executions
within a single phase?
Ie you want:
Phase X:
(1) plugin A
(2) plugin B
(3) plugin A again
Yes, I think this is not currently possible to achieve with execution
blocks.
There is some discussion
Thanks! You reiterated my thoughts almost exactly.
Forcing executions into arbitrary adjacent phases will work fine… it
just seems ugly.
thanks,
rovrevik
On Fri, Feb 22, 2008 at 3:35 AM, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
Hi Ryan,
So what you are trying to achieve is control the
related to MNG-1701 ?
On Fri, Feb 22, 2008 at 1:15 PM, Ryan Ovrevik [EMAIL PROTECTED] wrote:
Thanks! You reiterated my thoughts almost exactly.
Forcing executions into arbitrary adjacent phases will work fine… it
just seems ugly.
thanks,
rovrevik
On Fri, Feb 22, 2008 at 3:35 AM,
Yeah... seems related (if not the same) to me.
Why is specifying a plugin more than once bad? Is there a technical
reason? Pushing sections to adjacent phases works but since there are
only so many phases it doesn't scale.
On Fri, Feb 22, 2008 at 5:04 PM, Carlos Sanchez [EMAIL PROTECTED] wrote:
We should probably add some logic to the project/POM validator to
detect duplicated plugin entries (by the plugin's
groupId:artifactId:version) and fail the build with a useful error
message. That would prompt users to consolidate multiple plugin
sections that refer to the same plugin.
unless you have to define the plugin more than once because of profiles
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I was specifying a plugin twice with-in a profile to control the order
of operations across two plugins with in a particular phase. The
scenario is as follows (simplified):
* Use sql-maven to drop and create a database.
* Use dbunit to import some data.
* Use sql-unit again to drop some columns on
Put multiple execution blocks inside the executions. You would
probably need to use two phases though.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Ryan Ovrevik
Sent: Thursday, February 21, 2008 10:19 PM
To: dev@maven.apache.org
Subject: Re:
Yeah, thanks, I know about using multiple executions.
It is a shame that you have to put an execution in an arbitrary phase
just to make the configuration behave (at least it seems that way to
me). The use case that I have fits very nicely into
generate-test-resources to export date from a source
Only the first plugin configuration is applied when a plugin is used
multiple times within a profile. Following plug in configurations do
not use their specified configuration. Instead, configuration is based
on what appears to be a combination of the configuration specified in
the first plugin
On Wed, Feb 20, 2008 at 8:25 PM, Ryan Ovrevik [EMAIL PROTECTED] wrote:
Only the first plugin configuration is applied when a plugin is used
multiple times within a profile. Following plug in configurations do
not use their specified configuration. Instead, configuration is based
on what
Yep, I think this is related to it only picking the first version it
comes across, regardless of future version declarations.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Ryan Ovrevik
Sent: Wednesday, February 20, 2008 10:25 PM
To: dev@maven.apache.org
12 matches
Mail list logo
