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