I would propose the other direction: provide access to the core components or their build
and explain the manual steps to install & configure Wildfly to make use of it.
the scripts, as provided right now, hide to much of the important details for people who
want to install the monitor on an existing wildfly server.
it might be a good quickstart experience that we can keep, but the documentation should
explain the bare metal steps first and foremost.
On 06 Nov 2014, at 11:33, Heiko W.Rupp <hrupp(a)redhat.com> wrote:
> Am 06.11.2014 um 10:42 schrieb Heiko Braun <hbraun(a)redhat.com>:
>
>
> Currently the docs are a little misleading, as it says you should install the monitor
susbystem as described in the README but then points to the quickstart scripts
('start.sh') that download and install a dedicated WF instance.
>
> I think it would be better to focus on the steps needed to install all components on
an existing server.
We should perhaps write a start_big.sh that also installs your Cassandra subsystem, the
wildfly monitor
and then rhq-metrics(.war)
Anyone with shell-fu around? :)