activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From gemmellr <>
Subject [GitHub] activemq-artemis issue #1272: ARTEMIS-1129: Client Dependencies
Date Wed, 17 May 2017 14:25:25 GMT
Github user gemmellr commented on the issue:
    Would an alternative be just offering a separate client binary convenient download, rather
than just the single all-inclusive archive? Or documenting a maven command to gather all the
current jars needed for a given client release? Those wouldn't really be any harder to actually
use than the single jar in the end, but would avoid needing new uber jars that could end up
being a little fragile given all the shading config used to create them and going much less
tested than the main modules.
    Setting that aside, I notice there are various profiles specifying modules in the pom,
and I wondered if it is sufficient to only add these new ones in the one place as done, or
if they also need added to some of the other profiles? Not sure exactly what they all do.

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message