Stefan Bodewig wrote:
If somebody adds a POM for release 1.0 of a project X I am the release
manager of, do you really expect me to release 1.0.1 because this
other guy made a mistake in the POM which probably was created without
even consulting with me?
Exactly.
The perfect world is fine if you are controlling the release, you can
(should) be psycho-rigid for your release. But the fact of the matter is
that a repository is full of things and especially full of things where
dependencies where not described or described in way that might be limited
Can I expect everybody in the world to ship binaries with a super nice
ivy.xml.
No.
So someone would have to do it or I would have to do it. So I may do it
for version X and then revisit later with the same version X because
actually just the process of 'discovering' the 'real' dependencies of
the project and describing the dependencies takes time. The metadata
might also be 'not pretty' at first... like missing url, license,
description and so on.
So metadata do change.
