The maven javadoc goal by default generates a -javadoc.jar for every
artifact it produces and allows that to be deployed to the repo. I
believe it does this because that is the format expected by the
different IDEs (it certainly is for IDEA and I think Raymond said it
worked for Eclipse as well). I think we would be wise to follow this
convention.
That would mean that e.g. for -api there would be
tuscany-api-${version}-javadoc.jar
in the repo.
I agree that we should just do *-api and -spi.
I also think we should do aggregated javadoc for all those modules
online on the website. We could make an archive of that available on
the download site (but I don't think we need to do that through the
maven repos).
--
Jeremy
On 11/1/06, Jim Marino <[EMAIL PROTECTED]> wrote:
On Nov 1, 2006, at 9:33 AM, Raymond Feng wrote:
> Hi,
>
> I think it would be useful to package java in our M2 binary distro.
> I would like to hear your opinions:
I'd say as a separate downloadable jar since this would only be
relevant to extensions providers and not applications developers.
>
> 1) What modules should we generate javadoc? I assume only for *-api
> and *-spi.
yes. Core is not an exposed api/spi.
> 2) Should we package the javadoc with the standalone distro or as a
> separate archive?
separate archive
>
> Thanks,
> Raymond
---------------------------------------------------------------------
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]
