Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (athena.apache.org: domain of sebbaz@gmail.com designates
 72.14.246.247 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=ZDkwJnpzwLjsiD2pRdvP+Biwf7XlT3gqYq7+dUqg/9yjmK/LXzU2s1Ag2Im/HVZ6klqtRDi3sjHznuU3Zv8oIA4lfKHRDKoA7ENoUGq5HwWOGOGXMbAZBkbZCOrU4K6lu97wI8i/6gRE1s1sBKWh9SjDE2M33wGGkvfuFCsQw2s=
Message-ID: <25aac9fc0802201546o33f63cdai1a93348f9a9c2783@mail.gmail.com>
Date: Wed, 20 Feb 2008 23:46:43 +0000
From: sebb <sebbaz@gmail.com>
To: "Jakarta Commons Developers List" <dev@commons.apache.org>
Subject: Re: [VOTE] Release Proxy 1.0 (from rc2)
In-Reply-To: <47BCB4A2.1050804@apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <f2e8eedf0802191531h69e8febfje4e727ede313edd4@mail.gmail.com>
	 <47BCB4A2.1050804@apache.org>

No major problems, however there are some items that can be improved:

Dependency Listings entry:

>>>
Commons Proxy

Java library for dynamic proxying

../../../../../people.apache.org/www/commons.apache.org/proper/proxy/
<<<

Not sure where that originates, but it does not look right.

Ideally there should be a Developer or Building page describing how to
build the code.

It would be useful to have a text file in the source archive with
basic build info as well.

It would be good to mention the required Java version in the Release Notes.

On 20/02/2008, Emmanuel Bourg <ebourg@apache.org> wrote:
> A few suggestions for the next release (don't hold 1.0 just for this if
>  you don't have the time) :
>
>  - A tutorial with short code examples would be nice to get a quick taste
>  of the API. The overview page is not very sexy, I'm not a proxy guru and
>  I'm not sure to understand what I can achieve with the component.
>
>  - package.html files are missing, the consequence is an almost blank
>  table when the Javadoc is opened
>
>  - the javadoc for classes such as JavassistUtils is missing. Some
>  classes or interfaces with only one method have a javadoc at the class
>  level but not at the method level. I understand that the method comment
>  will most likely be redundant, but it's still useful for an IDE such as
>  IntelliJ that can display the method documentation in a popup window.
>
>
>  Emmanuel Bourg
>
>
>
>  ---------------------------------------------------------------------
>  To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>  For additional commands, e-mail: dev-help@commons.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org