On 5/07/2006 10:54 AM, David Jencks wrote:
I think the process is somewhat broken and that the maven team is being
far too strict about changing broken poms that were in fact installed by
the maven team, not supplied by the project. (xmlbeans is the case in
point for me). I also think that traceability of where poms came from
and under what auspices they are added to either the repository svn tree
or ibiblio is sorely lacking. (again xmlbeans being my sore spot). We
are in the situation where a pom appeared from an unknown source, is
wrong, did not come from the project, and can't be updated. Much as I
like maven it's hard for me to see how this is going to lead to success.
David,
I thought we'd agreed to fix that up? I can't find the issue on it other
than http://jira.codehaus.org/browse/MEV-406 which is not the one I
recall (that one is about stax which is a whole other problem beyond the
scope of Maven too).
- Brett
--
Brett Porter <[EMAIL PROTECTED]>
Apache Maven - http://maven.apache.org/
Better Builds with Maven - http://library.mergere.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
