projects directly, for example Eclipse users can select Import… → Existing Maven Projects from the File menu. If you can’t directly import your project into your IDE, you may be able to generate IDE metadata you’ve deployed to Cloud Foundry, you would do the following: Select Run Configurations… from the Run menu. Create a new Java Application “launch configuration”. Browse for the my-app project. Use org.springframework http://dev.bar.com name: Developer Setup prod: url: http://foo.bar.com name: My Cool App Would be transformed into these properties: environments.dev.url=http://dev.bar.com environments

projects directly, for example Eclipse users can select Import… → Existing Maven Projects from the File menu. If you can’t directly import your project into your IDE, you may be able to generate IDE metadata you’ve deployed to Cloud Foundry, you would do the following: Select Run Configurations… from the Run menu. Create a new Java Application “launch configuration”. Browse for the my-app project. Use org.springframework http://dev.bar.com name: Developer Setup prod: url: http://foo.bar.com name: My Cool App Would be transformed into these properties: environments.dev.url=http://dev.bar.com environments

projects directly, for example Eclipse users can select Import… → Existing Maven Projects from the File menu. If you can’t directly import your project into your IDE, you may be able to generate IDE metadata you’ve deployed to Cloud Foundry, you would do the following: Select Run Configurations… from the Run menu. Create a new Java Application “launch configuration”. Browse for the my-app project. Use org.springframework example in a UN*X shell: $ SPRING_APPLICATION_JSON='{"foo":{"bar":"spam"}}' java -jar myapp.jar In this example you will end up with foo.bar=spam in the Spring Environment. You can also supply the JSON

projects directly, for example Eclipse users can select Import… → Existing Maven Projects from the File menu. If you can’t directly import your project into your IDE, you may be able to generate IDE metadata you’ve deployed to Cloud Foundry, you would do the following: Select Run Configurations… from the Run menu. Create a new Java Application “launch configuration”. Browse for the my-app project. Use org.springframework example in a UN*X shell: $ SPRING_APPLICATION_JSON='{"foo":{"bar":"spam"}}' java -jar myapp.jar In this example you will end up with foo.bar=spam in the Spring Environment. You can also supply the JSON

projects directly, for example Eclipse users can select Import… → Existing Maven Projects from the File menu. If you can’t directly import your project into your IDE, you may be able to generate IDE metadata you’ve deployed to Cloud Foundry, you would do the following: Select Run Configurations… from the Run menu. Create a new Java Application “launch configuration”. Browse for the my-app project. Use org.springframework example in a UN*X shell: $ SPRING_APPLICATION_JSON='{"foo":{"bar":"spam"}}' java -jar myapp.jar In this example you will end up with foo.bar=spam in the Spring Environment. You can also supply the JSON

projects directly, for example Eclipse users can select Import… → Existing Maven Projects from the File menu. If you can’t directly import your project into your IDE, you may be able to generate IDE metadata you’ve deployed to Cloud Foundry, you would do the following: Select Run Configurations… from the Run menu. Create a new Java Application “launch configuration”. Browse for the my-app project. Use org.springframework example in a UN*X shell: $ SPRING_APPLICATION_JSON='{"foo":{"bar":"spam"}}' java -jar myapp.jar In this example you will end up with foo.bar=spam in the Spring Environment. You can also supply the JSON

projects directly, for example Eclipse users can select Import… → Existing Maven Projects from the File menu. If you can’t directly import your project into your IDE, you may be able to generate IDE metadata you’ve deployed to Cloud Foundry, you would do the following: Select Run Configurations… from the Run menu. Create a new Java Application “launch configuration”. Browse for the my-app project. Use org.springframework example in a UN*X shell: $ SPRING_APPLICATION_JSON='{"foo":{"bar":"spam"}}' java -jar myapp.jar In this example you will end up with foo.bar=spam in the Spring Environment. You can also supply the JSON

projects directly, for example Eclipse users can select Import… → Existing Maven Projects from the File menu. If you can’t directly import your project into your IDE, you may be able to generate IDE metadata deployed to Cloud Foundry, you would do the following: • Select Run Configurations… from the Run menu. • Create a new Java Application “launch configuration”. • Browse for the my-app project. • Use example in a UN*X shell: $ SPRING_APPLICATION_JSON='{"foo":{"bar":"spam"}}' java -jar myapp.jar In this example you will end up with foo.bar=spam in the Spring Environment. You can also supply the JSON

projects directly, for example Eclipse users can select Import… → Existing Maven Projects from the File menu. If you can’t directly import your project into your IDE, you may be able to generate IDE metadata you’ve deployed to Cloud Foundry, you would do the following: Select Run Configurations… from the Run menu. Create a new Java Application “launch configuration”. Browse for the my-app project. Use org.springframework example in a UN*X shell: $ SPRING_APPLICATION_JSON='{"foo":{"bar":"spam"}}' java -jar myapp.jar In this example you will end up with foo.bar=spam in the Spring Environment. You can also supply the JSON

projects directly, for example Eclipse users can select Import… → Existing Maven Projects from the File menu. If you can’t directly import your project into your IDE, you may be able to generate IDE metadata you’ve deployed to Cloud Foundry, you would do the following: Select Run Configurations… from the Run menu. Create a new Java Application “launch configuration”. Browse for the my-app project. Use org.springframework example in a UN*X shell: $ SPRING_APPLICATION_JSON='{"foo":{"bar":"spam"}}' java -jar myapp.jar In this example you will end up with foo.bar=spam in the Spring Environment. You can also supply the JSON