[ 
https://issues.apache.org/jira/browse/UIMA-6240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Work on UIMA-6240 started by Richard Eckart de Castilho.
--------------------------------------------------------
> Failure to resolve type system imports when generating descriptors
> ------------------------------------------------------------------
>
>                 Key: UIMA-6240
>                 URL: https://issues.apache.org/jira/browse/UIMA-6240
>             Project: UIMA
>          Issue Type: Bug
>          Components: uimaFIT-Maven-Plugin
>            Reporter: Richard Eckart de Castilho
>            Assignee: Richard Eckart de Castilho
>            Priority: Major
>             Fix For: 2.6.0uimaFIT
>
>
> The uimaFIT maven plugin "generate" goal fails if there are by-name imports 
> from other Maven modules:
> {code}
> [WARNING] Cannot generate descriptor for [XXX]
> org.apache.uima.resource.ResourceInitializationException: An import could not 
> be resolved.  No file with name "some/typesystem.xml" was found in the class 
> path or data path. (Descriptor: some JAR reference)
>       at 
> org.apache.uima.util.CasCreationUtils.mergeTypeSystems(CasCreationUtils.java:1084)
>       at 
> org.apache.uima.util.CasCreationUtils.mergeTypeSystems(CasCreationUtils.java:1029)
>       at 
> org.apache.uima.fit.factory.TypeSystemDescriptionFactory.createTypeSystemDescription(TypeSystemDescriptionFactory.java:133)
>       at 
> org.apache.uima.fit.factory.AnalysisEngineFactory.createEngineDescription(AnalysisEngineFactory.java:1018)
>       at 
> org.apache.uima.fit.maven.GenerateDescriptorsMojo.execute(GenerateDescriptorsMojo.java:133)
>       at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
> {code}
> This happens despite the uimaFIT maven plugin setting the thread context 
> classloader to a classloader which has access to all the dependencies of the 
> Maven module being processed. Unfortunately, the context classloader is not 
> picked up properly due to UIMA-6239.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to