We'll have to discuss it on a case by case scenario when it comes to that. One potential I see is related to the pos component. In the start component in the framework stack there is already pos.properties file.
Best regards, Pierre Smits *ORRTIZ.COM <http://www.orrtiz.com>* Services & Solutions for Cloud- Based Manufacturing, Professional Services and Retail & Trade http://www.orrtiz.com On Sat, Mar 21, 2015 at 6:05 PM, Jacques Le Roux < jacques.le.r...@les7arts.com> wrote: > When there are no confusions, that sounds good to me. I see no reasons why > securityext properties file should be named truition.properties! > > Jacques > > Le 20/03/2015 15:03, Pierre Smits a écrit : > >> The same can be applied to the following .properties files: >> >> >> - in applications stack >> - securityext: truition.properties -> securityext.properties >> - workeffort: workeffortsearch.properties -> workeffort.properties >> - in special purpose stack >> - ebay: ebayExport.properties -> ebay.properties >> - ebaystore: EbayStore.properties -> ebaystore.properties >> - googlebase: googleBaseExport.properties -> googlebase.properties >> - googlecheckout: googleCheckout.properties -> >> googlecheckout.properties >> - lucene: search.properties -> lucene.properties >> - pos: parameters.properties -> pos.properties >> - scrum: revision.properties -> scrum.properties >> >> Best regards, >> >> Pierre Smits >> >> *ORRTIZ.COM <http://www.orrtiz.com>* >> Services & Solutions for Cloud- >> Based Manufacturing, Professional >> Services and Retail & Trade >> http://www.orrtiz.com >> >>
