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"
<[EMAIL PROTECTED]>
To: <[email protected]>
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
