-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
osgi
and aspectj
annotations(?) are not recognized by ijar
and logs are flooded with the noise
#21781
Comments
@dkashyn-sfdc do you have a minimal repro? |
Not yet, but if you add |
Another one is With endless output like
and
|
https://repo1.maven.org/maven2/org/apache/ws/commons/axiom/axiom-dom/1.2.20/ |
Thanks. It looks like this is WAI. There is some precedent for skipping this warning for well-known cases, but I'm not sure how well that scales for all such cases. Another option could be to cache these and only report an unknown attribute once per ijar invocation which could go a long way towards reducing spam? That aside, I would have expected most builds today to use the header compiler (Turbine), and not ijar. what Bazel version are you using? Do you have header compilation explicitly disabled? In the meantime, you might be able to workaround this with |
@hvadehra Based on the logs, I think that these warnings are emitted for |
Ah, right. Is it possible to maybe wrap the corresponding source jars in a |
In our cases this is some
I suspect that in this case |
Then maybe just build with |
I'll try It is not speeding things up for us unless we use RBE and slowing them down for local env :( Back to |
@dkashyn-sfdc Are you using a recent version of rules_java and Bazel, which use a Graal Native Image of Turbine? Together with |
I submitted #22072 to deduplicate the warnings. |
Work towards bazelbuild#21781 Closes bazelbuild#22072. PiperOrigin-RevId: 629359080 Change-Id: I2c813d3a9069ec125a914bfc57e6c9068c83d3bc
still seeing this with 7.2.0rc1 |
Description of the bug:
ijar
produces extra logging that just floods the output without any real value.That message is originating from
bazel/third_party/ijar/classfile.cc
Line 1595 in 472b96d
aspectj
output alone is hugeWhich category does this issue belong to?
Java Rules
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
No response
Which operating system are you running Bazel on?
OSX, RHEL
What is the output of
bazel info release
?7.1
If
bazel info release
returnsdevelopment version
or(@non-git)
, tell us how you built Bazel.No response
What's the output of
git remote get-url origin; git rev-parse HEAD
?No response
Is this a regression? If yes, please try to identify the Bazel commit where the bug was introduced.
No response
Have you found anything relevant by searching the web?
No response
Any other information, logs, or outputs that you want to share?
aspectj
is much more noisy, thousands of lines like (other annotations fromorg.aspectj.weaver
are there as well see https://github.com/codehaus/backport175/blob/master/org.aspectj/modules/weaver/src/org/aspectj/weaver/AjAttribute.java for more of those)The text was updated successfully, but these errors were encountered: