This is a bug we are hoping to fix shortly. While finalName can't be
completely modified for installing in the repository, it should be possible
to add a classifier for the environment. For reference, the JIRA bug is the
one referring to attaching an artifact with a classifier via a profile.
- Brett
On 9/20/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
I have a project to build / deploy for three different enviroments
(test,integration, production with different configs) and want to set the
jar file name depending on the active profile.
I know one possibility is with the finalName Element. The jar process uses
the finalName and generate the jar with the correct name (specified by
finalName)
But the install process doesn't use the finalName.
How can I achieve it that the install process (and of course the deploy
process) also uses the finalName.
Please help!
TIA
Martin Kuhn
++
Diese Nachricht ist vertraulich und ausschließlich für den/die Adressaten
bestimmt. Sollten Sie nicht der beabsichtigte Adressat, einer seiner
Mitarbeiter oder sein Empfangsbevollmächtigter sein, ist jede Form der
Kenntnisnahme, Veröffentlichung, Vervielfältigung oder Weitergabe des
Inhalts dieser Nachricht unzulässig. In diesem Fall bitten wir, den
Absender umgehend zu benachrichtigen und die Nachricht zu vernichten.
Elektronisch versandte Nachrichten können durch Unberechtigte manipuliert
und/oder gelesen werden, weshalb jegliche Haftung hierfür ausgeschlossen
wird.
++
This communication is confidential and is intended solely for the
addressee(s). If you are not the intended recipient(s), his/her assistant,
or authorized recipient, any form of disclosure, reproduction,
distribution or any use of this communication or the information in it, is
strictly prohibited and may be unlawful. In this case, please notify the
sender immediately and destroy the e-mail. Electronic communication via
the Internet by e-mail may be manipulated and/or read by third parties,
thus we exclude any liability whatsoever for this e-mail.
++
