Am 2018-06-28 um 14:34 schrieb Claude Brisson:
*you* spotted the bug and the entire Cargo variables are /crap/,
unusable for policy files. The produce is java.io.File#toString()
which does not work for URIs. The output is
"file:D:\Projects\veltools...". This is like MNG-6386. There is no way
to fix that, but only in Cargo by adding to each property a
subproperty '.uri' via File.toPath().toUri().
I commented out the security manager sections in showcase's pom.xml.
It's not even possible to generate the policy file as a filtered resource:
- there is a ${project.baseUri} property, but not taken into account by
the Maven resources filter (you can workaround it by assigning a new
property)
https://issues.apache.org/jira/browse/MNG-6436
- there is no such thing as ${localSettings.repositoryUri} (which isn't
even a File but a String, is it?)
It looks like it's rather a missing Maven feature to let users add an
'.uri' suffix to any File property (and to do it accordingly to RFC
3986) or to anything that is known to be the string representation of a
path.
That is true, though it has never been requested. Definitvely worth to
consider for 4.0.0.
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
For additional commands, e-mail: dev-h...@velocity.apache.org
