Open gastaldi opened 4 years ago
Me too on supporting wildcards for quarkus.package.user-configured-ignored-entries. I am using uber-jar packaging type and need to exclude a complete jar file.
It never occurred to me that wildcards might not work. I can't even seem to rely on the Unix mantra that "everything is a file" to exclude entire directories.
Example:
<configuration>
<ignoredEntries>
<ignoredEntry>META-INF/native-image</ignoredEntry>
</ignoredEntries>
</configuration>
This to me means: ignore the META-INF/native-image
"file" (a directory). The ignoredEntries
documentation doesn't discourage me from expecting to be able to ignore directories:
...this array specifies entries that should be excluded from the final jar. The entries are relative to the root of the file.
Without wildcard- and folder support this to me is only a mildly useful feature. We use it to get rid off the "[WARNING] [io.quarkus.deployment.pkg.steps.JarResultBuildStep] Dependencies with duplicate files detected." build warnings.
@gastaldi I just tried it. It seems to work now. Thanks for the quick fix! Unfortunately it does not work with wildcards, e.g.
META-INF/swagger-ui-files/*.js.map
or even betterMETA-INF/**/*.js.map
, but I guess that is a different story.Originally posted by @sebthom in https://github.com/quarkusio/quarkus/issues/10406#issuecomment-653250959