On 29/03/06, Martin Cooper <[EMAIL PROTECTED]> wrote: > On 3/29/06, Henri Yandell <[EMAIL PROTECTED]> wrote: > > > > On 3/29/06, Sandy McArthur <[EMAIL PROTECTED]> wrote: > > > On 3/29/06, Rahul Akolkar <[EMAIL PROTECTED]> wrote: > > > > Or maybe we should simply advertise the dependencies pages better? > > > > > > Dependencies should be listed on the download page. The mind set of > > > someone wanting to to use a component is and I know this from having > > > done it a dozen or so times:
+1 > > > > I've come to believe that dependencies should be included in the > > distribution. Also that we shouldn't bother with binary and source > > distributions anymore; be like tapestry/hivemind (I think they're the > > ones) and have just the one dist file. -1 if that is the only archive type made available > Urk. No thanks. If I download a couple of Commons components, and they share > a couple of dependencies, and the bundled versions of those dependencies are > different, what should I, as a user, do? I think that would just cause more > confusion within the user base. +1 > As for having just a single distribution, I'm not in favour of that either. > The vast majority of users don't give a dickey bird about the source, and it > just bulks up the distribution, and therefore the size of the end user's > distribution as well. I doubt our users will thank us for increasing the > size of their own applications, potentially increasing their bandwidth usage > for customers to download their products. +1 Seems to me the binary download should be the minimum needed to run the component; the source download should not include any jars that are in the binary download. Depending on the component, potentially put the javadoc in a separate jar. > -- > Martin Cooper > > > > 1. Find the component's site. > > > 2. Find the download link on the site. > > > 3. See want they want to download (src/bin, tar/zip) > > > 4. Unpack > > > 5. Find the jar and add it to their project. > > > > > > Step #3 is where we have the most cranial activity available to us and > > > we should take advantage of that. Any other step and the end user is > > > just going through the motions trying to get their work done with as > > > little effort as possible. > > > > Agreed. > > > > Hen > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
