Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Loose app doesn't honor outputFileNameMapping config on maven-war-plugin (e.g. for JAR dependencies) #1677

Open
imsandli opened this issue May 26, 2023 · 1 comment

Comments

@imsandli
Copy link

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:

  1. <stripVersion>true</stripVersion> seems to be ignored in LooseAppSupport.

  2. 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?

@scottkurz 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
@scottkurz
Copy link
Member

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 !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants