ARTEMIS-643 wrong paths in restricted-security-client.policy

user.dir points to current working directory from which the maven command
was invoked. If the command is not invoked from project root directory,
the generated paths are wrong what causes failures of some tests.
This commit is contained in:
Erich Duda 2016-07-20 10:15:31 +02:00 committed by Martyn Taylor
parent d1cfcdffa0
commit f4a0763baf
1 changed files with 2 additions and 2 deletions

View File

@ -23,8 +23,8 @@ grant {
permission java.net.SocketPermission "*:1024-", "connect"; permission java.net.SocketPermission "*:1024-", "connect";
// Note1: normally, we don't need this permission since the applet allows reading jars loaded by the applet // Note1: normally, we don't need this permission since the applet allows reading jars loaded by the applet
// Note2: Which of the following two java.io.FilePermission is necessary depends on the exact Maven command // Note2: Which of the following two java.io.FilePermission is necessary depends on the exact Maven command
permission java.io.FilePermission "${user.dir}/artemis-core-client/target/classes/-", "read"; permission java.io.FilePermission "${activemq.basedir}/artemis-core-client/target/classes/-", "read";
permission java.io.FilePermission "${user.dir}/artemis-core-client/target/artemis-core-client-${project.version}.jar", "read"; permission java.io.FilePermission "${activemq.basedir}/artemis-core-client/target/artemis-core-client-${project.version}.jar", "read";
permission java.util.PropertyPermission "activemq.version.property.filename", "read"; permission java.util.PropertyPermission "activemq.version.property.filename", "read";
permission java.util.PropertyPermission "activemq.artemis.client.global.thread.pool.max.size", "read"; permission java.util.PropertyPermission "activemq.artemis.client.global.thread.pool.max.size", "read";
permission java.util.PropertyPermission "activemq.artemis.client.global.scheduled.thread.pool.core.size", "read"; permission java.util.PropertyPermission "activemq.artemis.client.global.scheduled.thread.pool.core.size", "read";