I think the best way for providing bug fixes is having bundle fragments without complicating features mechanism. You may release fragment attached to bundle which must be fixed. Just by using another feature repository.
Cheers, Łukasz Dywicki -- [email protected] Twitter: ldywicki Blog: http://dywicki.pl Code-House - http://code-house.org Wiadomość napisana przez Christian Schneider <[email protected]> w dniu 26 lut 2013, o godz. 05:45: > I would do the patch only in memory. So the repo can stay as is. > > Christian > > On 26.02.2013 09:49, Jean-Baptiste Onofré wrote: >> Hi Christian, >> >> Where would you update the features XML ? In the system repo ? >> When you call a feature refresh, do you take only from system repo or from a >> remote repo ? >> >> Regards >> JB >> >> On 02/26/2013 09:46 AM, Christian Schneider wrote: >>> Hi all, >>> >>> sometimes we have the issue that a feature file of an already released >>> project is incorrect. Another similar case is if a small issue appears >>> that can be fixed by just patching a single bundle. >>> In both cases it is necessary to change an existing feature file to make >>> this work without a new release and without making user apps bump up the >>> dependency to the feature file to the next bugfix release number. >>> >>> So I thought about a way to patch feature files at runtime. >>> >>> The idea is to have a config with: >>> <mvn url of feature>:<path to patch> >>> >>> This config would make the feature command apply the patches to the >>> named feature files after loading them. So a user could patch their >>> feature files to quickly fix simple issues. >>> >>> What do you think? >>> >>> Christian >>> >> > > > -- > Christian Schneider > http://www.liquid-reality.de > > Open Source Architect > http://www.talend.com >
