Hi Kent, Kent Närling wrote: > What IS really the purpose of <finalName>?
It is used to give the resulting artifact a different name locally in your target directory. > Apparently, the install plugin ignores the artifact name when > deploying it to the repository anyway?? Definitely. The filename is part of the Maven repository's meta data. Otherwise Maven would have no chance of pulling it from there again. > We would like to have a version-less filename on the artifact in the > repository (the version is in the path anyway), is this possible? No. These are Maven structures. IIRC there is a possibility to inject a different implementation for the RepositoryManager (or whatever the interface is called), but I am not aware of any alternative implementation. > If not, what is the real purpose of <finalName> if it is not > used for the > name of the artifact/file in the end anyway... ? You may either use the local file directly for a hot deployment on your developer machine or you can use additional plugins to process the file further. - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
