I think you misunderstand the maven lifecycle. Maven has a default
lifecycle that is described here
https://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html.
You use plugins and define executions to hang off those phases.  In your
case I would use the maven exec plugin and probably attach it to the
integration test phase

On Sat, Oct 17, 2015, 1:26 PM Philipp Kraus <[email protected]>
wrote:

> Hello,
>
> I would like to create an own goal / target, that is run after the
> packaging goal.
> At the moment my default target is package, so I get a Jar file, so I
> would like to
> create an optional call „mvn executepackage“, which can be run after
> package.
> The goal should run a defined shell command with the Jar filename as input.
>
> How can I do this?
>
> Thanks
>
> Phil
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to