[
https://issues.jboss.org/browse/ARQ-2051?page=com.atlassian.jira.plugin.s...
]
Gerhard Poul commented on ARQ-2051:
-----------------------------------
I've now created a new docker container that works with the current wercker
environment and I also moved to the 1.2 version of the liberty-maven-plugin. The bad news
is that at least for me the ApplicationMBean is never shown over the localConnector with
the versions I tested with from the public maven repositories. I see a few other
WebSphere:* MBeans, but not the ApplicationMBean.
[~atijms] are you seeing this MBean? Can you tell me which exact JDK and liberty version
you're using? tnx!
Add ability to add localconnector feature automatically to
server.xml
---------------------------------------------------------------------
Key: ARQ-2051
URL:
https://issues.jboss.org/browse/ARQ-2051
Project: Arquillian
Issue Type: Feature Request
Components: WebSphere Containers
Affects Versions: was_1.0.0.Beta2
Reporter: arjan tijms
Assignee: Gerhard Poul
For the managed container for Liberty to connect to a liberty instance, the
{{localConnector-1.0}} feature needs to be present in {{server.xml}}.
This is somewhat of an obstacle when using a CI managed Liberty, where a Liberty instance
is downloaded and installed from Maven during the test. Following the work done in
ARQ-1729 it should be relatively easy to add this {{localConnector-1.0}} feature to
{{server.xml}}.
I would like to propose adding a new boolean to the configuration for the managed Liberty
container, and when set to true the Arquillian container will add the mentioned feature
and will thus be able to start Liberty without requiring the user to modify the
installation first.
(I'll look into doing a PR for this)
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)