<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:clearspace="http://www.jivesoftware.com/xmlns/clearspace/rss" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>Clearspace Server Syndication Feed</title>
    <link>https://grep.elasticpath.com/blogs</link>
    <description>A syndication feed of all the blogs on this system</description>
    <pubDate>Mon, 25 Jan 2010 18:33:25 GMT</pubDate>
    <generator>Clearspace 2.5.7 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2010-01-25T18:33:25Z</dc:date>
    <item>
      <title>Simplifying Deployment with Spring and the EP Settings Framework</title>
      <link>https://grep.elasticpath.com/community/techblog/blog/2010/01/25/simplifying-deployment-with-spring-and-the-ep-settings-framework</link>
      <description>Before the settings framework was introduced in EP, many environment specific settings were hard coded in config files contained within the WAR. Every time we performed a deployment, we needed to post-process the WAR artifacts to match the environment</description>
      <pubDate>Mon, 25 Jan 2010 18:33:25 GMT</pubDate>
      <author>rheinen</author>
      <guid>https://grep.elasticpath.com/community/techblog/blog/2010/01/25/simplifying-deployment-with-spring-and-the-ep-settings-framework</guid>
      <dc:date>2010-01-25T18:33:25Z</dc:date>
      <wfw:comment>https://grep.elasticpath.com/community/techblog/blog/comment/simplifying-deployment-with-spring-and-the-ep-settings-framework</wfw:comment>
      <wfw:commentRss>https://grep.elasticpath.com/community/techblog/blog/feeds/comments?blogPost=1094</wfw:commentRss>
    </item>
  </channel>
</rss>


