-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
None
-
All
-
Small
TCOMP-2320 allows to export dynamic dependencies. The process is working correctly but in the case of a ESB/OSGI export, those dependencies are automatically removed by the assembly plugin which rescans dependencies remove them.
Using the jms connector with artemis drivers, during job export we can see the following in maven logs:
... [DEBUG] adding entry lib/artemis-selector-2.31.2.jar [DEBUG] adding entry lib/artemis-core-client-2.31.2.jar [DEBUG] adding entry lib/artemis-commons-2.31.2.jar [DEBUG] adding entry lib/artemis-jms-client-2.31.2.jar ... org.apache.activemq:artemis-commons:jar:2.31.2:compile org.apache.activemq:artemis-core-client:jar:2.31.2:compile org.apache.activemq:artemis-jms-client:jar:2.31.2:compile org.apache.activemq:artemis-selector:jar:2.31.2:compile ... [DEBUG] Processing DependencySet (output=${talend.job.name}) [DEBUG] Filtering dependency artifacts WITHOUT transitive dependency path information. [DEBUG] org.apache.activemq:artemis-commons:jar:2.31.2 was removed by one or more filters. [DEBUG] org.apache.activemq:artemis-core-client:jar:2.31.2 was removed by one or more filters. [DEBUG] org.apache.activemq:artemis-jms-client:jar:2.31.2 was removed by one or more filters. [DEBUG] org.apache.activemq:artemis-selector:jar:2.31.2 was removed by one or more filters.
- is related to
-
TCOMP-2320 Export Dynamic dependencies in job build
- Done