WildFlyCore

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
AS7-682

was: 12e5162f8509ea0edb55a7a25138026fb0c3cb04

name value completion for standalone

was: 118b23e626cb7b3a1a4f72e90260c539444bee27

Ensure JMX sockets are registered as bound

was: c66e220cd224142a1949992fc76008c1842f5a05

Expose bound-address and bound-port metrics for SocketBindings

was: 35a4abaa18f89a76e0abce6b698b6bb351f6569b

Ensure sockets created by SocketBinding end up in the named registry

was: e7a91ac6b63809dd08a2e5d15b481219a1bc1358

AS7-679 updated help files for deploy/undeploy, tab-completion for deploy name argument

was: e9dd1abc718645621eb0a363b7351b66cf6eed8a

    • -15
    • +0
    /cli/src/main/java/org/jboss/as/cli/Util.java
    • -16
    • +29
    /cli/src/main/resources/help/deploy.txt
    • -9
    • +24
    /cli/src/main/resources/help/undeploy.txt
[AS7-616] Let jboss-as-protocol notify clients of server-side failures

was: aa29d6d377d1b856393044ebd72cf8974bddd0d9

AS7-679 undeploy changed --all-server-groups to --all-relevant-server-groups

was: e9917ff52df030323ac3c9f636d2a649e619f2cb

    • -2
    • +174
    /cli/src/main/java/org/jboss/as/cli/Util.java
[AS7-693] Persist server-group deployment's enabled flag Handler server-group deployment marshalling separately

was: 9c8a8aabf1170dad495a748904ed645cb8c5fe09

AS7-431: fixed full-replace and make sure the PathContentServitor service is removed

was: fd2d9bc1d601f835930dd7fcc645793c531ac10e

AS7-679 undeploy --keep-content and deploy --name=app-in-repo

was: 9b9bfe62785299b84ef1f3b3dd344a5f5b5fe14f

AS7-666 added --all-server-groups as an alternative to --server-groups=group1,group2... to deploy/undeploy

was: cece0eeb2043bbc8acb047ca94f293ac3334ffbc

AS7-675: handle attributes for jvm:add

was: 4bffadfd7bdbe18e6d2bc0dff21aefd6e85eba6a

0 is a valid value for socket-binding-port-offset

was: 54d4c179411797dccc0cf9ec5f99b6de5bb9bc1c

[AS7-431] Create the correct operation structure for a domain mode deployment add

[AS7-431] Use the correct content add structure in DomainDeploymentManager

[AS7-431] Fix parsing and marshalling issues

[AS7-431] Use correct operation structure when HostController starts a server

[AS7-431] Use current JIRA id in failure message

was: 81a24f0ac1da4af49913c3b8e0ed2d09718b4970

AS7-666 tab completion for server groups for deploy/undeploy

was: 0c3a06ef184d0abef21a0ab0d85d1a52a1b50e09

    • -0
    • +23
    /cli/src/main/java/org/jboss/as/cli/Util.java
AS7-431: content add operation handling for the domain

was: ebd340304bfafbdbf6365339c467bb2be88888b6

AS7-666 evil domain deploy support

was: d630524128c109e25870585d20c3aaba907858ed

    • -0
    • +48
    /cli/src/main/java/org/jboss/as/cli/Util.java
Re-add the socket group includes add/remove handlers wrongly deleted in 69afcb91cd3abd8c9c6fc31634fba066c46461c6 and add to the model

was: f9771aeb31aa6560af564bffbbbf9c7be1609fc1

[AS7-451] removing dependencies on MSC deprecated classes

was: 48d4d6389ad8903dbc303251c63727a2280e045a

updated help files wrt '--' argument convention, added arg value completion for history command

was: c37d93afb36343fe3c70378cb2f164f03fbe2c9e

    • -2
    • +2
    /cli/src/main/resources/help/deploy.txt
    • -1
    • +1
    /cli/src/main/resources/help/history.txt
AS7-431: unwarred welcome.war and handling exploded unmanaged content

was: 534c9569d7f929cc854da099c0c3cf191b655b92

Tidy up socket-binding-group, use 'includes' instead of 'include'

was: 69afcb91cd3abd8c9c6fc31634fba066c46461c6

AS7-636 context dependent command argument completion and value completion

was: 8da605ec62976f25aae3709d95e042dfed97aceb

    • -0
    • +81
    /cli/src/main/java/org/jboss/as/cli/CommandArgument.java
    • -0
    • +76
    /cli/src/main/java/org/jboss/as/cli/ParsedArguments.java
  1. … 14 more files in changeset.
Use 'includes' for attributes

was: bac2192028ef8ceebaa099dbe7fb15e565a6e88b

Revisit the profile descriptors, and settle on 'include' List<String> as the name of the includes

was: 178fe56349f855f304c39ee8df44dd3cb3500421

JBAS-9020: allow unmanaged content items

was: d441ecee47404e66207e9797d50c40c65c781560

JBAS-9020: fix writing back standalone.xml

was: 9a2ba175631b4f62ec93c72ab0ca00866c2a2528

More fixes to Beta4

was: ea470d5faec3d84eba0d25ee0fb17b24dc420a07

JBAS-9020: remove usage of dmr from runtime operations and make the content come in via a service

was: feecd19f7cc501d98c66add72917babdbeca0dce