Permalink
Commits on May 16, 2013
  1. @stuartwdouglas

    Undertow 1.0.0.Alpha14

    stuartwdouglas committed May 16, 2013
  2. @stuartwdouglas
  3. @stuartwdouglas

    Fixes for latest Undertow

    stuartwdouglas committed May 16, 2013
  4. @bstansberry
  5. @bstansberry

    Revert "WFLY-471 Disabling JAX-RS related tests failing due to upgrad…

    …e to HV 5" due to JAX-RS breakage
    
    This reverts commit 4939e56.
    bstansberry committed May 16, 2013
Commits on May 15, 2013
  1. @rmaucher @n1hility

    First web 8 build.

    rmaucher committed with n1hility May 15, 2013
  2. @rmaucher @n1hility

    Refix tests.

    rmaucher committed with n1hility May 14, 2013
  3. @bstansberry @n1hility
  4. @rmaucher @n1hility

    Revert fix, but add a comment.

    rmaucher committed with n1hility May 13, 2013
  5. @rmaucher @n1hility
  6. @rmaucher @n1hility
  7. @n1hility
  8. @jmesnil @n1hility

    delete manualmode's jbossas-messaging-failover before copy

    HornetQ failover is depending on the file system to lock a file.
    I have seen PRs be aborted because HornetQ live server can not lock this
    file to start (there is no timeout on this lock operation).
    Deleting the directory ensures that the file system's lock (from previous
    runs) is removed.
    jmesnil committed with n1hility May 14, 2013
  9. @jmesnil @n1hility

    [WLFY-509] JMS 2.0 API support

    * update maven GAV for JMS API to:
    
      org.jboss.spec.javax.jms:jboss-jms-api_2.0_spec:1.0.0.Alpha1
    
    * exclude the JMS 1.1 spec artifact from
      org.jboss.ws.cxf:jbossws-cxf-server dependencies
    
    * exclude temporarily the JMS 1.1 spec artifact from
      org.hornetq:hornetq-jms-server and org.hornetq:hornetq-jms-client
      depedencies until HornetQ supports JMS 2.0
    jmesnil committed with n1hility Apr 9, 2013
  10. @jaikiran @n1hility
  11. @stuartwdouglas @n1hility
  12. @stuartwdouglas @n1hility

    Initial HTTP upgrade support for management operations

    This commit adds support for multiplexing the remoting protocol over
    the HTTP management port, removing the need for two seperate management
    ports.
    
    Port 9999 is now no longer present in the default config, and the
    management client will attempt to connect via a HTTP upgrade by
    default.
    stuartwdouglas committed with n1hility Mar 28, 2013
  13. @stuartwdouglas @jaikiran
  14. @stuartwdouglas @jaikiran
  15. @stuartwdouglas @jaikiran
  16. @stuartwdouglas @jaikiran
  17. @stuartwdouglas @jaikiran
  18. @rhusar @jaikiran

    minor javadoc fix (package name)

    rhusar committed with jaikiran May 13, 2013
  19. @asoldano @jaikiran
  20. @dmlloyd
Commits on May 13, 2013
  1. @jmesnil @kabir
  2. @spolti @kabir

    Adjust the smoke test-suit

    spolti committed with kabir May 10, 2013
  3. @spolti @kabir
  4. @spolti @kabir

    A little detail fixed.

    spolti committed with kabir May 9, 2013
  5. @spolti @kabir

    WFLY-330 - Allow defining server http port (and other basic propertie…

    …s) via jvm arguments Obs: This is working, but the final tests on subsystem.xml fails because the final value is not int.
    
    I change the ajp, http, https and remoting.
    These parameteres can be configurated on Jvm Parameters like that:
    -Djboss.http.port=9080
    -Djboss.https.port=9843
    -Djboss.remoting.port=4487
    -Djboss.ajp.port=8010
    
    If not set, the default is configurated.
    
    This is work OK, but the surefire final test fails on:
    org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase
    
    and
    
    org.jboss.as.test.smoke.mgmt.BasicOperationsUnitTestCase
    
    We need adjust the tests Too.
    spolti committed with kabir May 9, 2013
  6. @jamezp @kabir
  7. @jamezp @kabir
  8. @rachmatowicz @kabir
  9. @rachmatowicz @kabir

    [WFLY-245] Disable execution of x-site tests; update server instance …

    …names to use wildfly base name.
    rachmatowicz committed with kabir May 9, 2013
  10. @rachmatowicz @kabir