Hi, I think if you want to manage your own version of the such files the way to do it would be to keep your copy in a place like "modules/distribution/src/main/resources/carbon-home/" in the ES and copy from there using the bin.xml. Overwriting the file added by the IS feature will cause problems to all the other products that tries to install your feature.
Regards, Pulasthi On Fri, Jul 18, 2014 at 2:01 PM, Ayesha Dissanayaka <[email protected]> wrote: > Hi, > > Currently we keep a copy of "identity.xml" in ES source and pack it with > the ES distribution. This causes to override the identity.xml file comes > with IS [01], and we have to manually update the file to sync with IS. > > The reason we keep a local copy is that identity.xml file packed with IS > does not contains commits[02][03] that we require for ES pack. > > What would be the best way to continue with managing this 'identity.xml' > file. > - commit the changes to IS /if it is OK to merge the changes[04] > - continue with managing a copy and update manually > - is there any other way to handle this? > > [01] https://wso2.org/jira/browse/STORE-472 > [02] > https://github.com/wso2/enterprise-store/commit/74d33514bc3078e9bd8794f32eaf46978ab044b1 > [03] > https://github.com/wso2/enterprise-store/commit/1062d2ae349206cc5190a450a1a1c8d0324b9ee8 > [04] > https://github.com/wso2/enterprise-store/commits/1.2.0/modules/distribution/src/repository/conf/identity.xml > > -- > *Ayesha Dissanayaka* > Software Engineer, > WSO2, Inc : http://wso2.com > <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> > 20, Palmgrove Avenue, Colombo 3 > E-Mail: [email protected] <[email protected]> > -- -- Pulasthi Supun Software Engineer; WSO2 Inc.; http://wso2.com, Email: [email protected] Mobile: +94 (71) 9258281 Blog : http://pulasthisupun.blogspot.com/ Git hub profile: https://github.com/pulasthi
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
