Permalink
Browse files

Rename profiles arq-wildfly-remote / arq-wildfly-managed --> arq-remo…

…te / arq-managed
  • Loading branch information...
ctomc committed Feb 27, 2017
1 parent 4708064 commit 5b56d3ed0d3608da2763e77761748e321244591d
Showing with 121 additions and 121 deletions.
  1. +2 −2 RELEASE_PROCEDURE.md
  2. +2 −2 bean-validation-custom-constraint/README.md
  3. +2 −2 bean-validation/README.md
  4. +2 −2 cdi-interceptors/README.md
  5. +2 −2 cdi-portable-extension/README.md
  6. +2 −2 cdi-veto/README.md
  7. +4 −4 contacts-jquerymobile/README.md
  8. +2 −2 contacts-jquerymobile/functional-tests/pom.xml
  9. +2 −2 ejb-in-war/README.md
  10. +9 −9 guide/KitchensinkQuickstart.asciidoc
  11. +2 −2 helloworld-html5/README.md
  12. +2 −2 helloworld-html5/functional-tests/pom.xml
  13. +2 −2 helloworld-mbean/README.md
  14. +2 −2 helloworld-ws/README.md
  15. +3 −3 jaxrs-client/README.md
  16. +4 −4 kitchensink-angularjs/README.md
  17. +2 −2 kitchensink-angularjs/functional-tests/pom.xml
  18. +2 −2 kitchensink-ear/README.md
  19. +3 −3 kitchensink-html5-mobile/.cheatsheet.xml
  20. +2 −2 kitchensink-html5-mobile/README.md
  21. +2 −2 kitchensink-jsp/README.md
  22. +2 −2 kitchensink-ml-ear/README.md
  23. +2 −2 kitchensink-ml/README.md
  24. +3 −3 kitchensink/.cheatsheet.xml
  25. +2 −2 kitchensink/README.md
  26. +3 −3 managed-executor-service/README.md
  27. +4 −4 pom.xml
  28. +3 −3 shrinkwrap-resolver/README.md
  29. +2 −2 ...esolver/src/test/java/org/jboss/as/quickstarts/shrinkwrap/resolver/ShrinkwrapImportFromPomIT.java
  30. +2 −2 spring-greeter/README.md
  31. +2 −2 spring-greeter/functional-tests/pom.xml
  32. +2 −2 spring-kitchensink-asyncrequestmapping/README.md
  33. +2 −2 spring-kitchensink-asyncrequestmapping/functional-tests/pom.xml
  34. +2 −2 spring-kitchensink-basic/README.md
  35. +2 −2 spring-kitchensink-basic/functional-tests/pom.xml
  36. +2 −2 spring-kitchensink-controlleradvice/README.md
  37. +2 −2 spring-kitchensink-controlleradvice/functional-tests/pom.xml
  38. +2 −2 spring-kitchensink-matrixvariables/README.md
  39. +2 −2 spring-kitchensink-matrixvariables/functional-tests/pom.xml
  40. +2 −2 spring-kitchensink-springmvctest/README.md
  41. +2 −2 spring-kitchensink-springmvctest/functional-tests/pom.xml
  42. +2 −2 spring-petclinic/README.md
  43. +2 −2 spring-petclinic/functional-tests/pom.xml
  44. +2 −2 tasks-jsf/README.md
  45. +2 −2 tasks-rs/README.md
  46. +2 −2 tasks/README.md
  47. +2 −2 template/README.md
  48. +3 −3 wsat-simple/README.md
  49. +3 −3 wsba-coordinator-completion-simple/README.md
  50. +3 −3 wsba-participant-completion-simple/README.md
View
@@ -6,11 +6,11 @@ Testing the quickstarts
Most of the quickstarts require starting ${product.name.full} in standalone mode. Some require the "standalone-full" profile, some require XTS, some require Postgres and some require other quickstarts to be deployed. Profiles are used in the root POM to separate out these groups, allowing you to test the quickstarts easily. For example, to run those that require only standalone mode:
mvn clean verify wildfly:deploy wildfly:undeploy -Parq-wildfly-remote -P-requires-postgres,-requires-full,-complex-dependencies,-requires-xts
mvn clean verify wildfly:deploy wildfly:undeploy -Parq-remote -P-requires-postgres,-requires-full,-complex-dependencies,-requires-xts
Or, to run those only those quickstarts that require the full profile
mvn clean verify wildfly:deploy wildfly:undeploy -Parq-wildfly-remote -P-requires-postgres,-default,-complex-dependencies,-requires-xts
mvn clean verify wildfly:deploy wildfly:undeploy -Parq-remote -P-requires-postgres,-default,-complex-dependencies,-requires-xts
And so on.
@@ -52,9 +52,9 @@ This quickstart provides Arquillian tests. By default, these tests are configure
2. Open a command prompt and navigate to the root directory of this quickstart.
3. Type the following command to run the test goal with the following profile activated:
mvn clean verify -Parq-wildfly-remote
mvn clean verify -Parq-remote
You can also let Arquillian manage the ${product.name} server by using the `arq-wildfly-managed` profile. For more information about how to run the Arquillian tests, see [Run the Arquillian Tests](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/RUN_ARQUILLIAN_TESTS.md#run-the-arquillian-tests).
You can also let Arquillian manage the ${product.name} server by using the `arq-managed` profile. For more information about how to run the Arquillian tests, see [Run the Arquillian Tests](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/RUN_ARQUILLIAN_TESTS.md#run-the-arquillian-tests).
Investigate the Console Output
@@ -53,9 +53,9 @@ This quickstart provides Arquillian tests. By default, these tests are configure
2. Open a command prompt and navigate to the root directory of this quickstart.
3. Type the following command to run the test goal with the following profile activated:
mvn clean verify -Parq-wildfly-remote
mvn clean verify -Parq-remote
You can also let Arquillian manage the ${product.name} server by using the `arq-wildfly-managed` profile. For more information about how to run the Arquillian tests, see [Run the Arquillian Tests](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/RUN_ARQUILLIAN_TESTS.md#run-the-arquillian-tests).
You can also let Arquillian manage the ${product.name} server by using the `arq-managed` profile. For more information about how to run the Arquillian tests, see [Run the Arquillian Tests](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/RUN_ARQUILLIAN_TESTS.md#run-the-arquillian-tests).
Investigate the Console Output
@@ -99,9 +99,9 @@ This quickstart provides Arquillian tests. By default, these tests are configure
2. Open a command prompt and navigate to the root directory of this quickstart.
3. Type the following command to run the test goal with the following profile activated:
mvn clean verify -Parq-wildfly-remote
mvn clean verify -Parq-remote
You can also let Arquillian manage the ${product.name} server by using the `arq-wildfly-managed` profile. For more information about how to run the Arquillian tests, see [Run the Arquillian Tests](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/RUN_ARQUILLIAN_TESTS.md#run-the-arquillian-tests).
You can also let Arquillian manage the ${product.name} server by using the `arq-managed` profile. For more information about how to run the Arquillian tests, see [Run the Arquillian Tests](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/RUN_ARQUILLIAN_TESTS.md#run-the-arquillian-tests).
Run the Quickstart in Red Hat JBoss Developer Studio or Eclipse
@@ -67,9 +67,9 @@ This quickstart provides Arquillian tests. By default, these tests are configure
2. Open a command prompt and navigate to the root directory of this quickstart.
3. Type the following command to run the test goal with the following profile activated:
mvn clean verify -Parq-wildfly-remote
mvn clean verify -Parq-remote
You can also let Arquillian manage the ${product.name} server by using the `arq-wildfly-managed` profile. For more information about how to run the Arquillian tests, see [Run the Arquillian Tests](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/RUN_ARQUILLIAN_TESTS.md#run-the-arquillian-tests).
You can also let Arquillian manage the ${product.name} server by using the `arq-managed` profile. For more information about how to run the Arquillian tests, see [Run the Arquillian Tests](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/RUN_ARQUILLIAN_TESTS.md#run-the-arquillian-tests).
Investigate the Console Output
View
@@ -55,9 +55,9 @@ This quickstart provides Arquillian tests. By default, these tests are configure
2. Open a command prompt and navigate to the root directory of this quickstart.
3. Type the following command to run the test goal with the following profile activated:
mvn clean verify -Parq-wildfly-remote
mvn clean verify -Parq-remote
You can also let Arquillian manage the ${product.name} server by using the `arq-wildfly-managed` profile. For more information about how to run the Arquillian tests, see [Run the Arquillian Tests](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/RUN_ARQUILLIAN_TESTS.md#run-the-arquillian-tests).
You can also let Arquillian manage the ${product.name} server by using the `arq-managed` profile. For more information about how to run the Arquillian tests, see [Run the Arquillian Tests](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/RUN_ARQUILLIAN_TESTS.md#run-the-arquillian-tests).
Investigate the Console Output
@@ -158,7 +158,7 @@ For example:
OR
#With Tests
mvn clean verify wildfly:deploy -Pminify,arq-wildfly-remote
mvn clean verify wildfly:deploy -Pminify,arq-remote
Run the Arquillian tests
------------------------
@@ -168,7 +168,7 @@ the use of a container. You can activate this test by selecting one of the conta
To run the test in JBoss, first start the container instance. Then, run the test goal with the following profile activated:
mvn clean verify -Parq-wildfly-remote
mvn clean verify -Parq-remote
Run the QUnit tests
-------------------
@@ -202,13 +202,13 @@ To run these tests, you must build the main project as described above.
3. Navigate to the functional-tests/ directory in this quickstart.
4. If you have a running instance of the ${product.name} server, as described above, run the remote tests by typing the following command:
mvn clean verify -Parq-wildfly-remote
mvn clean verify -Parq-remote
5. If you prefer to run the functional tests using managed instance of the ${product.name} server, meaning the tests will start the server for you, type the following command:
_NOTE: For this to work, Arquillian needs to know the location of the ${product.name} server. This can be declared through the `JBOSS_HOME` environment variable or the `jbossHome` property in `arquillian.xml`. See [Run the Arquillian Tests](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/RUN_ARQUILLIAN_TESTS.md#run-the-arquillian-tests) for complete instructions and additional options._
mvn clean verify -Parq-wildfly-managed
mvn clean verify -Parq-managed
Import the Project into an IDE
--------------------------------
@@ -73,7 +73,7 @@
<profiles>
<profile>
<!-- Profile that executes tests in managed JBoss EAP instance. -->
<id>arq-wildfly-managed</id>
<id>arq-managed</id>
<dependencies>
<dependency>
<groupId>org.wildfly.arquillian</groupId>
@@ -85,7 +85,7 @@
<profile>
<!-- Profile that executes tests in remote JBoss EAP instance. -->
<id>arq-wildfly-remote</id>
<id>arq-remote</id>
<dependencies>
<dependency>
<groupId>org.wildfly.arquillian</groupId>
View
@@ -81,9 +81,9 @@ This quickstart provides Arquillian tests. By default, these tests are configure
2. Open a command prompt and navigate to the root directory of this quickstart.
3. Type the following command to run the test goal with the following profile activated:
mvn clean verify -Parq-wildfly-remote
mvn clean verify -Parq-remote
You can also let Arquillian manage the ${product.name} server by using the `arq-wildfly-managed` profile. For more information about how to run the Arquillian tests, see [Run the Arquillian Tests](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/RUN_ARQUILLIAN_TESTS.md#run-the-arquillian-tests).
You can also let Arquillian manage the ${product.name} server by using the `arq-managed` profile. For more information about how to run the Arquillian tests, see [Run the Arquillian Tests](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/RUN_ARQUILLIAN_TESTS.md#run-the-arquillian-tests).
Investigate the Console Output
@@ -714,12 +714,12 @@ image:gfx/eclipse_arquillian_0.png[]
Now, make sure the server is not running (so that the instance started for running the test does not interfere), and then run the tests from the command line by typing:
mvn clean test -Parq-wildfly-managed
mvn clean test -Parq-managed
You should see the server start up, a `test.war` deployed, test executed, and then the results displayed to you on the console:
------------------------------------------------------------------------
$ > mvn clean test -Parq-wildfly-managed
$ > mvn clean test -Parq-managed
[INFO] Scanning for projects...
@@ -851,10 +851,10 @@ Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
As you can see, that didn't take too long (approximately 15s), and is great for running in your QA environment, but if you running locally, you might prefer to connect to a running server. To do that, start up JBoss WildFly (as described in <<GettingStarted-, Getting Started with JBoss Enterprise Application Platform of WildFly>>. Now, run your test, but use the `arq-wildfly-remote` profile:
mvn clean test -Parq-wildfly-remote
mvn clean test -Parq-remote
------------------------------------------------------------------------
$ > mvn clean test -Parq-wildfly-remote
$ > mvn clean test -Parq-remote
[INFO] Scanning for projects...
@@ -925,7 +925,7 @@ Now, locate the Maven panel:
image:gfx/eclipse_arquillian_2.png[]
And activate the `arq-wildfly-managed` profile:
And activate the `arq-managed` profile:
image:gfx/eclipse_arquillian_3.png[]
@@ -939,7 +939,7 @@ image:gfx/eclipse_arquillian_12.png[]
You should see the server start in the Eclipse Console, the test be deployed, and finally the JUnit View pop up with the result (a pass of course!).
We can also run the test in an already running instance of Eclipse. Simply change the active profile to `arq-wildfly-remote`:
We can also run the test in an already running instance of Eclipse. Simply change the active profile to `arq-remote`:
image:gfx/eclipse_arquillian_11.png[]
@@ -1049,7 +1049,7 @@ Now, we need to look at how we select between containers in the `pom.xml`:
in your WildFly instance -->
<!-- This profile will start a new WildFly instance, and
execute the test, shutting it down when done -->
<!-- Run with: mvn clean test -Parq-wildfly-managed -->
<!-- Run with: mvn clean test -Parq-managed -->
<id>arq-wildfly-managed</id> <1>
<dependencies>
<dependency>
@@ -1063,9 +1063,9 @@ Now, we need to look at how we select between containers in the `pom.xml`:
</profile>
<profile>
<!-- An optional Arquillian testing profile that executes
<!-- An optional Arquillian testing profile that executes
tests in a remote WildFly instance -->
<!-- Run with: mvn clean test -Parq-wildfly-remote -->
<!-- Run with: mvn clean test -Parq-remote -->
<id>arq-wildfly-remote</id>
<dependencies>
<dependency>
@@ -125,11 +125,11 @@ To run these tests, you must build the main project as described above.
3. Navigate to the functional-tests/ directory in this quickstart.
4. If you have a running instance of the ${product.name} server, as described above, run the remote tests by typing the following command:
mvn clean verify -Parq-wildfly-remote
mvn clean verify -Parq-remote
5. If you prefer to run the functional tests using managed instance of the ${product.name} server, meaning the tests will start the server for you, type fhe following command:
mvn clean verify -Parq-wildfly-managed
mvn clean verify -Parq-managed
Run the Quickstart in Red Hat JBoss Developer Studio or Eclipse
-------------------------------------
@@ -62,7 +62,7 @@
<profiles>
<profile>
<!-- Profile that executes tests in managed JBoss EAP instance. -->
<id>arq-wildfly-managed</id>
<id>arq-managed</id>
<dependencies>
<dependency>
<groupId>org.wildfly.arquillian</groupId>
@@ -74,7 +74,7 @@
<profile>
<!-- Profile that executes tests in remote JBoss EAP instance. -->
<id>arq-wildfly-remote</id>
<id>arq-remote</id>
<dependencies>
<dependency>
<groupId>org.wildfly.arquillian</groupId>
@@ -113,9 +113,9 @@ This quickstart provides Arquillian tests. By default, these tests are configure
2. Open a command prompt and navigate to the root directory of this quickstart.
3. Type the following command to run the test goal with the following profile activated:
mvn clean verify -Parq-wildfly-remote
mvn clean verify -Parq-remote
You can also let Arquillian manage the ${product.name} server by using the `arq-wildfly-managed` profile. For more information about how to run the Arquillian tests, see [Run the Arquillian Tests](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/RUN_ARQUILLIAN_TESTS.md#run-the-arquillian-tests).
You can also let Arquillian manage the ${product.name} server by using the `arq-managed` profile. For more information about how to run the Arquillian tests, see [Run the Arquillian Tests](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/RUN_ARQUILLIAN_TESTS.md#run-the-arquillian-tests).
Run the Quickstart in Red Hat JBoss Developer Studio or Eclipse
View
@@ -83,9 +83,9 @@ This quickstart provides Arquillian tests. By default, these tests are configure
2. Open a command prompt and navigate to the root directory of this quickstart.
3. Type the following command to run the test goal with the following profile activated:
mvn clean verify -Parq-wildfly-remote
mvn clean verify -Parq-remote
You can also let Arquillian manage the ${product.name} server by using the `arq-wildfly-managed` profile. For more information about how to run the Arquillian tests, see [Run the Arquillian Tests](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/RUN_ARQUILLIAN_TESTS.md#run-the-arquillian-tests).
You can also let Arquillian manage the ${product.name} server by using the `arq-managed` profile. For more information about how to run the Arquillian tests, see [Run the Arquillian Tests](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/RUN_ARQUILLIAN_TESTS.md#run-the-arquillian-tests).
Investigate the Console Output
----------------------------
View
@@ -55,9 +55,9 @@ This quickstart provides Arquillian tests. By default, these tests are configure
2. Open a command line and navigate to the root directory of this quickstart.
3. Type the following command to run the test goal with the following profile activated:
mvn clean verify -Parq-wildfly-remote
mvn clean verify -Parq-remote
You can also let Arquillian manage the ${product.name} server by using the `arq-wildfly-managed` profile. For more information about how to run the Arquillian tests, see [Run the Arquillian Tests](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/RUN_ARQUILLIAN_TESTS.md#run-the-arquillian-tests).
You can also let Arquillian manage the ${product.name} server by using the `arq-managed` profile. For more information about how to run the Arquillian tests, see [Run the Arquillian Tests](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/RUN_ARQUILLIAN_TESTS.md#run-the-arquillian-tests).
Investigate the Console Output
@@ -144,7 +144,7 @@ You can also start the server and deploy the quickstarts or run the Arquillian t
To run the tests in Red Hat JBoss Developer Studio:
You must first set the active Maven profile in project properties to be either `arq-wildfly-managed` for running on managed server or `arq-wildfly-remote` for running on remote server. Then, to run the tests, right click on the project or individual classes and select Run As --> JUnit Test in the context menu.
You must first set the active Maven profile in project properties to be either `arq-managed` for running on managed server or `arq-remote` for running on remote server. Then, to run the tests, right click on the project or individual classes and select Run As --> JUnit Test in the context menu.
Debug the Application
@@ -68,9 +68,9 @@ This quickstart provides Arquillian tests. By default, these tests are configure
2. Open a command line and navigate to the root directory of this quickstart.
3. Type the following command to run the test goal with the following profile activated:
mvn clean verify -Parq-wildfly-remote
mvn clean verify -Parq-remote
You can also let Arquillian manage the ${product.name} server by using the `arq-wildfly-managed` profile. For more information about how to run the Arquillian tests, see [Run the Arquillian Tests](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/RUN_ARQUILLIAN_TESTS.md#run-the-arquillian-tests).
You can also let Arquillian manage the ${product.name} server by using the `arq-managed` profile. For more information about how to run the Arquillian tests, see [Run the Arquillian Tests](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/RUN_ARQUILLIAN_TESTS.md#run-the-arquillian-tests).
Run the Arquillian Functional Tests
@@ -89,11 +89,11 @@ To run these tests, you must build the main project as described above.
3. Navigate to the `functional-tests/` directory in this quickstart.
4. If you have a running instance of the ${product.name} server, as described above, run the remote tests by typing the following command:
mvn clean verify -Parq-wildfly-remote
mvn clean verify -Parq-remote
5. If you prefer to run the functional tests using managed instance of the ${product.name} server, meaning the tests will start the server for you, type fhe following command:
mvn clean verify -Parq-wildfly-managed
mvn clean verify -Parq-managed
Run the Quickstart in Red Hat JBoss Developer Studio or Eclipse
Oops, something went wrong.

0 comments on commit 5b56d3e

Please sign in to comment.