Daniel Fagerstrom wrote:
I'll talk to Upayavira, and see if we can take care about it.
I saw that you had changed the Cocoon group id to org.apache.cocoon from
apache-cocoon in the main pom and the core pom but nowhere else. What is
your plane for this? Should we just start to change group
I've just done a fresh build of trunk using m2, which failed somehow
because of problems with xml-apis, saying something like:
This artifact has been relocated to xml-apis:xml-apis:1.0.b2.
And I also found references to it trying to get it from a URL at:
Daniel Fagerstrom wrote:
I think that the problems is that there was a 2.0.2 release of the
xml-apis by mistake, don't know the story behind it, but see
http://www.apache.org/dist/java-repository/xml-apis/jars/. It should
have been 1.0.b2.
Several poms at the official maven repository have
Jorg Heymans skrev:
Daniel Fagerstrom wrote:
...
The root of the problem lies somewhere in the current m2 poms from
excalibur. These have been automatically converted from the m1
project.xml files, so they are not using things like
scopeprovided/scope where they should. This problem became
