Tips
-
-
- Starting mutiple containers conditionally +
- Starting multiple containers conditionally
- Starting Tomcat in security mode
- How to get Tomcat 5 working with the Java 5 XML Parsers
- How to use the ZIP or TAR.GZ distributions provided by servers on a Maven repository @@ -414,8 +414,13 @@
java.security.managerjava.security.policy
@@ -490,7 +495,13 @@ - JDK 11. Please note that older or newer versions of the JDK cannot build all of Codehaus Cargo, and hence should not be used to release new versions.
- Maven 3.2.5 or newer, though it is for sure a good idea to use the latest Maven version available.
- With Maven 3.8.1 onwards, you might have someArtifactTransferExceptions with the OW2 snapshot repository (which was defined as HTTP over a decade back). You can work around these using the instructions in the chapterArtifactTransferExceptionwith Maven 3.8.1 onwards.
+ With Maven 3.8.1 onwards, you might have some - An access to the Sonatype Nexus instance as a manager for the Codehaus Cargo project. Read more about it on the Initial Setup section of the OSSRH guide.
- The GNU privacy guard (GPG) installed on your machine and at least one secret key.
-
@@ -323,7 +323,7 @@
- All containers with a public download link are automatically tested by the Continous Integration system every time there is a code change:
- Open the CI page and click on the latest build -
- First, check if the overall status is PASSED +
- First, check if the overall status is PASSED
- Then, click on the build and check for the command with
cat core/samples/java/containers.login it (on all CI jobs for the last build, as we split the container tests into multiple parallel jobs to reduce the total time required for integration testing). It should indicate status0for all containers:
- For non-publicly-downloadable containers, tests need to be done on your computer. These include:
diff --git a/cargo/Tomcat+9.x.html b/cargo/Tomcat+9.x.html
index a2e4051c07..fb0e4efcf4 100644
--- a/cargo/Tomcat+9.x.html
+++ b/cargo/Tomcat+9.x.html
@@ -2033,7 +2033,7 @@
For
Tested On
This container is automatically tested by the Continous Integration system every time there is a code change.
- The server used for tests is downloaded from: https://repo.maven.apache.org/maven2/org/apache/tomcat/tomcat/9.0.81/tomcat-9.0.81.zip
Before you start
- All containers with a public download link are automatically tested by the Continous Integration system every time there is a code change:
Starting multi
Starting Tomcat in security mode
-
Warning: the proposed solution only works on Linux, see MNG-6437
-Cargo supports passing system properties Passing system properties. So, to start Tomcat in security mode, you need to specify two system properties:
+Warning: the proposed solution only works on Linux, see MNG-6437.
+Cargo supports passing system properties. So, to start Tomcat in security mode, you need to specify two system properties:
How to ge
How to run a Jetty webapp under a Java Security Manager
Tip submitted by Claude Brisson
-UPDATE: This solution doesn't work on Windows for now: @cargo.repository@, @cargo.container@ and @cargo.webapp@ should be URIs and not paths
This solution doesn't work on Windows for now: @cargo.repository@, @cargo.container@ and @cargo.webapp@ should be URIs and not paths.
Jetty 8.x has its own security manager, which can be enabled by enabling the jetty-policy.xml module, but it will search for its policies files under a lib/policy directory located in the same location as start.jar, inaccessible to Cargo's custom configuration folders.
So we'll stick to the Jetty 9.x container. In Jetty 9.x there is no internal security manager, so we'll directly run Jetty 9.x under the standard java.lang.SecurityManager.
We'll first need a mywebapp.policy policy file. It gives rights to Jetty itself:
Prerequisites
ArtifactTransferExceptions with the OW2 snapshot repository (which was defined as HTTP over a decade back). You can work around these using the instructions in the chapter ArtifactTransferException with Maven 3.8.1 onwards.