You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a Maven artifact which contains multiple UIMA components, but I do not want OMTD to see them all. For that reason, I have created only descriptors for one of the components and also the META-INF/eu.openminted.share/descriptors.txt lists only one component.
However, when I tried registering the component as a Maven artifact, the registry offered me a choice between all the components in the JAR.
Does the registry scanning the classes in Maven artifacts for component information even if the JAR already includes a META-INF/eu.openminted.share/descriptors.txt?
IMHO the registry should not perform a class-based component scan if a META-INF/eu.openminted.share/descriptors.txt file is present in the artifact.
Or could it be a problem of artifact caching? (cf. #8)
As a user, it is hard to tell what actually happens because the system logs no information of the individual steps it is performing to the UI.
The text was updated successfully, but these errors were encountered:
My fault. The registry correctly detects if any descriptors are present and if so does not do the class scanning. Problem was, that the JAR really did not contain any descriptors due to a but in the OMTD-SHARE Maven plugin (3.0.2.3 - 3.0.2.4).
I have a Maven artifact which contains multiple UIMA components, but I do not want OMTD to see them all. For that reason, I have created only descriptors for one of the components and also the
META-INF/eu.openminted.share/descriptors.txt
lists only one component.However, when I tried registering the component as a Maven artifact, the registry offered me a choice between all the components in the JAR.
Does the registry scanning the classes in Maven artifacts for component information even if the JAR already includes a
META-INF/eu.openminted.share/descriptors.txt
?IMHO the registry should not perform a class-based component scan if a
META-INF/eu.openminted.share/descriptors.txt
file is present in the artifact.Or could it be a problem of artifact caching? (cf. #8)
As a user, it is hard to tell what actually happens because the system logs no information of the individual steps it is performing to the UI.
The text was updated successfully, but these errors were encountered: