Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (herse.apache.org: domain of marc.portier@gmail.com
 designates 66.249.92.171 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:organization:user-agent:mime-version:to:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding:sender;
        b=jBUgiaoykP/orJJ2/8roH20IOAMxk59//yHiB0CBBJHwnlQiEjG3E7IGzg2zo7tAsL+areIzMJwc01H9vcFcpW8kaKzVMamdB2zV3NT6bMTP8rlfnfIKeueWJVPgiNBcfwMe5g7pLuiaVaNvnfeegS1CnpT9MzpC1sK6WYIdppc=
Message-ID: <462374FF.9050504@outerthought.org>
Date: Mon, 16 Apr 2007 15:07:11 +0200
From: Marc Portier <mpo@outerthought.org>
Organization: Outerthought
User-Agent: Thunderbird 1.5.0.10 (X11/20070306)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: 2.2 failing to build: cocoon-javaflow
References: <11641E74-7ADB-4D99-A86C-43823CC3A712@luminas.co.uk>
 <4623588F.30309@apache.org>
 <859F9128-A1BD-46E3-92BE-17828A37039F@luminas.co.uk>
 <46237230.7070704@outerthought.org>
In-Reply-To: <46237230.7070704@outerthought.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: Marc Portier <marc.portier@gmail.com>


Marc Portier wrote:
> 
> now, to solve things I think we better
> - ask jci peeps to publish non-snapshot releases on a public repo (this
> includes RC-releases)
> 
> - or just add my patch to the pom, rather then yours, no?
> 
> 

oh, upon reread I think additional clarification is due:

our patches do not involve the same pom.xml file.
- yours is about cocoon-core
- mine about cocoon-javaflow-impl (closer to the actual issue)


oh, and also note that I'm totally don't want to say my patch is the
_good_ solution:

in fact, historically adding the trick to 'allow non-snapshots from
people.apache.org' in cocoon-core/pom.xml rather then ask jci to
properly publish the rc-release (or just keep dependency to the *real*
snapshot) is quite direclty leading us to the current situation today

so re-using that trick in yet another pom is surely not the _clean_ way
of going about this.


it is _just_ a fast way of getting us all to build again

-marc=