Juan Pablo Aroztegi wrote: > The .settings/org.eclipse.wst.common.component file currently includes > the context name. If anyone wants to use a name different to "openbravo" > they have to modify this file, and therefore it appears as modified in > the SCM's working directory. And this is uncomfortable. > > To prevent this in other files like Openbravo.properties and log4j.lcf > we have them as templates, and the setup tools fill them with the chosen > values. We could do the same with this file.
Hi, this would force every eclipse user to setup one more thing before he can start to work. Another way would be to add it to the .hgignore file. Meaning no extra work for most people, but extra work if you want to modify and commit it. But this way it would be only extra work for 1-2 people and i suppose not so often.. Regards, Stefan ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Openbravo-development mailing list Openbravo-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openbravo-development
