[jira] [Commented] (MNG-6875) mvn test keeps failing after changes removed

["Karl Heinz Marbaise (Jira)" <ji...@apache.org>]

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

Karl Heinz Marbaise commented on MNG-6875:
------------------------------------------

First it would be helpful to describe on which project you are working or even better if you have project which can be used to reproduce the behaviour. Furthermore are you running on plain command line or within an IDE ? Which Java version do you use?. Apart from that Maven does not store any kind of metadata about Git branches ...

If you have switched from one branch to another it could be the case that older plugin version might not identifying to rebuild parts (depends on the plugin versions you are using) but I can't tell you for sure cause I don't have the information .....

> 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)