You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by Raymond Feng <en...@gmail.com> on 2007/02/02 07:38:16 UTC
Developing extension code with latest kernel?
Hi,
Most of the extensions in the trunk depend on the pre-spec-changes-SNAPSHOT version of the kernel. What should I do if I want to start to evolve an extension (for example, databinding-sdo) with the latest kernel?
I think of the following steps:
1) Copy the code to pre-spec-changes branch and publish SNAPSHOTs to maven
2) Update the code in trunk to reference the latest version (1.0-incubator-SNAPSHOT) of kernel
Does it make sense?
Thanks,
Raymond
Re: Developing extension code with latest kernel?
Posted by Jean-Sebastien Delfino <js...@apache.org>.
Raymond Feng wrote:
> Hi,
>
> Here's the situation in my case:
>
> 1) I want to improve databinding in the latest kernel which will
> change (for example, adding a method to an interface, or refactoring
> some code) the SPIs and core.
>
> 2) I want to evolve the databinding extensions such as SDO, JAXB and
> AXIOM at the same time.
>
> If the databindings are still being consumed at the pre-spec-changes
> kernel level, then we have to maintain them by copying them to the
> branch. Otherwise, we can just move forward in the trunk.
>
> Thanks,
> Raymond
>
> ----- Original Message ----- From: "Jean-Sebastien Delfino"
> <js...@apache.org>
> To: <tu...@ws.apache.org>
> Sent: Friday, February 02, 2007 8:25 AM
> Subject: Re: Developing extension code with latest kernel?
>
>
>> Raymond Feng wrote:
>>> Hi,
>>>
>>> Most of the extensions in the trunk depend on the
>>> pre-spec-changes-SNAPSHOT version of the kernel. What should I do if
>>> I want to start to evolve an extension (for example,
>>> databinding-sdo) with the latest kernel?
>>>
>>> I think of the following steps:
>>>
>>> 1) Copy the code to pre-spec-changes branch and publish SNAPSHOTs to
>>> maven
>>> 2) Update the code in trunk to reference the latest version
>>> (1.0-incubator-SNAPSHOT) of kernel
>>>
>>> Does it make sense?
>>>
>>> Thanks,
>>> Raymond
>>>
>>
>> Can you describe the change to the kernel that you need for your
>> databinding-sdo work? Is it a big change? Does it affect any SPIs?
>>
>> --
>> Jean-Sebastien
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>>
>
Ok, what you initially proposed sounds good me. If I understand correctly:
1) Copy the current databinding extension code to the pre-spec-changes
branch. This will allow others to continue to use it on top of the
pre-spec-changes kernel (and maybe make a few small bug fixes in it if
needed).
2) Change the databinding extension in trunk to reference the trunk
version of the kernel, and evolve it in the trunk.
3) Make your core and SPI changes in the trunk version of the kernel.
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: Developing extension code with latest kernel?
Posted by Raymond Feng <en...@gmail.com>.
Hi,
Here's the situation in my case:
1) I want to improve databinding in the latest kernel which will change (for
example, adding a method to an interface, or refactoring some code) the SPIs
and core.
2) I want to evolve the databinding extensions such as SDO, JAXB and AXIOM
at the same time.
If the databindings are still being consumed at the pre-spec-changes kernel
level, then we have to maintain them by copying them to the branch.
Otherwise, we can just move forward in the trunk.
Thanks,
Raymond
----- Original Message -----
From: "Jean-Sebastien Delfino" <js...@apache.org>
To: <tu...@ws.apache.org>
Sent: Friday, February 02, 2007 8:25 AM
Subject: Re: Developing extension code with latest kernel?
> Raymond Feng wrote:
>> Hi,
>>
>> Most of the extensions in the trunk depend on the
>> pre-spec-changes-SNAPSHOT version of the kernel. What should I do if I
>> want to start to evolve an extension (for example, databinding-sdo) with
>> the latest kernel?
>>
>> I think of the following steps:
>>
>> 1) Copy the code to pre-spec-changes branch and publish SNAPSHOTs to
>> maven
>> 2) Update the code in trunk to reference the latest version
>> (1.0-incubator-SNAPSHOT) of kernel
>>
>> Does it make sense?
>>
>> Thanks,
>> Raymond
>>
>
> Can you describe the change to the kernel that you need for your
> databinding-sdo work? Is it a big change? Does it affect any SPIs?
>
> --
> Jean-Sebastien
>
>
> ---------------------------------------------------------------------
> 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: Developing extension code with latest kernel?
Posted by Jean-Sebastien Delfino <js...@apache.org>.
Raymond Feng wrote:
> Hi,
>
> Most of the extensions in the trunk depend on the pre-spec-changes-SNAPSHOT version of the kernel. What should I do if I want to start to evolve an extension (for example, databinding-sdo) with the latest kernel?
>
> I think of the following steps:
>
> 1) Copy the code to pre-spec-changes branch and publish SNAPSHOTs to maven
> 2) Update the code in trunk to reference the latest version (1.0-incubator-SNAPSHOT) of kernel
>
> Does it make sense?
>
> Thanks,
> Raymond
>
Can you describe the change to the kernel that you need for your
databinding-sdo work? Is it a big change? Does it affect any SPIs?
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: Developing extension code with latest kernel?
Posted by ant elder <an...@gmail.com>.
On 2/2/07, Raymond Feng <en...@gmail.com> wrote:
>
> Hi,
>
> Most of the extensions in the trunk depend on the
> pre-spec-changes-SNAPSHOT version of the kernel. What should I do if I want
> to start to evolve an extension (for example, databinding-sdo) with the
> latest kernel?
>
> I think of the following steps:
>
> 1) Copy the code to pre-spec-changes branch and publish SNAPSHOTs to maven
> 2) Update the code in trunk to reference the latest version (
> 1.0-incubator-SNAPSHOT) of kernel
>
> Does it make sense?
This isn't how I understood the new structure would be used. It already can
be quite confusing working out what things are using which versions of
things (even the maven reactor builds get confused!) and I worry that doing
this could make that even worse. Could any/all the other extensions also
start using the current trunk code instead of the pre-spec branch - Axis2,
JavaScript etc? If so in some respects it would be simpler to just copy
everything to the pre-spec branch and put everything back working off trunk,
at least then everything stays in sync.
Is the real problem here that we need more regular releases of the various
parts of Tuscany, and proper releases not just variously named SNAPSHOT
builds? I think we've been a bit scared of releases due to all the
difficulties we've had in the past, but they shouldn't be so scary. If we
decide something is at a suitably stable point can't we just release things
like tuscany-core-M3-200702021055.jar? We don't need all the hoopla around
getting samples up and running and massive website updates etc, its almost
just tag, sign, vote and wait a few days, the IPMC seem quite good with
release votes these days. If others agree with this approach I volunteer to
be RM to get some stable releases out more regularly. What do people think?
...ant
Re: Developing extension code with latest kernel?
Posted by Rick <cr...@gmail.com>.
Raymond Feng wrote:
> Hi,
>
> Most of the extensions in the trunk depend on the pre-spec-changes-SNAPSHOT version of the kernel. What should I do if I want to start to evolve an extension (for example, databinding-sdo) with the latest kernel?
>
> I think of the following steps:
>
> 1) Copy the code to pre-spec-changes branch and publish SNAPSHOTs to maven
Taking databinding-sdo as an example if you copied to the pre-spec-changes,
would you also remove the module from pom.xml in services ? Today all of
services builds incubator-snapshot versions which if you build services from its
root just like building the java root would get you the incubator snapshot
version of databinding-sdo. Or am I miss understanding?
I think this also presumes the changes introduced are easily compatible with
the older "pre-spec-changes" kernel.
Would any sample/itests need to move off of referencing the sdo-databinding
incubator version to the pre-spec-changes? I think yes, but not 100% sure.
As you keep evolving databinding-sdo in the trunk (@incubator-SNAPSHOT) you
continue to update/merge to the pre-spec-changes branch and publish
pre-spec-changes to maven snapshot repo to validate with itest and possilby run
samples?
> 2) Update the code in trunk to reference the latest version (1.0-incubator-SNAPSHOT) of kernel
Would this not slowly migrate us back to where we came from as more extensions
and services followed suit?
>
> Does it make sense?
>
> Thanks,
> Raymond
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org