Create a pom, place the plugins configuration in sequence. Bind Each
plugin's execution to the same phase.
ie you can bind 2 executions from diffrent plugins to the same phase. The
order of executions are the
order of plugins appear in the pom
-D
On 9/17/06, Manuel Ledesma <[EMAIL PROTECTED]>
Let me explain the scenario,
We have user's properties on DB (MySQL), existing environment using ant
1.6.5, we are using depends feature to trigger the load of user's properties
before starting weblogic.
I have already the user-profile-plugin and weblogic-plugin, but I don't know
how I can wire t
not possible since you dont want to wire them into a maven phase
-D
On 9/17/06, Manuel Ledesma <[EMAIL PROTECTED]> wrote:
I would like to be able to call just one and trigger the execution of the
other.
-Original Message-
From: dan tran [mailto:[EMAIL PROTECTED]
Sent: Sunday, Septem
I would like to be able to call just one and trigger the execution of the
other.
-Original Message-
From: dan tran [mailto:[EMAIL PROTECTED]
Sent: Sunday, September 17, 2006 8:12 PM
To: Maven Developers List
Subject: Re: Calling plugins sequentially
mvn plugin1:goal1 plugin2:goal2 ?
-
mvn plugin1:goal1 plugin2:goal2 ?
-D
On 9/17/06, Brett Porter <[EMAIL PROTECTED]> wrote:
Please don't cross-post. The users@ list was the correct place to
post it, so only posting it there is sufficient.
- Brett
On 18/09/2006, at 10:02 AM, Manuel Ledesma wrote:
> First of all, I only have
Please don't cross-post. The users@ list was the correct place to
post it, so only posting it there is sufficient.
- Brett
On 18/09/2006, at 10:02 AM, Manuel Ledesma wrote:
First of all, I only have two days working with maven. I have read
the book
Better Buils with Maven completely and any
First of all, I only have two days working with maven. I have read the book
Better Buils with Maven completely and any possible documentation found in
maven.apache.org.
I would like to call two o more plugins sequentially, example
- user-profile-plugin - loads user properties into maven runtim
I'm interested in opening this up for discussion. Where the code
lives doesn't really have any effect on binary artifacts - they end
up in the repository and can be used from anywhere. So I'm wondering
where it makes the most sense to put it in the source repository.
I'm inclined to say hav
On 9/17/06, Alexandre Poitras <[EMAIL PROTECTED]> wrote:
Another thing I would like to see fixed is the snapshot apache
repository. Nighlty builds are still deployed using a unique version
identifier. This feature doesn't work and this is why a lot of people
have trouble when it's come to snapsh
On 18/09/2006, at 12:40 AM, Alexandre Poitras wrote:
Another thing I would like to see fixed is the snapshot apache
repository. Nighlty builds are still deployed using a unique version
identifier. This feature doesn't work and this is why a lot of people
have trouble when it's come to snapshot
Another thing I would like to see fixed is the snapshot apache
repository. Nighlty builds are still deployed using a unique version
identifier. This feature doesn't work and this is why a lot of people
have trouble when it's come to snapshot dependencies. It should be
written very big somewhere on
done
On 9/16/06, Jochen Wiedmann <[EMAIL PROTECTED]> wrote:
... the directory
/www/people.apache.org/repo/m2-ibiblio-repository/org/apache/ws/commons/axiom
due to the release of Axiom 1.1.
Thanks,
Jochen
--
My wife Mary and I have been married for forty-seven years and not
once have we had a
12 matches
Mail list logo
