[
https://issues.jboss.org/browse/JBIDE-25291?page=com.atlassian.jira.plugi...
]
Aurélien Pupier commented on JBIDE-25291:
-----------------------------------------
{quote}Are these flags standard to all images?{quote}
it is standard to all images based on fabric8
{quote}I'm very concerned that the openshift server adapter design is going to be
flooded with a huge number of use-case-specific crap that isn't applicable to other
situations. This stuff as a whole really needs to be spec'd out. A list of all things
an openshift server should be able to do, and a set of different behavior for each task
need to be outlined. Then implementations can be made.
Right now it seems everything is 100% ad-hoc and it's giving me a very dirty
feeling.{quote}
it is the same than for all work done with OpenShift server adapters. The Node;js and EAP
images used by Red Hat are trying to define some conventions. These conventions for
Jolokia seems to be coherent, the implementor ([~rhuss]) of Jolokia has worked to create
the fabric8 images using Jolokia. So I think that we can take it as convention.
Read Jolokia port from image configuration instead of hardcoded to
default value
--------------------------------------------------------------------------------
Key: JBIDE-25291
URL:
https://issues.jboss.org/browse/JBIDE-25291
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: jmx, openshift
Affects Versions: 4.5.0.Final, 4.5.1.AM3
Reporter: Aurélien Pupier
see
https://hub.docker.com/r/fabric8/s2i-java/ for classical use case:
{noformat}
AB_JOLOKIA_PORT : Port to use (Default: 8778)
{noformat}
might worth to also take care of all other parameters?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)