On Nov 9, 2010, at 2:31 AM, Johan Henselmans wrote: > Greetings, > > Once again I have been bitten by a human error (me) that forgot to move a > properties file from test to deployment. > > I want to make sure the human error (me) is gotten rid of.
Don't do it man! Think of your family! Think of Belgian beer!!! > The situation is as follows: I have different settings per customer, as they > differ in third party settings, connections to banks and all that. They are > stored in their respective Properties.customerA, config.properties.customerA, > application.properties.customerA etc in Resources and folders inside > Resources. > > I'd like to create a deployment per customer, so I could say > hudson|maven|ant|make|bash create a deployment for customer a, or b, or all > customers in their respective folders, upload to deployment servers, then per > customer server click on deploy button and wait until the support calls come > in. > > What do you people use to do that, which fits in the normal process of > eclipse, write something, test, fix, test, fix, test, rewrite, forget to > test, deploy? > > Anybody that would like to share their experience. What I have done in the past is to have a framework per customer (same name, e.g. AppCustomization.framework). That gets installed/copied per customer (needs embedded builds or per customer installation directories). It should be easy to add a post-build copy of properties per customer in Ant. Chuck -- Chuck Hill Senior Consultant / VP Development Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems. http://www.global-village.net/products/practical_webobjects
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-deploy mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com This email sent to [email protected]
