[jbosstools-issues] [JBoss JIRA] (JBIDE-15125) arqullianClassLoader in root of workspace

[Snjezana Peco (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-15125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12787477#comment-12787477 ] 

Snjezana Peco commented on JBIDE-15125:
---------------------------------------

ArquillianClassLoader is a separate classloader that is used to create an arquillian archive or discover an arquillian container.
It uses the arqullianClassLoader directory to avoid the Windows jar locking issue.
The PR moves this directory to the .metadata/.plugins/org.jboos.tools.arquillian.core directory.
I have applied the patch to master, but not in the jbosstools-4.1.x branch.
                
> arqullianClassLoader in root of workspace
> -----------------------------------------
>
>                 Key: JBIDE-15125
>                 URL: https://issues.jboss.org/browse/JBIDE-15125
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: testing-tools
>            Reporter: Max Rydahl Andersen
>            Assignee: Snjezana Peco
>            Priority: Critical
>             Fix For: 4.1.0.CR1
>
>
> I have a folder named "arquillianClassloader" in my workspace.
> Any idea where that is coming from and what it is for ?
> arquillianClassLoader
> ├── jboss-as-kitchensink-html5-mobile
> │   └── shrinkwrap-impl-base-1_0_1
> │       └── META-INF
> │           └── services
> │               ├── org.jboss.shrinkwrap.api.exporter.ZipExporter
> │               ├── org.jboss.shrinkwrap.api.spec.WebArchive
> │               └── org.jboss.shrinkwrap.spi.Configurable
> └── jboss-javaee6-webapp
>     └── shrinkwrap-impl-base-1_0_1
>         └── META-INF
>             └── services
>                 ├── org.jboss.shrinkwrap.api.exporter.ZipExporter
>                 ├── org.jboss.shrinkwrap.api.spec.WebArchive
>                 └── org.jboss.shrinkwrap.spi.Configurable

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira