This line was what misled me
"if I create an artefact for it in my nexus, the file name is
changed to jarfile-3.x.x"
You might want to add an installer to your deployment process.
I use IzPack to build an installer that puts all the right jars and
resource files in the right places.
You co
Maybe I'm missing something, but why not add an ant task or assembly plugin
during the pre-verify phase (or other appropriate phase) to rename the artifact
so that runtime it's the correct name for future phases?
I do a similar trick to get a pom first dependency to play nice as a manifest
firs
Hi Ron,
might have not explained it right: jarfile3.jar gets turned into
jarfile3-x.x.x.jar due to the version number i have to supply when creating the
artefact in nexus.
I agree it would be easier to either get rid of the version number at build
time or at least change the naming to jarfile-
... changing the code doesn't work, because the jar file in question is a
signed jar...
-Ursprüngliche Nachricht-
Von: Thomas Klöber
Gesendet: Montag, 8. Juni 2015 08:10
An: 'Maven Users List'; 'i...@soebes.de'
Betreff: AW: Help needed with a strange fixe
Hi Karl Heinz,
thanks for your answer.
Yes, we could change the code with the filename check. But I'm loath to do it
since it is a 3rd party jar file and we had to do this every time a new version
is released...
I'm just surprised that there is no other way or means to tell Maven that a
diffe
