I'd agree. There's no point in generating Javadoc for non-public apis in the distribution.
On 6/20/07, Adam Winer <[EMAIL PROTECTED]> wrote:
On 6/20/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: > > -1, with two problems: > > > > - The dist zip contains Javadoc for trinidadinternal. > > That's both a lot of wasted space and documenting > > code that we explicitly don't want people touching. > > My understanding is, that we should release javadoc as well. > I am sure, all projects do. MyFaces CORE also release it's IMPL javadoc It shouldn't. We shouldn't repeat that mistake. So again, -1. Developers are free to run Javadoc if they desperately want it, but these are explicitly classes that noone outside of Trinidad should be using. There's no reason to bloat our dist bundle. -- Adam > > -Matthias > > > > > - We dist zip includes commons-beanutils/collections/logging JARs > > even though our runtime code has no dependencies on any of them. > > > > -- Adam > > > > > > > > On 6/19/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > > > I was running the needed tasks to get the 101 release of the Trinidad > > > MyFaces CORE out. This is the first release of the JSF components > > > (targeted for JSF 1.1) since leaving the Apache Incubator. > > > The artifacts are deployed to my private Apache account ([1] and [2]). > > > > > > Please take a look at the "1.0.1" artifacts and vote > > > > > > ------------------------------------------------ > > > [ ] +1 for community members who have reviewed the bits > > > [ ] +0 > > > [ ] -1 for fatal flaws that should cause these bits not to be released, > > > and why.............. > > > ------------------------------------------------ > > > > > > Thanks, > > > Matthias > > > > > > [1] http://people.apache.org/~matzew/trinidad_core_101/ > > > [2] http://people.apache.org/~matzew/trinidad_core_101_dist/ > > > > > > -- > > > Matthias Wessendorf > > > > > > further stuff: > > > blog: http://matthiaswessendorf.wordpress.com/ > > > mail: matzew-at-apache-dot-org > > > > > > > > -- > Matthias Wessendorf > > further stuff: > blog: http://matthiaswessendorf.wordpress.com/ > mail: matzew-at-apache-dot-org >
