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

Grigoriy Mikhalkin commented on MNG-6875:
-----------------------------------------

[~khmarbaise] unfortunately, project is closed source. I will try to create 
reproducible example this weekend.

I ran plain command in terminal and use OpenJDK v1.8.0_242

> mvn test keeps failing after changes removed
> --------------------------------------------
>
>                 Key: MNG-6875
>                 URL: https://issues.apache.org/jira/browse/MNG-6875
>             Project: Maven
>          Issue Type: Bug
>            Reporter: Grigoriy Mikhalkin
>            Priority: Major
>
> Maven version: 3.6.0
> Problem: 
> After i created new branch and did few changes to code, i ran `mvn test` and 
> got formatting error:
>  
> {code:java}
> somefile has not been previously formatted. Please format file and commit 
> before running validation!{code}
>  
>  
> I stashed changes, so `git status` didn't displayed any changes between 
> master and branch, and ran `mvn test` again - still got same error.
>  
> Then i switched to master and ran `mvn test` - no errors. Switched to new 
> branch again - still having errors. Just in case, i tried to close my IDE and 
> log out/in - nothing helps.
>  
> From what i understand, even if there some changes in files, that git is not 
> tracking, `mvn test` should return identical results in both cases(as code in 
> master and branch are same). But in reality it's not the case. Probably, 
> maven stores some metadata about git branches, that can cause such behavior?
>  
> Btw, not sure if this is really problem with maven. Maybe someone can point 
> to right places to look at.
>   



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to