On 5/2/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
[snip]
Simon Laws wrote:
>
>> - tuscany-rmi? Should this be a binding
>>
>>
>> Yes, would be better as tuscany-binding-rmi.
>>
We already have a tuscany-binding-rmi module: the implementation of the
RMI binding.
The tuscany-rmi modul
Simon Laws wrote:
On 5/2/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
[snip]
Simon Laws wrote:
>
>> - tuscany-rmi? Should this be a binding
>>
>>
>> Yes, would be better as tuscany-binding-rmi.
>>
We already have a tuscany-binding-rmi module: the implementation of the
RMI binding.
Th
On 5/2/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
[snip]
Simon Laws wrote:
>
>> - tuscany-rmi? Should this be a binding
>>
>>
>> Yes, would be better as tuscany-binding-rmi.
>>
We already have a tuscany-binding-rmi module: the implementation of the
RMI binding.
The tuscany-rmi modul
[snip]
Simon Laws wrote:
- tuscany-rmi? Should this be a binding
Yes, would be better as tuscany-binding-rmi.
We already have a tuscany-binding-rmi module: the implementation of the
RMI binding.
The tuscany-rmi module defines an RMI hosting extension point, similar
to how the tuscany-h
Hi,
I believe that it is better to wait until having a more consistent version
of what already it is.
2007/5/2, ant elder <[EMAIL PROTECTED]>:
On 5/2/07, Simon Laws <[EMAIL PROTECTED]> wrote:
>
> On 5/2/07, ant elder <[EMAIL PROTECTED]> wrote:
> >
> > On 5/2/07, Simon Laws <[EMAIL PROTECTED]>
On 5/2/07, Simon Laws <[EMAIL PROTECTED]> wrote:
On 5/2/07, ant elder <[EMAIL PROTECTED]> wrote:
>
> On 5/2/07, Simon Laws <[EMAIL PROTECTED]> wrote:
> >
> > On 4/30/07, ant elder <[EMAIL PROTECTED]> wrote:
> > >
> > > Excellent thanks, thats type type feedback I was looking for!
Comments
> > in
On 5/2/07, ant elder <[EMAIL PROTECTED]> wrote:
On 5/2/07, Simon Laws <[EMAIL PROTECTED]> wrote:
>
> On 4/30/07, ant elder <[EMAIL PROTECTED]> wrote:
> >
> > Excellent thanks, thats type type feedback I was looking for! Comments
> in
> > line...
> >
> > On 4/30/07, Jean-Sebastien Delfino <[EMAIL
On 5/2/07, Simon Laws <[EMAIL PROTECTED]> wrote:
On 4/30/07, ant elder <[EMAIL PROTECTED]> wrote:
>
> Excellent thanks, thats type type feedback I was looking for! Comments
in
> line...
>
> On 4/30/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
>
>
>
> I have a few questions and suggesti
On 4/30/07, ant elder <[EMAIL PROTECTED]> wrote:
Excellent thanks, thats type type feedback I was looking for! Comments in
line...
On 4/30/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
I have a few questions and suggestions.
> - tuscany-sca.jar contains .svn directories, I guess they
Excellent thanks, thats type type feedback I was looking for! Comments in
line...
On 4/30/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
I have a few questions and suggestions.
- tuscany-sca.jar contains .svn directories, I guess they should be
removed from the JAR.
I can't see thes
ant elder wrote:
On 4/29/07, ant elder <[EMAIL PROTECTED]> wrote:
What do we want the Tuscany SCA distribution to look like for the next
release? I'll suggest the following straw man as start, please suggest
changes. I'm using the name 'beta1' here till we decide on the real
name.
All the ar
I guess this is the question about what should we call the next release - M3
or beta1 or something else? See:
http://mail-archives.apache.org/mod_mbox/ws-tuscany-dev/200704.mbox/[EMAIL
PROTECTED]
...ant
On 4/29/07, 王洪伟 <[EMAIL PROTECTED]> wrote:
why not with a sign --M3 ?
like this :
tuscan
On 4/29/07, ant elder <[EMAIL PROTECTED]> wrote:
What do we want the Tuscany SCA distribution to look like for the next
release? I'll suggest the following straw man as start, please suggest
changes. I'm using the name 'beta1' here till we decide on the real name.
All the artifacts in the defau
why not with a sign --M3 ?
like this :
tuscany-sca-1.0-M3-beta1.zip
tuscany-sca-1.0-M3-beta1.tar.gz
tuscany-sca-1.0-M3-beta1-src.zip
tuscany-sca-1.0-M3-beta1-src.tar.gz
2007/4/29, ant elder <[EMAIL PROTECTED]>:
What do we want the Tuscany SCA distribution to look like for the next
release? I'l
What do we want the Tuscany SCA distribution to look like for the next
release? I'll suggest the following straw man as start, please suggest
changes. I'm using the name 'beta1' here till we decide on the real name.
All the artifacts in the default build would be published to the maven
repository
15 matches
Mail list logo