[ http://jira.codehaus.org/browse/MEV-406?page=comments#action_69282 ]
Corridor Software Developer commented on MEV-406:
-
Can we take Brett's idea about a 2.0.0-1.pom to fruition and close this out?
It's blocking the 2.0.1 release of the xmlb
[ http://jira.codehaus.org/browse/MEV-406?page=comments#action_68995 ]
Brett Porter commented on MEV-406:
--
agreed for the POM, though I was actually referring to the maven-metadata.xml
file
> XMLBeans pom is missing dependency
> ---
[ http://jira.codehaus.org/browse/MEV-406?page=comments#action_68968 ]
Steve Loughran commented on MEV-406:
Brett says
>Should we write some properties in to the artifact metadata that says who
>submitted the current POM, and the >MEV/MAVENUPLOAD issue
[ http://jira.codehaus.org/browse/MEV-406?page=comments#action_68954 ]
Brett Porter commented on MEV-406:
--
the particular API jar and its heritage is a known problem, and that's probably
one reason just adding the stax dependency to this might be a bad idea
[ http://jira.codehaus.org/browse/MEV-406?page=comments#action_68000 ]
Carlos Sanchez commented on MEV-406:
This can't be fixed in the repo. Dependencies can't change or previous builds
won't be reproducible.
You can add the dependencies in your pom and
