-
Notifications
You must be signed in to change notification settings - Fork 5
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
API to run Ceylon module #60
Comments
Moving to 1.2, unfortunately. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If users want to run Ceylon using JBoss modules we have two options:
-- Well, actually we have two cases: the distrib modules are already in the classpath, set by the user, or
-- They are not and we need to either call or do like
Launcher
The problem ATM with JBoss modules is that it completely fucks up JAXP system-wise. The minute we load JBoss modules, it hijacks the JAXP system properties with its own classes, that only its own classloader can provide. This is wrong, as it kills every other thread running on the JVM that wants to use JAXP (if they are not using JBoss modules).
I guess the first thing would be to ask the JBoss modules guys if we can do something about not fucking up JAXP system-wise, and upgrade our JBoss modules lib when they add that option.
The text was updated successfully, but these errors were encountered: