-
Notifications
You must be signed in to change notification settings - Fork 199
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
Exception Provider class xmlpull not found in modularized application #1155
Comments
Hi @tobiasdiez, thanks for reporting this! I wonder if the problem is that Can you try modifying
and see if that change would fix the issue? |
This issue is still present in 2.6:
|
In 2.6.1 it is still present: JabRef/jabref#6594 |
Hi @tobiasdiez, can you create a github repository with a simple repro? |
Hello. I am facing the same problem. module-info.java module com.jesjobom {
requires applicationinsights.core; //automatic module
} Error:
|
Just going to throw this out there as a something that might save someone some work, or prod something into motion. I've got insights working for another project in a modularized build by way of adding module-info to the insights jars... The caveat is this is dependent on having a working webservice stack, which last I looked was still not jigsaw compliant, and still relied on reflection, meaning jdeps didn't ferret out all the needed dependencies. Making insights modular looks reasonably trivial compared to the j2ee stacks needed for webservice calls. Use at own risk. Your mileage may vary. Insert caveat here. |
Closing, there are new 3.4.0 versions |
When using applicationinsights-core-2.5.1 in an modularized java 12 (or 13) application, you get the following error:
The file
/META-INF/services/com.microsoft.applicationinsights.core.dependencies.xmlpull.v1.XmlPullParserFactory
indeed containscom.microsoft.applicationinsights.core.dependencies.xmlpull.mxp1.MXParser,org.xmlpull.mxp1_serializer.MXSerializer
which is indeed a strange format (as there should be one class per line). I guess one should use StAX instead of XPP3 anyway...The text was updated successfully, but these errors were encountered: