Yep, I didn't understand that concept.
So what I tried now is I added an execution to my plugin, as follows:
<executions>
<execution>
<phase>install</phase>
<goals>
<goal>deploy</goal>
</goals>
</execution>
</executions>
under the assumption that maven will now consider this plugin as part of the
deploy goal of the install phase?
I tried running it and it actually does do what I want, it now does all the
steps prior to deploy - build, test, package, etc...
So that's good. Not sure if I did it the right way though or just lucked
out.
But now what if I also wanted the other goal I mentioned called
weblogic:start to run prior to this deploy? What would I need to do to the
pom? I am thinking maybe put that goal in the executions prior to the
existing deploy goal? like: <goal>weblogic:start</goal> ?? Somehow I dont
think thats the correct way to do it
--
View this message in context:
http://maven.40175.n5.nabble.com/How-can-I-have-a-goal-depend-on-another-goal-tp4384674p4388271.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
