Le 19/11/2010 03:36, Gary Gregory a écrit : >> -----Original Message----- >> From: sebb [mailto:seb...@gmail.com] >> Sent: Thursday, November 18, 2010 18:34 >> To: Commons Developers List >> Subject: Re: [VOTE] Release Commons NET 2.2 based on RC3 >> >> On 19 November 2010 02:07, Phil Steitz <phil.ste...@gmail.com> wrote: >>> On 11/18/10 8:43 PM, sebb wrote: >>>> >>>> On 19 November 2010 01:12, Gary Gregory<ggreg...@seagullsoftware.com> >>>> wrote: >>>>> >>>>> I know we've gone back and forth but I think it would be nice to adopt a >>>>> convention to include source and javadoc in the bin distro. >>>> >>>> OK by me so long as there is only one copy of the javadoc in the bin >>>> distro. >>> >>> Why? In that case, I would ditch the jar; but some people like that. Is it >>> really that big? I bet [math] is the biggest and I don't recall it adding >>> that much heft. >> >> In the case of NET: >> >> 1843782 commons-net-2.2-javadoc.jar >> 212453 commons-net-2.2.jar >> 377467 commons-net-2.2-sources.jar >> >> The Javadoc is nearly 10 times the size of the binary code. > > I do not think we should base decisions like this on a byte count, relative > or not. I like to think of what users do with this stuff.
As it seems adding this stuff in the binary jar is for IDE, isn't the source jar inclusion sufficient ? IDEs are smart enough to extract the javadoc themselves from the source. They always display only a small part (like one method javadoc in a popup window when your mouse hover on a call to the method), so the complete structured javadoc may be overkill ? If this is really the case, we could simply add the source as a compromise between two extreme positions. Luc > > Gary > >> >>> Phil >>>> >>>>> From my POV, I get the bin distro to use from an IDE, so I really want >>>>> the source jar. I used the src distro to fix bugs and add features. >>>>> >>>>> It is not worth holding back a release but can we enforce whatever the >>>>> bin/src distro pattern is in the commons parent POM? >>>>> >>>>> Gary Gregory >>>>> Senior Software Engineer >>>>> Rocket Software >>>>> 3340 Peachtree Road, Suite 820 . Atlanta, GA 30326 . USA >>>>> Tel: +1.404.760.1560 >>>>> Email: ggreg...@seagullsoftware.com >>>>> Web: seagull.rocketsoftware.com >>>>> >>>>> >>>>> >>>>>> -----Original Message----- >>>>>> From: Oliver Heger [mailto:oliver.he...@oliver-heger.de] >>>>>> Sent: Wednesday, November 17, 2010 23:22 >>>>>> To: Commons Developers List >>>>>> Subject: Re: [VOTE] Release Commons NET 2.2 based on RC3 >>>>>> >>>>>> Build works fine with JDK 1.5 on Windows 7. Artifacts look good. >>>>>> >>>>>> The only nitpick I found is that the binary distribution does not >>>>>> contain the source and Javadocs jar. >>>>>> >>>>>> So +1. >>>>>> >>>>>> Oliver >>>>>> >>>>>> Am 17.11.2010 02:27, schrieb sebb: >>>>>>> >>>>>>> This is a vote to release Apache Commons NET 2.2 based on RC3. >>>>>>> >>>>>>> Changes since RC1 are: >>>>>>> - drop unnecessary jars from binary archive >>>>>>> - include RELEASE-NOTES in binary and source archives >>>>>>> >>>>>>> [ ] +1 release it >>>>>>> [ ] +0 go ahead I don't care >>>>>>> [ ] -1 no, do not release it because... >>>>>>> >>>>>>> tag: >>>>>>> http://svn.apache.org/repos/asf/commons/proper/net/tags/NET_2_2_RC3/ >>>>>>> >>>>>>> site: http://people.apache.org/~sebb/NET_2_2_RC3/ >>>>>>> >>>>>>> Archives (Maven and non-Maven) have been uploaded to: >>>>>>> >>>>>>> >>>>>>> https://repository.apache.org/content/repositories/orgapachecommons-011/ >>>>>>> >>>>>>> Vote will remain open for at least 72 hours. >>>>>>> >>>>>>> --------------------------------------------------------------------- >>>>>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >>>>>>> For additional commands, e-mail: dev-h...@commons.apache.org >>>>>>> >>>>>> >>>>>> >>>>>> --------------------------------------------------------------------- >>>>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >>>>>> For additional commands, e-mail: dev-h...@commons.apache.org >>>>> >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >>>>> For additional commands, e-mail: dev-h...@commons.apache.org >>>>> >>>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >>>> For additional commands, e-mail: dev-h...@commons.apache.org >>>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >>> For additional commands, e-mail: dev-h...@commons.apache.org >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
