To make it more cleared here is the output
....
Writing Pack 2: izpack-demo01 für Linux
....
[ End ]
[INFO]
[INFO] --- maven-site-plugin:3.3:attach-descriptor (attach-descriptor) @
demo-assembly ---
[INFO]
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @
demo-assembly ---
[INFO] Installing com.soebes.tools.izpack:demo-assembly:0.1.0-SNAPSHOT
at end
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] IZPack Demo :: Root ............................... SUCCESS [0.781s]
You can see that the install plugin is called but has no artifacts
available which can be installed ?
Kind regards
Karl Heinz
On 2/28/14 11:56 AM, Karl Heinz Marbaise wrote:
Hi,
i have question concerning a maven plugin which defines it's own
lifecycle (extensions true)...it produces artifacts without a problem...
I have observed an issue...this plugin does not work in relationship
with maven-install-plugin / maven-deploy-plugin in relationship with
installAtEnd / deployAtEnd option is there anything which should be paid
attention to in creating such plugin ?
Or is this related to maven-install/deploy-plugin
any ideas / hints / suggestions ?
Thanks in advance...
Kind regards
Karl-Heinz Marbaise
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
Mit freundlichem Gruß
Karl-Heinz Marbaise
--
SoftwareEntwicklung Beratung Schulung Tel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl-Heinz Marbaise ICQ#: 135949029
Hauptstrasse 177 USt.IdNr: DE191347579
52146 Würselen http://www.soebes.de
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
