We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
All your examples look like this
wildfly::config::module { 'org.apache.ignite': source => 'http://my.source.com/source-file.jar', dependencies => ['javax.api', 'javax.transaction.api'] }
what about when there are multiple jar files as part of a module?
such as
<?xml version="1.0" encoding="UTF-8"?> <module xmlns="urn:jboss:module:1.1" name="org.apache.ignite"> <resources> <resource-root path="ignite-core-2.8.1.jar"/> <resource-root path="ignite-indexing-2.8.1.jar"/> <resource-root path="ignite-shmem-1.0.0.jar"/> <resource-root path="cache-api-1.0.0.jar"/> </resources> <dependencies> <module name="javax.api"/> <module name="sun.jdk" /> <module name="com.h2database.h2" /> </dependencies> </module>
The text was updated successfully, but these errors were encountered:
Hi,
The rationale behind not direct supporting tarball/archive as a source for a module was to avoid dependencies of other modules to extract it.
Basically you have two options for the scenario you described:
Install the files as dependencies and require then in your module.
Download/copy other JARs manually using file module.
Sorry, something went wrong.
No branches or pull requests
All your examples look like this
what about when there are multiple jar files as part of a module?
such as
The text was updated successfully, but these errors were encountered: