Try updating from the SVN again, it should be fixed now. The site/pom.xml was using myfaces-master 1.0.3 instead of 1.0.4 as parent, although i'm not sure why it didn't worked anyway, but it will work now.

Regards,
Catalin

Wendy Smoak <[EMAIL PROTECTED]> wrote:
On 6/5/06, Matthias Wessendorf <[EMAIL PROTECTED]> wrote:

> > [INFO] Scanning for projects...
> > [INFO] ------------------------------------------------------------------------
> > [ERROR] FATAL ERROR
> > [INFO] ------------------------------------------------------------------------
> > [INFO] Failed to resolve artifact.
> >
> > GroupId: org.apache.myfaces.maven
> > ArtifactId: myfaces-master
> > Version: 1.0.3-SNAPSHOT
> >
> > Reason: Unable to download the artifact from any repository
> >
> > org.apache.myfaces.maven:myfaces-master:pom:1.0.3-SNAPSHOT
> >
> > from the specified remote repositories:
> > central (http://repo1.maven.org/maven2)
> >

> mmm
> to me it works.

I can reproduce it after rm -rf $M2_REPO/org/apache/myfaces.

There is either a missing, or an incorrect dependency version.

The myfaces-master pom is currently at 1.0.4-SNAPSHOT, yet from the
error, something is looking for 1.0.3-SNAPSHOT. Regardless, it should
be able to find 1.0.3-SNAPSHOT in Apache's Maven snapshot repo, yet it
only looked in the central repo.

I'm sorry I don't have time to chase this down tonight, but I can
confirm that 'mvn install' does not work from a fresh checkout of
myfaces/current with nothing in my local repo.

--
Wendy

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

Reply via email to