Hi,
if i correctly understand you have a property file for each environment
and maybe some other files and a base artifact (jar/war?) now it sounds
you have to build for each environment a different jar/war ?
Maybe something like this could help here:
https://github.com/khmarbaise/multienv-maven-plugin/
or:
https://github.com/khmarbaise/iterator-maven-plugin/
Kind regards
Karl Heinz Marbaise
On 31/05/17 11:42, Jürgen Weber wrote:
Hi Jörg,
problem is, I have to build message driven beans, some 20, only difference
is the queue name in the deployment descriptor. Queue names are listed in a
property file.
I know that Maven wants no environment specific properties in artifacts,
but Sun defined the activation spec for MDBs. And the activation spec is in
code or in ejb-jar.xml, both in the mdb jar. So I have to build a different
MDB for each queue. And I have to iterate over the queues (which is
possible in ant + JavaScript. Yuck).
So I'd need to attach n artefacts, wherea in a Maven pom I have to list
each artefact individually.
Greetings, Jürgen
Am 30.05.2017 08:45 schrieb "Jörg Schaible" <joerg.schai...@bpm-inspire.com
:
Hi Jürgen,
Jürgen Weber wrote:
What is the recommended work-around for attaching artifacts created by
antrun?
* forward target directory as variable to ant ?
That helps if the created files should be removed in a normal "clean" phase.
* build-helper-maven-plugin attach-artifact ?
Definitely the proper action.
http://technotes.khitrenovich.com/attach-maven-artifact-
external-build-xml-file/
https://issues.apache.org/jira/browse/MANTRUN-181
Thx,
Juergen
Cheers,
Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
