You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+24-10Lines changed: 24 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,20 +36,34 @@ I don't plan to write any formal documentation, read the code. The [Java EE 7 Es
36
36
37
37
### IntelliJ ###
38
38
39
-
### Cargo ###
39
+
### Arquillian ###
40
40
41
-
Samples can be deployed and run on WildFly and GlassFish 4.
41
+
Samples are tested on Wildfly and GlassFish using the Arquillian ecosystem.
42
42
43
-
Make sure to edit ``glassfish.home`` or ``wildfly.home`` property value in the top-level ``pom.xml`` to point to your local GlassFish or Wildfly directory respectively. This is achieved using Maven profiles. Include ``-P wildfly`` on mvn CLI to run the samples on WildFly and ``-P glassfish`` fo GlassFish.
43
+
Only one profile can be active at a given time otherwise there will be dependency conflicts.
44
44
45
-
Only one profile can be active at a given time otherwise there will be port conflicts.
45
+
There are 3 available profiles:
46
46
47
-
1. In one terminal, ``mvn cargo:run`` at the top-level directory to start container
48
-
2. In the sample directory
49
-
1.``mvn package cargo:deploy`` to deploy for the first time
50
-
2.``mvn package cargo:redeploy`` to redeploy subsequently
51
-
3.``mvn cargo:undeploy`` to undeploy
52
-
3. Check for application name printed by Cargo output. Access the application at http://localhost:8080/<APP-NAME>
47
+
*``wildfly-managed-arquillian``
48
+
The default profile and it will install a Wildfly server and start up the server pr sample.
49
+
Useful for CI servers.
50
+
51
+
*``wildfly-remote-arquillian``
52
+
This profile requires you to start up a Wildfly server outside of the build. Each sample will then
53
+
reuse this instance to run the tests.
54
+
Useful for development to avoid the server start up cost pr sample.
55
+
56
+
*``glassfish-embedded-arquillian``
57
+
This profile uses the GlassFish embedded server and runs in the same JVM as the TestClass.
58
+
Useful for development, but has the downside of server startup pr sample.
59
+
60
+
To run them in the console do:
61
+
62
+
1. In the terminal, ``mvn -Pwildfly-managed-arquillian`` at the top-level directory to start the tests
63
+
64
+
When developing and runing them from IDE, remember to activate the profile before running the test.
65
+
66
+
To learn more about Arquillian please refer to the [Arquillian Guides](http://arquillian.org/guides/)
0 commit comments