This question belongs on the users list.
Setting that aside, finalName is only meant as a convenience for use
during the build process, and as such it only affects the filenames
local to the build.
You're better off if you regard the repositories (local and remote) as
databases (or catalogs), where the content has to be addressable in a
predictable way if it's going to be retrieved.
If you're trying to set the name of a file in a particular way, chances
are good that you're trying to use the repository as more than an
artifact database / catalog.
HTH,
-john
On 09/26/2014 01:34 AM, VicBi wrote:
Hi,
Thanks for responding, I saw that I could use the plugin assembly. I'll try
to do it with this plugin :).
Thanks and regards
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-deploy-does-not-respect-finalName-tp5806549p5806658.html
Sent from the Maven Developers mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
John Casey
---
GitHub: https://github.com/jdcasey/
Twitter: http://twitter.com/buildchimp
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
