Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Duplicate
-
None
-
None
-
None
Description
ActiveMQ has an odd structure to define Java services. Instead of putting them into META-INF/services/<classname>, they put them into sub-folders:
1008 2016-04-28 12:30 META-INF/services/org/apache/activemq/wireformat/default
1013 2016-04-28 12:30 META-INF/services/org/apache/activemq/transport/mock
1011 2016-04-28 12:30 META-INF/services/org/apache/activemq/transport/ssl
1011 2016-04-28 12:30 META-INF/services/org/apache/activemq/transport/nio+ssl
1011 2016-04-28 12:30 META-INF/services/org/apache/activemq/transport/udp
1023 2016-04-28 12:30 META-INF/services/org/apache/activemq/transport/multicast
1011 2016-04-28 12:30 META-INF/services/org/apache/activemq/transport/tcp
After merging services with the metaInf-services, the folder looks like so:
1008 2016-04-28 12:30 META-INF/services/default
1013 2016-04-28 12:30 META-INF/services/mock
1011 2016-04-28 12:30 META-INF/services/ssl
1011 2016-04-28 12:30 META-INF/services/nio+ssl
1011 2016-04-28 12:30 META-INF/services/udp
1023 2016-04-28 12:30 META-INF/services/multicast
1011 2016-04-28 12:30 META-INF/services/tcp
which renders the JAR useless.
You can test with this JAR: http://search.maven.org/#artifactdetails%7Corg.apache.activemq%7Cactivemq-client%7C5.13.3%7Cjar
Attachments
Issue Links
- duplicates
-
MASSEMBLY-920 ContainerDescriptorHandler for MetaInf-Services breaks folder structure
- Closed