Eclipse Krazo is an implementation of action-based MVC specified by Jakarta MVC 2.0. It builds on top of Jakarta RESTful Webservices and currently contains support for RESTEasy and Jersey with a well-defined SPI for other implementations.
Eclipse Krazo has configurations to run the testsuite against a bunch of application servers like WildFly, Payara, Glassfish or Liberty. The following sections describe how you test Eclipse Krazo against them. At the moment, we test against following servers:
To run the Krazo testsuite with Eclipse Glassfish, you need to follow these steps:
glassfish6/glassfish/bin/startserv
testsuite
package of Eclipse Krazo and execute mvn clean integration-test -Ptestsuite-glassfish
To run the Krazo testsuite with WildFly, you need to run testsuite-wildfly-managed
or follow these steps:
sh standalone.sh --debug
. This enables you to remote-debug the Arquillian tests.testsuite
package of Eclipse Krazo and execute mvn clean integration-test -Ptestsuite-wildfly
To run the Krazo testsuite with OpenLiberty, you just need to run mvn verify -P testsuite-liberty-managed
. Maven
will download and configure an instance of OpenLiberty for you.
In this case, ensure that your local SNAPSHOTS are the newest version of Krazo. Most of time, this solves the problem.
To check if a dependency requires a CQ, the command mvn org.eclipse.dash:license-tool-plugin:license-check -Dskip.dash=false
can be executed. This creates a summary file in target/dash/summary
.