[ 
https://issues.apache.org/jira/browse/MNG-6437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17768154#comment-17768154
 ] 

ASF GitHub Bot commented on MNG-6437:
-------------------------------------

gnodet commented on PR #812:
URL: https://github.com/apache/maven/pull/812#issuecomment-1731994316

   
   > > What am I doing wrong?
   > 
   > The PR only tackles plugin configuration injection, not model 
interpolation. I'll see if/how that can be done...
   
   Actually, this is not the problem.  The problem is that the 
maven-help-plugin is using the `PluginParameterExpressionEvaluator` and not the 
`PluginParameterExpressionEvaluatorV4`.  However, after also enhancing the 
`PluginParameterExpressionEvaluator` class, the next problem is that 
`${session.multiModuleProjectDirectory}` only works on the v4 api, as the 
`MavenSession` does not have the `multiModuleProjectDirectory`, which is 
deprecated.
   After fixing everything that, I do have
   ```
   [INFO] Enter the Maven expression i.e. ${project.groupId} or 0 to exit?:
   ${session.rootDirectory.uri}
   [INFO] 
   <uri>file:///Users/gnodet/work/git/maven/</uri>
   ```
   




> Generic .uri suffix to get the URI representation of any file property
> ----------------------------------------------------------------------
>
>                 Key: MNG-6437
>                 URL: https://issues.apache.org/jira/browse/MNG-6437
>             Project: Maven
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 3.5.4
>            Reporter: Claude Brisson
>            Assignee: Guillaume Nodet
>            Priority: Major
>             Fix For: 4.0.x-candidate, 4.0.0
>
>
> It's impossible to properly generate, for instance, a java policy file which 
> needs files URIs, using either Cargo properties and filtered config files, or 
> just filtered resources.
> In both cases, the problem is the impossibility to generate proper URIs when 
> expanding Maven properties (see also MNG-3760).
> The candidate feature is to add a way to explicitly request the URI when 
> expanding a property by means of a {{.uri}} suffix. The underlying 
> {{getUri()}} method should rely on the correct {{Path#toUri()}} and neither 
> {{File#toUri()}} nor {{File#toString()}}, see the SO reference in MNG-6386.
> For instance:
>  * {{${project.basedir.uri}}} instead of the broken {{${project.baseUri}}} 
> (and of course fix MNG-6436 otherwise it's useless)
>  * {{${project.build.directory.uri}}}
>  * {{${settings.localRepository.uri}}}
>  * etc
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to