Description Alex Pogrebnyak 2011-06-30 18:33:07 EDT

Build Identifier: 20110615-0604

m2e should only modify this file on project import and 'Update Project Configuration'.

In reality this file gets modified by a number of outside factors.

1. On POM update
2. On Project->Clean
3. Because it rains outside

Also, it insists on adding 'archiveName' parameter to <dependent-module> element of contributing projects.  I.e.

<dependent-module archiveName="my-depnedency-0.0.1-SNAPSHOT.jar" deploy-path="/WEB-INF/lib" handle="module:/resource/my-dependency/my-dependency">
    <dependency-type>uses</dependency-type>
</dependent-module>

Moreover it keeps appending version number to the participating jars.  This is totally unnecessary.  In fact if you omit archavieName completely it will assemble the dependency jar without version number in its name and will publish it correctly to WEB-INF/lib.

Needless to say, that if this file contains version number, now there is a problem when the project's version is incremented.

Because of your own recommendations to keep various '.settings' files under source control, I don't want somebody junior to overwrite this very sensitive descriptor with his/her changes and then chase this problem for days ( believe me this happened to me before ).

I understand that you try to cater to many environments, but if you could keep your modifications of this file to some predictable points, it would help tremendously.


Reproducible: Always