Mailing-List: contact continuum-dev-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: continuum-dev@maven.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Message-ID: <46DBF9C0.5000502@venisse.net>
Date: Mon, 03 Sep 2007 14:10:40 +0200
From: Emmanuel Venisse <emmanuel@venisse.net>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: continuum-dev@maven.apache.org
Subject: Re: The specified resource isn't a file or the protocol used isn't
                     allowed.
References: <27205.84.233.182.145.1188815948.squirrel@www.sharp.fm>
    <37398.84.233.182.145.1188816398.squirrel@www.sharp.fm>
    <46DBEC2B.5030601@venisse.net>
    <56604.84.233.182.145.1188819621.squirrel@www.sharp.fm>
    <46DBF45B.10404@venisse.net>
 <38574.84.233.182.145.1188820899.squirrel@www.sharp.fm>
In-Reply-To: <38574.84.233.182.145.1188820899.squirrel@www.sharp.fm>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit


Graham Leggett a �crit :
> On Mon, September 3, 2007 1:47 pm, Emmanuel Venisse wrote:
> 
>>> When you say it works fine, are you referring to continuum v1.1 beta 2
>>> installed brand new from scratch, or are you using previous versions
>>> that
>>> have been upgraded?
>> both and beta-3-SNAPSHOT too :)
> 
> Let me try trunk and see if the problem still exists.

ok.

> 
>> dev list is for development/developer discussions. All other discussions
>> are for users list
> 
> Bugs are a development discussion, and I'm pretty certain at this point
> that what I am seeing is a bug. I am after people who know the underlying
> code in the hope that I may contribute a patch once the problem has been
> isolated and fixed.
> 
I am the one that apply the majority of patches, I'm sorry to insist but the dev list is for dev discussion like design, new features, etc we want to introduce
bugs must be discussed on the users list so other users can have the same issue will can find/read the thread and contribute to the discussion too.

If you want to talk about an issue, the bast way is to discuss about it on the users list, then you can open an issue in jira if we don't have already one about it and eventually submit a patch.

Emmanuel