You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<stripVersion>true</stripVersion> seems to be ignored in LooseAppSupport.
configuring <outputFileNameMapping>@{artifactId}@.@{extension}@</outputFileNameMapping>
in maven-ear/war-plugin did not help. Probably because my project is a war. (See here)
Is there a way to link to jars without a version number?
The text was updated successfully, but these errors were encountered:
scottkurz
changed the title
Dev Mode ignores stripVersion
Loose app doesn't honor outputFileNameMapping config on maven-war-plugin (e.g. for JAR dependencies)
May 26, 2023
I changed the title since I think the second observation you mentioned (that <outputFileNameMapping> doesn't work for WARs) is what we should center on.
(I don't think it makes as much sense to look at expanding the interpretation of the liberty-maven-plugin <stripVersion> however. )
But thank you @imsandli for opening the issue and for digging up and including references to the past PRs here !
In a maven multimodule war project with jpa it would help to point to a
<jar-file>
in the persistence.xml.Example:
<jar-file>../../lib/entities.jar</jar-file>
Failed tries:
<stripVersion>true</stripVersion>
seems to be ignored in LooseAppSupport.configuring
<outputFileNameMapping>@{artifactId}@.@{extension}@</outputFileNameMapping>
in maven-ear/war-plugin did not help. Probably because my project is a war. (See here)
Is there a way to link to jars without a version number?
The text was updated successfully, but these errors were encountered: