On 3/25/07, robert burrell donkin <[EMAIL PROTECTED]> wrote:
On 3/23/07, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
> robert burrell donkin ha scritto:
<snip>
> >> 2) How should we manage javadocs creation and sdk creation in this
> >> multimodule structure? I think the "move" broke them.
> >
> > it's easy to put them back again but i'd prefer to hear opinions
> > before i implement
> >
> > one approach is for all modules to create src and javadoc jars of
> > their own (useful for IDEs) and then unpack them in deploy. another is
> > to javadoc from the deployment across all modules.
>
> I prefer to have each jar with its own javadocs, and maybe we can unpack
> them all in a single package in the final distribution, but I don't know
> if this is easy to do.
i favour this as well but i'd like to see if there's a consensus
before i implement
I like the way spring does it. You have various dependencies split
into separate jars, but then there's a single big javadoc
(http://static.springframework.org/spring/docs/2.0.x/api/). It's just
nice to have a comprehensive reference.
I'm not sure how fair a comparison this is as I still need to digest a
bit more how things are divided.
--
Serge Knystautas
Lokitech >> software . strategy . design >> http://www.lokitech.com
p. 301.656.5501
e. [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
