-
1. Re: Updating S-RAMP Artifact content
eric.wittmann Oct 2, 2014 10:01 AM (in response to giorgimode)I think the preferred approach to managing environment-specific configuration is to make sure it is deployed external to (along side) the JAR. This way the JAR itself is portable across all runtime environments. The configuration might be a properties file that gets deployed to the target platform's config directory, with different settings for the different environments, and is simply deployed first (also managed within s-ramp/dtgov).
That said, the deployment workflow is fully customizable, so you could implement a custom task in the workflow to insert the config into the JAR. Another possibility with the next release is to implement a custom deployer which would do that work prior to deploying to the target environment.
-
2. Re: Updating S-RAMP Artifact content
giorgimode Oct 2, 2014 10:37 AM (in response to eric.wittmann)Good to know. When should we expect the new release?
-
3. Re: Updating S-RAMP Artifact content
eric.wittmann Oct 2, 2014 10:53 AM (in response to giorgimode)We're doing our best to get it out this week! We're running up against some issues when running on the Fuse platform, but I think we're closing in on it.
-
4. Re: Updating S-RAMP Artifact content
eric.wittmann Oct 9, 2014 7:28 AM (in response to giorgimode)In case you didn't see the announcement, the new release (1.4.0.Final) came out a few days ago. You can find it here:
-
5. Re: Updating S-RAMP Artifact content
giorgimode Oct 9, 2014 8:50 AM (in response to eric.wittmann)I have been working on it already. Thanks.