karaf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré ...@nanthrax.net>
Subject Re: [DISCUSS] Best way to provide a migration to the new 1.3.0 features schema for downstream projects
Date Thu, 11 Jun 2015 07:47:35 GMT
Hi Guillaume,

I would do for the second one, I think it's easier and make sense for 
backward compatibility.

Regards
JB


On 06/11/2015 08:51 AM, Guillaume Nodet wrote:
> I want to work on a nice way to migrate to the new 1.3.0 schema for
> features for downstream projects (pax-web, cxf, activemq, etc…).
> I have two possible ways in mind which I'd like to discuss.
>
> The first one would be to write an additional mojo for the maven plugin
> which would translate the new 1.3.0 schema to older schemas, deleting
> unsupported stuff.  The mojo would thus generate an additional schema with
> a different classifier, either for the old schema, or for the new one.
>
> Another way would be to add this translation tool inside a bug-fix release
> of older branches, so that the old feature service could support the 1.3.0
> syntax.  The drawback is that this would not work on already existing
> releases obviously.
>
> Or we could do both.
>
> Fwiw, I haven't experimented yet on the translation, so for complex
> features definition using the new schema, I'm not sure yet if the
> translation will lead to usable results.  As a last resort, if it's not
> usable, the downstream projects can manually provide the two repositories.
>
> Thoughts ?
>
> Guillaume Nodet
>

-- 
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Mime
View raw message