Return-Path: Delivered-To: apmail-myfaces-dev-archive@www.apache.org Received: (qmail 8905 invoked from network); 26 Apr 2006 07:36:38 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 26 Apr 2006 07:36:37 -0000 Received: (qmail 38591 invoked by uid 500); 26 Apr 2006 07:36:33 -0000 Delivered-To: apmail-myfaces-dev-archive@myfaces.apache.org Received: (qmail 38449 invoked by uid 500); 26 Apr 2006 07:36:32 -0000 Mailing-List: contact dev-help@myfaces.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "MyFaces Development" Delivered-To: mailing list dev@myfaces.apache.org Received: (qmail 38427 invoked by uid 99); 26 Apr 2006 07:36:32 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Apr 2006 00:36:32 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of manfred.geiler@gmail.com designates 66.249.82.202 as permitted sender) Received: from [66.249.82.202] (HELO xproxy.gmail.com) (66.249.82.202) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Apr 2006 00:36:31 -0700 Received: by xproxy.gmail.com with SMTP id t16so963839wxc for ; Wed, 26 Apr 2006 00:36:10 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=eOOr5Deu5CilPSynSYeq3EhooL2ZCPwR0vOkMgnrPKPV4AQpwMVhdD8Cq1NG9dRnDDI5RjNrh3Ds0PPzZLZHl4oDvIs92VdUAwPkqgxpvBI3fS9Smbwna/PQAZYUwF9XaO3xaTOSDeQ27EpZd/GnE1+OMjg+GmY39MkI8SfDkjo= Received: by 10.70.71.11 with SMTP id t11mr5006209wxa; Wed, 26 Apr 2006 00:36:10 -0700 (PDT) Received: by 10.70.70.4 with HTTP; Wed, 26 Apr 2006 00:36:10 -0700 (PDT) Message-ID: <564d4f680604260036y3193b11dmabe4018cbf1da756@mail.gmail.com> Date: Wed, 26 Apr 2006 09:36:10 +0200 From: "Manfred Geiler" To: "MyFaces Development" Subject: Re: [Important] Ugly bug in core pom.xml for 1.1.2 and 1.1.3 Cc: "John Fallows" , "Bernd Bohmann" , "Wendy Smoak" In-Reply-To: <2387fbc50604241632h62042b83h39dc7009fdb593a5@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_27465_20998326.1146036970458" References: <564d4f680604240753n40262949u43e40e81d12536d3@mail.gmail.com> <2387fbc50604240832r433faccfjd94cdb0f4575c1ca@mail.gmail.com> <564d4f680604241435h3eb662f8x7655f0112c0ec307@mail.gmail.com> <2387fbc50604241632h62042b83h39dc7009fdb593a5@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------=_Part_27465_20998326.1146036970458 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On 4/25/06, Sean Schofield 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.1releas= e(!) > > 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: ------ malformed element ! apache-maven-snapshots http://cvs.apache.org/maven-snapshot-repository > > We should also try to fix the releases myfaces-core-project-1.1.2.pomAS= AP. > > 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 thin= g 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 ------=_Part_27465_20998326.1146036970458 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On 4/25/06, Sean Schofield <sean.schofield@gmail.com> 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 rele= ase(!)
> from http://cvs.apache.org/maven-snapshot-repository, which
> is subje= ct 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.&nbs= p; Interesting that maven downloads the master-pom.  Its
really only a maven-related dependency.  I'm suprised its req= uiring
it.

Out of curiousity why doesn't maven just grab the myfa= ces-master-1.0.1
from ibiblio?  Why is it even checking the sn= apshot repo?

Looks like Maven tries to do that because WE coerce Maven to downl= oad every dependency regarding the myfaces-core-project artifact. We do tha= t by mistakenly saying: "Use http://cvs.apache.org/maven-snapshot-repository for all your downloads.= "
Just for remembrance, this is the concerned section:
  &l= t;repositories>
    <repository>
  =     <snapshots />   ------ malformed element= !
      <id>apache-maven-snapshots</id&= gt;
      <url>http://cvs.apache.org/maven-snapshot-reposit= ory</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 retroa= ctively.
I'd say we need to release a whole new core (1.1.3 ) ASAP for t= his and
other reasons.  I'm trying my best but I am only one p= erson 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

------=_Part_27465_20998326.1146036970458--