Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
3.5.4
-
None
-
None
-
Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 2018-06-17T20:33:14+02:00)
Maven home: D:\Entwicklung\Programme\apache-maven-3.5.4
Java version: 1.8.0_172, vendor: Oracle Corporation, runtime: C:\Program Files\Java\jdk1.8.0_172\jre
Default locale: de_DE, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 2018-06-17T20:33:14+02:00) Maven home: D:\Entwicklung\Programme\apache-maven-3.5.4 Java version: 1.8.0_172, vendor: Oracle Corporation, runtime: C:\Program Files\Java\jdk1.8.0_172\jre Default locale: de_DE, platform encoding: Cp1252 OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
Description
This has been reported in https://www.mail-archive.com/dev@velocity.apache.org/msg07854.html.
Consider you have a policy file in src/test/resources which you want to pass to the VM with Cargo and Jetty. The security manager accepts only URIs, but ${project.baseUri} is only interpolated within the POM. This should be available to Maven Filtering too.