-
Notifications
You must be signed in to change notification settings - Fork 317
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
Manifest version parsing is not working in Wildfly #599
Comments
Also, shouldn't we close the JarFile after the version parsing? |
@eyalkoren Couldn't we just remove the version check here: Lines 84 to 86 in f51f253
It seems like the header re-adding is idempotent: Lines 55 to 60 in f51f253
Is the sole reason for the version check to reduce the overhead of the @mdindoffer thanks for all the reports, really appreciated ❤️ |
@mdindoffer Thanks for this useful input! I made a fix and will link a snapshot to test shortly. @felixbarny the check is indeed for performance reasons in this case, but I would say we should always strive to instrument as little as possible even when the performance hit is not huge. In addition, I DO see value in this matcher, I know I would use it before if had it available. So, for now I will add a fix and if we see we can't get it robust enough with little effort, we can remove this matcher altogether. |
@eyalkoren Yep, your fix works. Thanks. |
Manifest version resolution introduced in #558 does not work in Widlfly.
The
jarUrl.getFile()
returnsfile:/home/wildfly-9.0.2.Final/modules/system/layers/base/org/apache/httpcomponents/main/httpclient-4.3.6.jar!/
The path contains an exclamation mark, probably because the full URL is
jar:file:/home/wildfly-9.0.2.Final/modules/system/layers/base/org/apache/httpcomponents/main/httpclient-4.3.6.jar!/
, i.e. includes thejar:
protocol. This breaks the JarFile creation.Stack Trace
Environment
Wildfly 9.0.2.Final with provided httpclient 4.3.6
The text was updated successfully, but these errors were encountered: