Home/ Questions/Q 6890583
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-27T06:18:03+00:00

I have a question about the Maven Release plugin. According to the plugin documentation,

  • 0

I have a question about the Maven Release plugin. According to the plugin documentation, one of the steps followed by the release:prepare goal is :

  • Check that there are no uncommitted changes in the sources.

I understand the importance of this point. Let’s take as example the case of a multimodules project developed by many developers. Every developer has done its part of the work, and the project is ready to be released. But, only one person on one machine will do the release, and I think that checking the presence of uncommitted changes in the working copy of the person performing the release isn’t enough.

Maybe there are uncommitted changes in the working copies of other developer that also worked on the project? Am I missing something (I mean, is this really a problem? If yes, is there a way to do these verifications with Maven or the working copies of the other developers must be checked manually?)

Thanks

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The reason it checks for uncommitted changes in the sources is so that the released binary corresponds to the source code in the repository.

    If there were uncommitted changes on the machine doing the release, then the binaries wouldn’t correspond to the source.

    If other developers have uncommitted changes, that doesn’t matter, because their changes won’t end up in the binary.

    • 0