Support for native libraries in modules. about gradle-jboss-modules-plugin HOT 4 OPEN

Hi,
Could you explain a little bit this issue? My understanding is that this is about directory structure, that can be done using distribution plugin.
In our samples there is activemq module that has additional folder META-INF.

from gradle-jboss-modules-plugin.

Hi, @zhurlik.

It is partly about directory structure. Is there a way to handle pulling the native library from a maven or ivy repo and directing it to the correct directory? Based on that example it looks like I'd have to have those artifacts in source control.

from gradle-jboss-modules-plugin.

@zhurlik

In order to get the behavior I needed for this, I had to add a copy action to the make modules task:

makeModules {
  doLast {
    copy {
      into "${buildDir}/install/myServer/modules/my/module/name/main/lib/win-x86_64"
      from(configurations.myNativeModuleConfig) {
        rename 'nativeStuff-(.*).dll', 'nativeStuff.dll'
      }
    }
  }
}

Is there a cleaner way to accomplish this?

from gradle-jboss-modules-plugin.

I think that right now I see what you meant.

1. first of all we have to define how you would like to fetch/download *.so/*.dll files from the repository. I see a couple of solutions:

• as a dependency for example using custom layout for ivy (https://docs.gradle.org/current/userguide/repository_types.html)
• groovy/ant tasks
• other manually ways
  For all above cases we have to specify a few variables such as:
  [osname] and [cpuname], [module]/[revision]/[type]/[artifact].[ext]

2. then after knowing that a native resource will be available, we can discuss how it will be copied to jboss module folder

from gradle-jboss-modules-plugin.