Yes, people who created capabilities need to file the descriptions.

Myself included it seems. :(

-- 
Brian Stansberry
Manager, Senior Principal Software Engineer
JBoss by Red Hat



On Jun 29, 2016, at 1:31 PM, Claudio Miranda <claudio@claudius.com.br> wrote:

Hi, looking at current wildfly capabilities, I see the following

org.wildfly.batch.configuration
org.wildfly.batch.job.repository
org.wildfly.batch.thread.pool
org.wildfly.clustering.infinispan.cache-container.cache.store.jdbc.data-source
org.wildfly.clustering.infinispan.cache-container.cache.store.remote.outbound-socket-binding
org.wildfly.clustering.protocol.socket-binding
org.wildfly.clustering.singleton.default-policy
org.wildfly.clustering.singleton.policy
org.wildfly.clustering.singleton.singleton-policy.election-policy.socket-binding-preference
org.wildfly.clustering.transport.diagnostics-socket-binding
org.wildfly.data-source
org.wildfly.domain.profile
org.wildfly.domain.server-config
org.wildfly.domain.server-group
org.wildfly.domain.socket-binding-group
org.wildfly.extension.sar-deployment
org.wildfly.extension.undertow.handler
org.wildfly.io.buffer-pool
org.wildfly.io.max-threads
org.wildfly.io.worker
org.wildfly.jsr77
org.wildfly.management.jmx
org.wildfly.management.jmx.remote
org.wildfly.management.native-interface
org.wildfly.network.interface
org.wildfly.network.outbound-socket-binding
org.wildfly.network.socket-binding
org.wildfly.remoting.endpoint
org.wildfly.request-controller
org.wildfly.security
org.wildfly.transactions
org.wildfly.undertow.listener

But they differ from the https://github.com/wildfly/wildfly-capabilities/

Do you plan to update the git repo ?

--
 Claudio Miranda

claudio@claudius.com.br
http://www.claudius.com.br
_______________________________________________
wildfly-dev mailing list
wildfly-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev