Re: Spec APIs in Tuscany distros (was Re: svn commit: r475086)
Jeremy Boynes wrote: On 11/16/06, Simon Nash [EMAIL PROTECTED] wrote: I don't understand how this would break modularity. Because it couples together the release lifecycles of two very independent modules. These lifecycles would not be coupled. If the spec APIs move forward and we want to release an update to these that is out of cycle with a Tuscany Java SCA implementation milestone, we can do this at any time using the separate spec API distro that we have. This does not require releasing javadoc as well. The audience for the combined javadoc is developers who want to use the Tuscany Java SCA implementation, and this audience will want a consistent combination of javadoc that matches a specific Tuscany Java SCA implementation release. Users of the Tuscany api/spi javadoc will always need the spec javadoc as well. I'm not sure that that is true. I am sure that the converse isn't (users of the spec will not always need tuscany docs). Agreed on the second point, and this is why we have a separate source distro for the spec APIs. Simon Packaging them together enables Tuscany SCA developers to get all this javadoc with a single download rather than needing to do multiple downloads and manually combine the results. For those who need separate per-module javadoc because of IDE requirements, it will be available from maven. Simon -- Jeremy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Simon C Nash IBM Distinguished Engineer Hursley Park, Winchester, UK [EMAIL PROTECTED] Tel. +44-1962-815156 Fax +44-1962-818999 - 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] -- Simon C Nash IBM Distinguished Engineer Hursley Park, Winchester, UK [EMAIL PROTECTED] Tel. +44-1962-815156 Fax +44-1962-818999 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Spec APIs in Tuscany distros (was Re: svn commit: r475086)
Jeremy Boynes wrote: On 11/15/06, Simon Nash [EMAIL PROTECTED] wrote: Having a separate source distro for the SCA spec API makes sense to me. I see that your download page http://people.apache.org/~rfeng/tuscany/incubator-M2/downloads/ has already been updated to add this. I'm not so convinced that we should be delivering spec API files for commonj timer and work manager as part of the Tuscany SCA source distros. These are APIs that we are using rather than APIs that we are implementing. At the present time, we need to provide these files so that the SCA kernel can build, but I think we should be looking to eliminate them from our source distro as soon as possible and reference another source for these. If one's available that would be good - we originally used the one from Geronimo but that had problems and once fixed didn't fit our release schedule. BTW we do have an implementation of work manager thanks to Meeraj. The Tuscany SCA javadoc distro currently has the commonj APIs as well as the SCA APIs and the Tuscany APIs. I think we should remove the commonj APIs from this javadoc but retain the SCA APIs and the Tuscany APIs. We're distributing per-module javadoc through maven as that fits the expectations of the IDEs - see previous discussion on this. We could mirror the spec javadoc on the download site. I don't think we should mix spec doc with tuscany doc (api/spi) as it breaks our modularity story. I don't understand how this would break modularity. Users of the Tuscany api/spi javadoc will always need the spec javadoc as well. Packaging them together enables Tuscany SCA developers to get all this javadoc with a single download rather than needing to do multiple downloads and manually combine the results. For those who need separate per-module javadoc because of IDE requirements, it will be available from maven. Simon -- Jeremy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Simon C Nash IBM Distinguished Engineer Hursley Park, Winchester, UK [EMAIL PROTECTED] Tel. +44-1962-815156 Fax +44-1962-818999 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Spec APIs in Tuscany distros (was Re: svn commit: r475086)
On 11/16/06, Simon Nash [EMAIL PROTECTED] wrote: I don't understand how this would break modularity. Because it couples together the release lifecycles of two very independent modules. Users of the Tuscany api/spi javadoc will always need the spec javadoc as well. I'm not sure that that is true. I am sure that the converse isn't (users of the spec will not always need tuscany docs). Packaging them together enables Tuscany SCA developers to get all this javadoc with a single download rather than needing to do multiple downloads and manually combine the results. For those who need separate per-module javadoc because of IDE requirements, it will be available from maven. Simon -- Jeremy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Simon C Nash IBM Distinguished Engineer Hursley Park, Winchester, UK [EMAIL PROTECTED] Tel. +44-1962-815156 Fax +44-1962-818999 - 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]
Spec APIs in Tuscany distros (was Re: svn commit: r475086)
Having a separate source distro for the SCA spec API makes sense to me. I see that your download page http://people.apache.org/~rfeng/tuscany/incubator-M2/downloads/ has already been updated to add this. I'm not so convinced that we should be delivering spec API files for commonj timer and work manager as part of the Tuscany SCA source distros. These are APIs that we are using rather than APIs that we are implementing. At the present time, we need to provide these files so that the SCA kernel can build, but I think we should be looking to eliminate them from our source distro as soon as possible and reference another source for these. The Tuscany SCA javadoc distro currently has the commonj APIs as well as the SCA APIs and the Tuscany APIs. I think we should remove the commonj APIs from this javadoc but retain the SCA APIs and the Tuscany APIs. Simon Jeremy Boynes wrote: On 11/14/06, Raymond Feng [EMAIL PROTECTED] wrote: Hi, Jeremy. Should we have a separate source distro for the SCA spec then? I think so - basically for every module that we may update individually. -- Jeremy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Simon C Nash IBM Distinguished Engineer Hursley Park, Winchester, UK [EMAIL PROTECTED] Tel. +44-1962-815156 Fax +44-1962-818999 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Spec APIs in Tuscany distros (was Re: svn commit: r475086)
On 11/15/06, Simon Nash [EMAIL PROTECTED] wrote: Having a separate source distro for the SCA spec API makes sense to me. I see that your download page http://people.apache.org/~rfeng/tuscany/incubator-M2/downloads/ has already been updated to add this. I'm not so convinced that we should be delivering spec API files for commonj timer and work manager as part of the Tuscany SCA source distros. These are APIs that we are using rather than APIs that we are implementing. At the present time, we need to provide these files so that the SCA kernel can build, but I think we should be looking to eliminate them from our source distro as soon as possible and reference another source for these. If one's available that would be good - we originally used the one from Geronimo but that had problems and once fixed didn't fit our release schedule. BTW we do have an implementation of work manager thanks to Meeraj. The Tuscany SCA javadoc distro currently has the commonj APIs as well as the SCA APIs and the Tuscany APIs. I think we should remove the commonj APIs from this javadoc but retain the SCA APIs and the Tuscany APIs. We're distributing per-module javadoc through maven as that fits the expectations of the IDEs - see previous discussion on this. We could mirror the spec javadoc on the download site. I don't think we should mix spec doc with tuscany doc (api/spi) as it breaks our modularity story. -- Jeremy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
