You might think about adding a fall back repository for future releases, so,
in the unlikely event that the files haven't synch'd over to ibilio yet, or
the very likely event that the connection to ibiblio (via maven build or ant
get) times out, the build won't fail, and you can keep the primary target as
ibiblio.
Just a thought.
--
James Mitchell
Software Engineer / Open Source Evangelist
Consulting / Mentoring
678.910.8017
----- Original Message -----
From: "Sean Schofield" <[EMAIL PROTECTED]>
Newsgroups: gmane.comp.jakarta.myfaces.devel
Sent: Thursday, February 09, 2006 2:38 PM
Subject: Re: [VOTE] Release MyFaces Maven 1.0.0
Release is done. (5) +1 PMC votes
The jars have been published to www.apache.org/dist/maven-repository.
We're awaiting word from the maven-dev group confirming that this is
the proper place to publish so they end up in ibiblio (I suspect they
need to be published to www.apache.org/dist/java-repository instead.)
Anyways that release is done and the jars will be out there on ibiblio
shortly. In the meantime in order to build the upcoming commons
*branch* you will need a local copy of the myfaces-maven dependency.
Sean
On 2/9/06, Bill Dudney <[EMAIL PROTECTED]> wrote:
+1
On Feb 8, 2006, at 9:26 AM, Sean Schofield wrote:
> It appears that ASF policy requires a vote before an official release.
> We need to "release" the myfaces-maven project ASAP so we can do more
> meaningful releases of the implementation and tomahawk.
>
> So to be on the safe side lets do an official vote. No release
> candidate has been built. We are voting on the tagged (1_0_0) version
> which can be built from maven.
>
> Sean
