[shrinkwrap-issues] [JBoss JIRA] (SHRINKWRAP-393) Make Shrinkwrap resolver work in a modular environment

Galder Zamarreño (JIRA) jira-events at lists.jboss.org
Tue Apr 10 15:32:47 EDT 2012


Galder Zamarreño created SHRINKWRAP-393:
-------------------------------------------

             Summary: Make Shrinkwrap resolver work in a modular environment
                 Key: SHRINKWRAP-393
                 URL: https://issues.jboss.org/browse/SHRINKWRAP-393
             Project: ShrinkWrap
          Issue Type: Enhancement
          Components: ext-resolver
    Affects Versions: 1.1.0-alpha-1
            Reporter: Galder Zamarreño


The subsystem I'm building requires dependencies of my war to downloaded and resolved at runtime or deploy time.

So, that means that I need to create a set of JBoss AS7 modules for Shrinkwrap resolver. However, the way classloader works to load META-INF/services/org.jboss.shrinkwrap.resolver.api.maven.MavenDependencyResolver is a bit crap cos it uses thread context classloader in DependencyBuilderInstantiator.

Can this be rewritten so that classloading can work in a modular environment as well?

The problem is that the thread context classloader at runtime is:

{code}ModuleClassLoader for Module "org.jboss.as.server:main" from local module loader @5d2412e7 (roots: /var/folders/vk/g4jts68n6nd37lgvynmtrwxh0000gn/T/test-module,/Users/g/Go/code/scalabox.git/./build/target/jboss-as/modules){code}

I can probably workaround this setting the module's classloader as thread context classloader temporarily, but this is not nice.

Thoughts?



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       



More information about the shrinkwrap-issues mailing list