diff --git a/cargo/Maven+3+Plugin+Tips.html b/cargo/Maven+3+Plugin+Tips.html index 34cfa0de85..c304130f41 100644 --- a/cargo/Maven+3+Plugin+Tips.html +++ b/cargo/Maven+3+Plugin+Tips.html @@ -414,7 +414,7 @@
Warning: the proposed solution only works on Linux, see MNG-6437
+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:
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
UPDATE: 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:
-
cat core/samples/java/containers.log
in 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 status 0
for all containers: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/10.1.13/tomcat-10.1.13.zip
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/11.0.0-M11/tomcat-11.0.0-M11.zip
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/8.5.93/tomcat-8.5.93.zip
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.80/tomcat-9.0.80.zip