You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tuscany.apache.org by rf...@apache.org on 2006/11/15 01:38:44 UTC

svn commit: r475086 - /incubator/tuscany/branches/sca-java-M2/sca/distribution/build.xml

Author: rfeng
Date: Tue Nov 14 16:38:44 2006
New Revision: 475086

URL: http://svn.apache.org/viewvc?view=rev&rev=475086
Log:
Add the SCA spec source code to the source distro

Modified:
    incubator/tuscany/branches/sca-java-M2/sca/distribution/build.xml

Modified: incubator/tuscany/branches/sca-java-M2/sca/distribution/build.xml
URL: http://svn.apache.org/viewvc/incubator/tuscany/branches/sca-java-M2/sca/distribution/build.xml?view=diff&rev=475086&r1=475085&r2=475086
==============================================================================
--- incubator/tuscany/branches/sca-java-M2/sca/distribution/build.xml (original)
+++ incubator/tuscany/branches/sca-java-M2/sca/distribution/build.xml Tue Nov 14 16:38:44 2006
@@ -20,14 +20,23 @@
 <project name="project" default="install">
 
     <property name="prefix" value="tuscany-sca-1.0-incubator-M2"/>
-    <property name="url" value="http://svn.apache.org/repos/asf/incubator/tuscany/branches/sca-java-M2"/>
+    <property name="url" value="http://svn.apache.org/repos/asf/incubator/tuscany"/>
 
     <target name="install" depends="source, sample, javadoc" />
 
-    <target name="javadoc">
+    <target name="javadoc" depends="spec">
 
 	<delete dir="target/javadoc" quiet="true"/>
 
+        <javadoc packagenames="org.osoa.*" sourcepath="target/source/zip/spec/src/main/java"
+               defaultexcludes="yes"
+               destdir="target/javadoc/spec"
+               author="true"
+               version="true"
+               use="true">
+            <link href="http://java.sun.com/j2se/1.5.0/docs/api/"/>
+        </javadoc>
+
         <unzip dest="target/javadoc/api">
             <fileset dir="../kernel/api">
                 <include name="target/*javadoc.jar"/>
@@ -62,25 +71,40 @@
 	<delete file="target/${prefix}-javadoc.tar" />
     </target>
 
+    <target name="spec">
+
+	<delete dir="target/source/zip/spec" quiet="true"/>
+	<exec executable="svn">
+            <arg line="export --native-eol CRLF ${url}/tags/java/spec/sca/1.0-incubator-M2 target/source/zip/spec"/>
+        </exec>
+
+	<delete dir="target/source/gz/spec" quiet="true"/>
+	<exec executable="svn">
+            <arg line="export --native-eol LF ${url}/tags/java/spec/sca/1.0-incubator-M2 target/source/gz/spec"/>
+        </exec>
+
+    </target>
 
-    <target name="source" depends="sample">
+    <target name="source" depends="spec, sample">
 
 	<delete dir="target/source/zip/sca" quiet="true"/>
 	<exec executable="svn">
-            <arg line="export --native-eol CRLF ${url}/sca target/source/zip/sca"/>
+            <arg line="export --native-eol CRLF ${url}/branches/sca-java-M2/sca target/source/zip/sca"/>
         </exec>
 
         <zip destfile="target/${prefix}-src.zip">
+            <zipfileset dir="target/source/zip/spec" prefix="src/spec"/>
             <zipfileset dir="target/source/zip/sca" prefix="src/sca"/>
             <zipfileset dir="target/source/zip/samples" prefix="src/samples"/>
         </zip>
 
 	<delete dir="target/source/gz/sca" quiet="true"/>
 	<exec executable="svn">
-            <arg line="export --native-eol LF ${url}/sca target/source/gz/sca"/>
+            <arg line="export --native-eol LF ${url}/branches/sca-java-M2/sca target/source/gz/sca"/>
         </exec>
 
         <tar destfile="target/${prefix}-src.tar" longfile="gnu">
+            <tarfileset dir="target/source/gz/spec" prefix="src/spec"/>
             <tarfileset dir="target/source/gz/sca" prefix="src/sca"/>
             <tarfileset dir="target/source/gz/samples" prefix="src/samples"/>
         </tar>
@@ -93,7 +117,7 @@
 
 	<delete dir="target/source/zip/samples" quiet="true"/>
 	<exec executable="svn">
-            <arg line="export --native-eol CRLF ${url}/samples target/source/zip/samples"/>
+            <arg line="export --native-eol CRLF ${url}/branches/sca-java-M2/samples target/source/zip/samples"/>
         </exec>
 
         <zip destfile="target/${prefix}-sample-src.zip">
@@ -102,7 +126,7 @@
 
 	<delete dir="target/source/gz/samples" quiet="true"/>
 	<exec executable="svn">
-            <arg line="export --native-eol LF ${url}/samples target/source/gz/samples"/>
+            <arg line="export --native-eol LF ${url}/branches/sca-java-M2/samples target/source/gz/samples"/>
         </exec>
 
         <tar destfile="target/${prefix}-sample-src.tar" longfile="gnu">



---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-commits-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-commits-help@ws.apache.org


Re: Spec APIs in Tuscany distros (was Re: svn commit: r475086)

Posted by Simon Nash <na...@hursley.ibm.com>.
Jeremy Boynes wrote:
> On 11/16/06, Simon Nash <na...@hursley.ibm.com> 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: tuscany-dev-unsubscribe@ws.apache.org
>> > For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>> >
>> >
>> >
>>
>> -- 
>> Simon C Nash   IBM Distinguished Engineer
>> Hursley Park, Winchester, UK   nash@hursley.ibm.com
>> Tel. +44-1962-815156   Fax +44-1962-818999
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>>
>>
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> 
> 
> 

-- 
Simon C Nash   IBM Distinguished Engineer
Hursley Park, Winchester, UK   nash@hursley.ibm.com
Tel. +44-1962-815156   Fax +44-1962-818999


---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org


Re: Spec APIs in Tuscany distros (was Re: svn commit: r475086)

Posted by Jeremy Boynes <jb...@apache.org>.
On 11/16/06, Simon Nash <na...@hursley.ibm.com> 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: tuscany-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> >
> >
> >
>
> --
> Simon C Nash   IBM Distinguished Engineer
> Hursley Park, Winchester, UK   nash@hursley.ibm.com
> Tel. +44-1962-815156   Fax +44-1962-818999
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org


Re: Spec APIs in Tuscany distros (was Re: svn commit: r475086)

Posted by Simon Nash <na...@hursley.ibm.com>.
Jeremy Boynes wrote:

> On 11/15/06, Simon Nash <na...@hursley.ibm.com> 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: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> 
> 
> 

-- 
Simon C Nash   IBM Distinguished Engineer
Hursley Park, Winchester, UK   nash@hursley.ibm.com
Tel. +44-1962-815156   Fax +44-1962-818999


---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org


Re: Spec APIs in Tuscany distros (was Re: svn commit: r475086)

Posted by Jeremy Boynes <jb...@apache.org>.
On 11/15/06, Simon Nash <na...@hursley.ibm.com> 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: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org


Spec APIs in Tuscany distros (was Re: svn commit: r475086)

Posted by Simon Nash <na...@hursley.ibm.com>.
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 <en...@gmail.com> 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: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> 
> 
> 

-- 
Simon C Nash   IBM Distinguished Engineer
Hursley Park, Winchester, UK   nash@hursley.ibm.com
Tel. +44-1962-815156   Fax +44-1962-818999


---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org


Re: svn commit: r475086 - /incubator/tuscany/branches/sca-java-M2/sca/distribution/build.xml

Posted by Jeremy Boynes <jb...@apache.org>.
On 11/14/06, Raymond Feng <en...@gmail.com> 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: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org


Re: svn commit: r475086 - /incubator/tuscany/branches/sca-java-M2/sca/distribution/build.xml

Posted by Raymond Feng <en...@gmail.com>.
Hi, Jeremy.

Should we have a separate source distro for the SCA spec then?

Thanks,
Raymond
----- Original Message ----- 
From: "Jeremy Boynes" <jb...@apache.org>
To: <tu...@ws.apache.org>
Sent: Tuesday, November 14, 2006 4:57 PM
Subject: Re: svn commit: r475086 - 
/incubator/tuscany/branches/sca-java-M2/sca/distribution/build.xml


> On 11/14/06, rfeng@apache.org <rf...@apache.org> wrote:
>> Log:
>> Add the SCA spec source code to the source distro
>>
>> Modified:
>>     incubator/tuscany/branches/sca-java-M2/sca/distribution/build.xml
>>
>
> This should not be part of the Tuscany distribution.
>
> Please can we keep with the modularity and keep seperate things separate.
> --
> Jeremy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org


Re: svn commit: r475086 - /incubator/tuscany/branches/sca-java-M2/sca/distribution/build.xml

Posted by Jeremy Boynes <jb...@apache.org>.
On 11/14/06, rfeng@apache.org <rf...@apache.org> wrote:
> Log:
> Add the SCA spec source code to the source distro
>
> Modified:
>     incubator/tuscany/branches/sca-java-M2/sca/distribution/build.xml
>

This should not be part of the Tuscany distribution.

Please can we keep with the modularity and keep seperate things separate.
--
Jeremy

---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org