All Downloads are FREE. Search and download functionalities are using the official Maven repository.

Download all versions of oxalis-integration-test JAR files with all dependencies

Search JAR files by class name

oxalis-integration-test from group no.difi.oxalis (version 4.0.0-RC2)

Oxalis integration test. Compiles and packages everything, after which the web container is started in the pre-integration-test phase, the .war file is deployed and the tests are executed in the integration-test phase. After the tests have been executed, the web container is stopped in the post-integration-test phase. The reason for using failsafe is the fact that Surefire would fail the build in the integration-test phase, without taking down the server in the post-integration-test phase. This implementation uses Tomcat, but you may change this to your liking. See http://cargo.codehaus.org/Maven2+plugin for more information.

Group: no.difi.oxalis Artifact: oxalis-integration-test

 

0 downloads
Artifact oxalis-integration-test
Group no.difi.oxalis
Version 4.0.0-RC2
Last update 01. March 2017
Tags: using reason have test compiles change everything deployed build cargo been plugin after executed more tomcat fail would tests file integration oxalis failsafe information post packages your liking without maven2 taking that surefire fact which stopped http container implementation codehaus server uses started down phase this
Organization Norwegian Agency for Public Management and eGovernment (Difi)
URL https://github.com/difi/oxalis
License not specified
Dependencies amount 7
Dependencies oxalis-as2, oxalis-inbound, oxalis-outbound, oxalis-statistics, httpclient, jcl-over-slf4j, logback-classic,
There are maybe transitive dependencies!

oxalis-integration-test from group no.difi.oxalis (version 4.0.0-RC1)

Oxalis integration test. Compiles and packages everything, after which the web container is started in the pre-integration-test phase, the .war file is deployed and the tests are executed in the integration-test phase. After the tests have been executed, the web container is stopped in the post-integration-test phase. The reason for using failsafe is the fact that Surefire would fail the build in the integration-test phase, without taking down the server in the post-integration-test phase. This implementation uses Tomcat, but you may change this to your liking. See http://cargo.codehaus.org/Maven2+plugin for more information.

Group: no.difi.oxalis Artifact: oxalis-integration-test

 

0 downloads
Artifact oxalis-integration-test
Group no.difi.oxalis
Version 4.0.0-RC1
Last update 24. May 2016
Tags: using reason have test compiles change everything deployed build cargo been plugin after executed more tomcat fail would tests file integration oxalis failsafe information post packages your liking without maven2 taking that surefire fact which stopped http container implementation codehaus server uses started down phase this
Organization not specified
URL Not specified
License not specified
Dependencies amount 7
Dependencies oxalis-as2, oxalis-inbound, oxalis-outbound, oxalis-sql, oxalis-jdbc-dbcp, httpclient, logback-classic,
There are maybe transitive dependencies!

oxalis-integration-test from group no.difi.oxalis (version 3.2.0)

Oxalis integration test. Experiment to see if running with embedded Tomcat will work. The idea is to compile and package everything, after which the web container is started in the pre-integration-test phase, the .war file is deployed and the tests are executed in the integration-test phase. After the tests have been executed, the web container is stopped in the post-integration-test phase. The reason for using failsafe is the fact that Surefire would fail the build in the integration-test phase, without taking down the server in the post-integration-test phase. This implementation uses Tomcat, but you may change this to your liking. See http://cargo.codehaus.org/Maven2+plugin for more information.

Group: no.difi.oxalis Artifact: oxalis-integration-test

 

0 downloads
Artifact oxalis-integration-test
Group no.difi.oxalis
Version 3.2.0
Last update 23. May 2016
Tags: using test reason change everything package plugin been after more tomcat would fail file experiment oxalis failsafe work information liking without embedded that surefire stopped http container codehaus will phase this idea have deployed build running cargo executed tests integration compile with post your maven2 taking which fact implementation uses server down started
Organization not specified
URL Not specified
License not specified
Dependencies amount 8
Dependencies httpclient, oxalis-as2, logback-classic, oxalis-inbound, oxalis-outbound, oxalis-sql, oxalis-jdbc-dbcp, webservices-rt,
There are maybe transitive dependencies!

oxalis-integration-test from group no.difi.oxalis (version 3.2.0-RC1)

Oxalis integration test. Experiment to see if running with embedded Tomcat will work. The idea is to compile and package everything, after which the web container is started in the pre-integration-test phase, the .war file is deployed and the tests are executed in the integration-test phase. After the tests have been executed, the web container is stopped in the post-integration-test phase. The reason for using failsafe is the fact that Surefire would fail the build in the integration-test phase, without taking down the server in the post-integration-test phase. This implementation uses Tomcat, but you may change this to your liking. See http://cargo.codehaus.org/Maven2+plugin for more information.

Group: no.difi.oxalis Artifact: oxalis-integration-test

 

0 downloads
Artifact oxalis-integration-test
Group no.difi.oxalis
Version 3.2.0-RC1
Last update 14. March 2016
Tags: using test reason change everything package plugin been after more tomcat would fail file experiment oxalis failsafe work information liking without embedded that surefire stopped http container codehaus will phase this idea have deployed build running cargo executed tests integration compile with post your maven2 taking which fact implementation uses server down started
Organization not specified
URL Not specified
License not specified
Dependencies amount 8
Dependencies httpclient, oxalis-as2, logback-classic, oxalis-inbound, oxalis-outbound, oxalis-sql, oxalis-jdbc-dbcp, webservices-rt,
There are maybe transitive dependencies!

oxalis-integration-test from group no.difi.oxalis (version 4.0.0-BETA1)

Oxalis integration test. Compiles and packages everything, after which the web container is started in the pre-integration-test phase, the .war file is deployed and the tests are executed in the integration-test phase. After the tests have been executed, the web container is stopped in the post-integration-test phase. The reason for using failsafe is the fact that Surefire would fail the build in the integration-test phase, without taking down the server in the post-integration-test phase. This implementation uses Tomcat, but you may change this to your liking. See http://cargo.codehaus.org/Maven2+plugin for more information.

Group: no.difi.oxalis Artifact: oxalis-integration-test

 

0 downloads
Artifact oxalis-integration-test
Group no.difi.oxalis
Version 4.0.0-BETA1
Last update 01. March 2016
Tags: using reason have test compiles change everything deployed build cargo been plugin after executed more tomcat fail would tests file integration oxalis failsafe information post packages your liking without maven2 taking that surefire fact which stopped http container implementation codehaus server uses started down phase this
Organization not specified
URL Not specified
License not specified
Dependencies amount 7
Dependencies oxalis-as2, oxalis-inbound, oxalis-outbound, oxalis-sql, oxalis-jdbc-dbcp, httpclient, logback-classic,
There are maybe transitive dependencies!

oxalis-integration-test from group no.difi.oxalis (version 3.1.1)

Oxalis integration test. Experiment to see if running with embedded Tomcat will work. The idea is to compile and package everything, after which the web container is started in the pre-integration-test phase, the .war file is deployed and the tests are executed in the integration-test phase. After the tests have been executed, the web container is stopped in the post-integration-test phase. The reason for using failsafe is the fact that Surefire would fail the build in the integration-test phase, without taking down the server in the post-integration-test phase. This implementation uses Tomcat, but you may change this to your liking. See http://cargo.codehaus.org/Maven2+plugin for more information.

Group: no.difi.oxalis Artifact: oxalis-integration-test

 

0 downloads
Artifact oxalis-integration-test
Group no.difi.oxalis
Version 3.1.1
Last update 13. August 2015
Tags: using test reason change everything package plugin been after more tomcat would fail file experiment oxalis failsafe work information liking without embedded that surefire stopped http container codehaus will phase this idea have deployed build running cargo executed tests integration compile with post your maven2 taking which fact implementation uses server down started
Organization not specified
URL Not specified
License not specified
Dependencies amount 8
Dependencies httpclient, oxalis-as2, logback-classic, oxalis-inbound, oxalis-outbound, oxalis-sql, oxalis-jdbc-dbcp, webservices-rt,
There are maybe transitive dependencies!



Page 1 from 1 (items total 6)


© 2015 - 2024 Weber Informatics LLC | Privacy Policy