Yeah - I was actually just about to respond to my own mail to indicate
exactly that. I don't know how I missed that the first time through the
doc - I think I was looking for a property named something differently.
That's exactly what I was looking for.
Thanks!
Eric
On Tue, Jun 20, 2017 at
Hi,
Have you checked the documentation about.. fileNameMapping
the following from the docs:
The file name mapping to use for all dependencies included in the EAR
file. The following values are valid standard, {code no-version}, full,
no-version-for-ejb. The standard means the filename is the
Is there a way to customize the filename used by the maven-ear-plugin for
the different modules but in a general template way?
At the moment, the bundleFilename by default seems to be:
${artifactId}-${version}.${packaging}
I would like to prepend it with a $[groupId} as well.
Hi all,
Many of my maven modules have the same build setup. For example a specific
shade variant or building docker images.
To clean up the process, and make it easier for others to reuse, I like to
get all the plugin bindings and configurations out of the POM and put it
into it's own lifecycle
