[
https://issues.apache.org/jira/browse/ARTEMIS-3334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17360198#comment-17360198
]
Robbie Gemmell commented on ARTEMIS-3334:
-----------------------------------------
The title still looks to be exactly what you say needs a PR, "documentation
gives no clue on how to place the jgroups config file in the classpath", so
maybe just update the incorrect description?! I see no reaosn to orphan this
Jira. The old description would still be in its updates, but since its
unnecessary, I dont see why that would matter.
Almost everything, including many doc changes, should have a JIRA. That you
already made one and now refuse to use it, actually seems a bit ridiculous to
me.
Aside: I am the person who coined 'NO-JIRA' a long long time ago in another
project, as a proposed escape for a pre-commit hook to ensure almost everything
had a JIRA, or a clear assertion it didnt need one, which someone could then be
queried on when it clearly should. The usage migrated over here. It is abused
rather a lot. The commit hook didnt happen in the end as apache used a
foundation wide svn repo at the time and it was deemed too much overhead.
> documentation gives no clue on how to place the jgroups config file in the
> classpath
> ------------------------------------------------------------------------------------
>
> Key: ARTEMIS-3334
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3334
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Affects Versions: 2.17.0
> Reporter: Erwin Dondorp
> Priority: Major
>
> on page
> [https://activemq.apache.org/components/artemis/documentation/latest/clusters.html,]
> it is mentioned that the jgroups configuration file must be in the classpath.
> the text is: "Make sure the file is in the java resource path so that Apache
> ActiveMQ Artemis can load it."
> however, the classpath is not easy to adjust as is completely replaced inside
> the startup script {{bin/artemis}}.
> The possibility is to use {{DEBUG_ARGS}} instead, but one must then also
> specify {{$ARTEMIS_HOME/lib/artemis-boot.jar}} again as otherwise that one is
> no longer in the classpath. so far, I could not find another way to adjust
> the classpath.
> It is true that the "artemis-boot" package builds a full classpath, but that
> classpath consists only of the JAR and ZIP files that it can find.
> Note that the examples properly work, because these do not use the regular
> startup scripts, but rely on maven to manage the classpath.
> my proposal: add a new fixed directory (e.g. \{{ARTEMIS_HOME/config}}? and/or
> {{ARTEMIS_HOME/_instance_/config}}?) which is always added to the classpath.
> the jgroups configuration file can then simply be placed in that directory
> when it is needed. that should then also be mentioned in the documentation.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
