We'd have to ask the maven people to republish just this artifact. Technically it requires a new vote, etc.
Lets concentrate on the new release first. I'm about to start a [VOTE] thread once TCK testing is done. In the meantime, please check your independent project agains the jars in our new myfaces repo[1]. Sean [1] http://myfaces.zones.apache.org/dist/maven-repository On 4/26/06, Manfred Geiler <[EMAIL PROTECTED]> wrote: > On 4/25/06, Sean Schofield <[EMAIL PROTECTED]> wrote: > > > > Actually when you build a custom project with a myfaces-impl-1.1.2 > > > dependency Maven 2.0.4 tries to download the myfaces-master-1.0.1 > release(!) > > > from http://cvs.apache.org/maven-snapshot-repository, > which > > > is subject to fail of course. > > > Try it out! > > > > OK now I see what you are saying. I didn't realize this was a custom > > project issue. Interesting that maven downloads the master-pom. Its > > really only a maven-related dependency. I'm suprised its requiring > > it. > > > > Out of curiousity why doesn't maven just grab the myfaces-master-1.0.1 > > from ibiblio? Why is it even checking the snapshot repo? > > > Looks like Maven tries to do that because WE coerce Maven to download every > dependency regarding the myfaces-core-project artifact. We do that by > mistakenly saying: "Use > http://cvs.apache.org/maven-snapshot-repository for all > your downloads." > Just for remembrance, this is the concerned section: > <repositories> > <repository> > <snapshots /> ------ malformed element ! > > <id>apache-maven-snapshots</id> > > <url>http://cvs.apache.org/maven-snapshot-repository</url> > </repository> > </repositories> > > > > > > We should also try to fix the releases myfaces-core-project-1.1.2.pom > ASAP. > > > > Well I don't think we can go back and fix this release retroactively. > > I'd say we need to release a whole new core (1.1.3 ) ASAP for this and > > other reasons. I'm trying my best but I am only one person and there > > is a lot of maven b.s. to deal with at the moment. > > > I just patched the myfaces-core-project-1.1.2.pom in my local M2 repo. Now > Maven build work like a charm. > > Since myfaces-core-project-1.1.2.pom is only a POM, there speaks nothing > against uploading a patched version to ibiblio, although this is not a thing > one should do every day, of course. Right? So, > * Is there an easy way to replace an already released POM on ibiblio? > * Any veto against this? > > Manfred > >