You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Richard Eckart de Castilho (Jira)" <de...@uima.apache.org> on 2021/11/18 09:32:00 UTC

[jira] [Created] (UIMA-6396) uimaFIT maven plugin mixes up test and compile scopes

Richard Eckart de Castilho created UIMA-6396:
------------------------------------------------

             Summary: uimaFIT maven plugin mixes up test and compile scopes
                 Key: UIMA-6396
                 URL: https://issues.apache.org/jira/browse/UIMA-6396
             Project: UIMA
          Issue Type: Bug
          Components: Ruta, uimaFIT-Maven-Plugin
            Reporter: Richard Eckart de Castilho
             Fix For: 2.6.0uimaFIT, 3.1.1ruta, 3.2.1uimaFIT


It looks like uimaFIT maven plugin scans types.txt files from compile dependencies as well as from test dependencies - and then when loading the descriptors, it seems that a different classloader is used causing imports in test scoped dependencies not to be properly resolvable.

First thing, the plugin shouldn't scan test dependencies by default at all. We probably need a scope parameter to control which scopes the plugin looks at.

Second, even if the test scope is looked at, the same path should be used during classpath scanning as well as during import resolving.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)