Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of flamefew@gmail.com designates
 64.233.162.192 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=gVjaHDkorcgk8pr2F2VblU5uHJykoyrB7FWDZVwKEPZ0r/lLsmtFGY/9iORpM4L8VhV5sp2VkItFQ4qoO9CNnSC9OlHXrrfxIu0q6wg3RyAcqWEsQH0uaeE9SH9CU/nV3yto9dJTbU7eZ8G+93ZdvjF5CT011NVUF9c5umf6kuA=
Message-ID: <31cc373605080320067a2aef87@mail.gmail.com>
Date: Wed, 3 Aug 2005 23:06:55 -0400
From: Henri Yandell <flamefew@gmail.com>
To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>
Subject: Re: [ALL] Distributing an ide version
In-Reply-To: <42F1603C.4010303@apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <B93830D99D595F43996A8899AEDB8F5310F9FF@ns1018.seagull.nl>
	 <42F1603C.4010303@apache.org>

Not sure why we have two downloads anyway. The src is usually
relatively small compared to the binary; is it to just to avoid
confusing the user?

Problem with Brett's 3-download approach is that when we say src we
don't mean src, we mean buildable. Just having the src in a jar
doesn't help somebody to build it. Still, I like that Maven will start
distributing javadoc and src too; helps heavily with my vague wish to
have all the versioned javadoc online.

I long since stopped using either the src or the binary download. I
get all my commons jars from either ibiblio or my local maven
repository, and I use the online javadoc. :)

Hen

On 8/3/05, Brett Porter <brett@apache.org> wrote:
> Doesn't the source zip required by an IDE usually need to be baed at the
> same level as a JAR?
>=20
> ie
> org/apache/commons/foo/Foo.java
>=20
> where in -src that is usually under src/...
>=20
> I'm not sure how that would site with an IDE though - perhaps include
> both those JARs in a single -dev zip.
>=20
> The approach we're taking with Maven is to publish a source JAR (and
> Javadoc JAR) that accompanies the binary JAR.
>=20
> - Brett
>=20
> Gary Gregory wrote:
>=20
> >+1.
> >
> >In my head I think of these pieces:
> >
> >commons-xxx-src.zip
> >       All sources needed to produce other pieces.
> >commons-xxx-bin.zip
> >       Runtime only, no source, no Javadoc, just the *runtime*.
> >commons-xxx-dev.zip (or ide)
> >       What I need to use the component for my development (source zip
> >file and runtime).
> >
> >Which now that I've written it out matches what you've proposed I see
> >;-)
> >
> >Gary
> >
> >
> >
> >>-----Original Message-----
> >>From: Stephen Colebourne [mailto:scolebourne@btopenworld.com]
> >>Sent: Wednesday, August 03, 2005 4:46 PM
> >>To: Jakarta Commons Developers List
> >>Subject: [ALL] Distributing an ide version
> >>
> >>Currently we make available two versions, src and bin.
> >>
> >>The src contains all the source code and xdocs. Occaisionaly the jar
> >>file is included (this is a related issue to this email thread).
> >>
> >>The bin contains the jar file, and the javadoc.
> >>
> >>Yet, whenever I download a commons package I always find myself
> >>downloading both - the bin to get the jar, and the src to get the
> >>
> >>
> >source
> >
> >
> >>to attach within my IDE (Eclipse).
> >>
> >>So, maybe we should consider having an ide download. This would
> >>
> >>
> >contain
> >
> >
> >>the jar and the zipped src (no xdoc or package.html etc). This would
> >>
> >>
> >be
> >
> >
> >>a smaller download than either current dist, yet provide everything
> >>
> >>
> >most
> >
> >
> >>users need, and without two downloads.
> >>
> >>Am I talking rubbish? Would you download a commons-xxx-ide.zip? Is it
> >>worth the effort?
> >>
> >>Stephen
> >>
> >>---------------------------------------------------------------------
> >>To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> >>For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> >>
> >>
> >>
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> >For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> >
> >
> >
> >
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>=20
>

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