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

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

cstamas opened a new pull request, #1604:
URL: https://github.com/apache/maven/pull/1604

   This is a bug how in Maven different paths are
   detected and handled.
   
   Maven 4 is not affected.
   
   ---
   
   https://issues.apache.org/jira/browse/MNG-8165
   
   Following this checklist to help us incorporate your
   contribution quickly and easily:
   
    - [ ] Make sure there is a [JIRA 
issue](https://issues.apache.org/jira/browse/MNG) filed
          for the change (usually before you start working on it).  Trivial 
changes like typos do not
          require a JIRA issue. Your pull request should address just this 
issue, without
          pulling in other changes.
    - [ ] Each commit in the pull request should have a meaningful subject line 
and body.
    - [ ] Format the pull request title like `[MNG-XXX] SUMMARY`,
          where you replace `MNG-XXX` and `SUMMARY` with the appropriate JIRA 
issue.
    - [ ] Also format the first line of the commit message like `[MNG-XXX] 
SUMMARY`.
          Best practice is to use the JIRA issue title in both the pull request 
title and in the first line of the commit message.
    - [ ] Write a pull request description that is detailed enough to 
understand what the pull request does, how, and why.
    - [ ] Run `mvn clean verify` to make sure basic checks pass. A more 
thorough check will
          be performed on your pull request automatically.
    - [ ] You have run the [Core IT][core-its] successfully.
   
   If your pull request is about ~20 lines of code you don't need to sign an
   [Individual Contributor License 
Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure
   please ask on the developers list.
   
   To make clear that you license your contribution under
   the [Apache License Version 2.0, January 
2004](http://www.apache.org/licenses/LICENSE-2.0)
   you have to acknowledge this by using the following check-box.
   
    - [ ] I hereby declare this contribution to be licenced under the [Apache 
License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
   
    - [ ] In any other case, please file an [Apache Individual Contributor 
License Agreement](https://www.apache.org/licenses/icla.pdf).
   
   [core-its]: https://maven.apache.org/core-its/core-it-suite/
   




> Maven does not find extensions for -f when current dir is root
> --------------------------------------------------------------
>
>                 Key: MNG-8165
>                 URL: https://issues.apache.org/jira/browse/MNG-8165
>             Project: Maven
>          Issue Type: Bug
>    Affects Versions: 3.9.8
>            Reporter: Charles Oliver Nutter
>            Assignee: Tamas Cservenak
>            Priority: Major
>             Fix For: 3.9.9
>
>
> There seems to be a problem with how Maven locates the `.mvn/extensions.xml` 
> file if you run it at root. This appears to be breaking JRuby's user of 
> Polyglot Maven when running in a Docker container 
> (https://github.com/jruby/jruby/issues/7059)
> To reproduce (see long output at 
> https://github.com/jruby/jruby/issues/7059#issuecomment-2190953877):
>  # Be at the root of the filesystem
>  # Create `.mvn/extensions.xml` file that enables Polyglot Ruby
>  # Create a file `blah/pom.rb` containing a `#` that will be rejected as 
> invalid pom XML.
>  # Execute the file with `mvn -f blah/pom.rb clean`
> The expected behavior should be that it fills in a dummy group and artifact 
> ID for the blank ruby pom file and executes it correctly.
> Instead, it does not load Polyglot Ruby and attempts to parse the file as XML.
> I suspect that work done in [https://github.com/apache/maven/pull/94] for 
> MNG-5889 may have introduced this bug. Prior to that issue, Maven would 
> always look in the current directory for `.mvn` (which is root in this case), 
> which would allow this scenario to work. The fix was to have Maven look first 
> in the target directory and then in parent directories, but now it never 
> looks at root (`/.mvn`).



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

Reply via email to