[UIMA-6240] Failure to resolve type system imports when generating descriptors

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.6.0uimaFIT, 3.2.0uimaFIT
• Component/s: uimaFIT-Maven-Plugin
• Assignee: Richard Eckart de Castilho
• Reporter: Richard Eckart de Castilho
• Created: 05/Jun/20 10:54
• Updated: 21/Oct/20 15:01
• Resolved: 25/Jun/20 10:48

Description

The uimaFIT maven plugin "generate" goal fails if there are by-name imports from other Maven modules:

[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)

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.

Issue Links

• relates to: UIMA-6239 RelativePathResolver_impl does never fall back to context classloader
• links to: GitHub Pull Request #111
• links to: GitHub Pull Request #112