Many OSS source releases contain the built jar files. The key reason for me is that I use eclipse. To do this I need - the genuine jar file (single trusted build) - the source code debug into/method prompts etc.
Unless the jar file is included in the source release, I will download the binary release as well in order to obtain the genuine built jar. As a result, I've always felt much happier with OSS projects that actually release the jar with the source download - [collections] is one of them. Stephen From: "Martin Cooper" <[EMAIL PROTECTED]> > > I'm fairly certain the bulk of our users don't necessarily mind that our > > -src distributions contain a jar. Speaking from my own > > experience, I don't > > view these as "source" or "binary" distributions but a distribution with > > only binaries and a distribution that also includes source. > > Please include > > the jars to remain consistent with other commons components. > > None of the Commons components that I've ever worked on, and certainly none > of those that I've been a release manager for, have ever included jars in > the source distros, so as far as I'm concerned, I'm being consistent, and > don't plan on changing the way those components are released. > > > Why would you put a _binary_ jar file in the _source_ distribution? If > > > people want the binary, they should download the binary distro, not the > > > source one. ;-) Also, putting it in both means that someone who > > wants both > > > distros has to download two copies of the jar, which doesn't > > seem to make > > > much sense. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
