Replies: 2 comments 2 replies
-
Hadn't considered this. |
Beta Was this translation helpful? Give feedback.
-
So, the vast majority of errors/warnings are class format errors come from multirelease JARs. We should fix that on our end some day. Pretty sure there is a bug in ikvm for it already. The others are class format errors. Obviously getting IKVM supporting later JRE releases would fix that. A few are class not found issues. I'd be curious if these are actual bugs in the Maven dep tree. Missing things? Maybe. Not sure what approach to take here. I understand the user of YOUR PACKAGE don't want to see them. But I can't think of any coherent approach to distinguish you from everybody else. |
Beta Was this translation helpful? Give feedback.
-
I look after a package publish on NuGet which makes use of
MavenReference
, something like this:I'm wondering if it is possible to supply some configuration to
MavenReference
to silence the IKVM warning messages end users see the first time they build their project after including my package? The messages are useful to me when things go wrong as a starting point for investigation, but under normal circumstances for end users of my package they are potentially confusing, or noise when emitted as part of a larger build process.Any advice on the configuration options available for these messages gratefully received!
Beta Was this translation helpful? Give feedback.
All reactions