<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Am 13.10.11 17:31, schrieb basZero:
    <blockquote
cite="mid:CAOXzDSHfxBPDGUF_6tn7ssrAW=ZExNH1SzZz6qK5otnz5i0MAQ@mail.gmail.com"
      type="cite">sounds great, but I would not reinvent the wheel.</blockquote>
    <blockquote
cite="mid:CAOXzDSHfxBPDGUF_6tn7ssrAW=ZExNH1SzZz6qK5otnz5i0MAQ@mail.gmail.com"
      type="cite">
      <div>checkout Maven Profiles, they do exactly this.</div>
    </blockquote>
    <br>
    I don't think the usage is really the same and I don't think it's
    applicable to the resource configurations,<br>
    but I will have a closer look at it.<br>
    But anyway, your links are very helpful nevertheless, because I
    guess we can learn from it at least and<br>
    also describe the differences in the documentation such that people
    don't get confused.<br>
    <br>
    Thanks for sharing this<br>
    <br>
    Michael<br>
    <blockquote
cite="mid:CAOXzDSHfxBPDGUF_6tn7ssrAW=ZExNH1SzZz6qK5otnz5i0MAQ@mail.gmail.com"
      type="cite">
      <div><br>
      </div>
      <div>if I remember correctly, Maven Profiles existed as separate
        files in version 2.x, from 3.x they have been integrated into
        Maven's settings.xsml:</div>
      <div><br>
      </div>
      <div><a moz-do-not-send="true"
          href="http://maven.apache.org/settings.html#Profiles">http://maven.apache.org/settings.html#Profiles</a></div>
      <div><br>
      </div>
      <div><a moz-do-not-send="true"
href="http://maven.apache.org/guides/introduction/introduction-to-profiles.html">http://maven.apache.org/guides/introduction/introduction-to-profiles.html</a></div>
      <div><br>
      </div>
      <div>Cheers</div>
      <div>Balz<br>
        <br>
        <div title="signature"> </div>
        <div class="gmail_quote">On Tue, Oct 11, 2011 at 9:47 PM,
          Michael Wechner <span dir="ltr"><<a moz-do-not-send="true"
              href="mailto:michael.wechner@wyona.com">michael.wechner@wyona.com</a>></span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hi<br>
            <br>
            Based on some other work it occured to me that it would be
            nice if one could easily differentiate configuration
            parameters for various scenarios/environments, e.g.
            Development, Testing, Staging and Production.<br>
            <br>
            The Yanel configuration itself already provides "local"
            configuration files, but in the case of resource
            configurations this is not the case, e.g.<br>
            <br>
            src/realms/yanel-website/res-configs-repo/data/en/contact.html.yanel-rc<br>
            <br>
            and in particular a parameter like<br>
            <br>
            <yanel:property name="to" value="<a
              moz-do-not-send="true" href="mailto:contact@wyona.com"
              target="_blank">contact@wyona.com</a>"/><br>
            <br>
            needs to be changed for development or testing. At the
            moment one has to keep editing these files<br>
            with the risk to use a value actually intended for another
            scenario/environment and hence creating errors.<br>
            <br>
            I think we could solve this problem in a very elegant way by
            introducing an attribute, e.g.<br>
            <br>
            <yanel:property name="to" value="<a
              moz-do-not-send="true" href="mailto:contact@wyona.com"
              target="_blank">contact@wyona.com</a>"
            env="production"/><br>
            <yanel:property name="to" value="<a
              moz-do-not-send="true"
              href="mailto:michael.wechner@wyona.com" target="_blank">michael.wechner@wyona.com</a>"
            env="development"/><br>
            <br>
            whereas inside<br>
            <br>
            WEB-INF/classes/yanel.xml<br>
            <br>
            the scenario/environment could be set globally, e.g.
            production or development or whatever and based on<br>
            that the right value selected.<br>
            <br>
            WDYT?<br>
            <br>
            Thanks<br>
            <br>
            Michael<br>
            <font color="#888888">
              <br>
              <br>
              -- <br>
              Yanel-development mailing list <a moz-do-not-send="true"
                href="mailto:Yanel-development@wyona.com"
                target="_blank">Yanel-development@wyona.com</a><br>
              <a moz-do-not-send="true"
                href="http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development"
                target="_blank">http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development</a><br>
            </font></blockquote>
        </div>
        <br>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
    </blockquote>
    <br>
  </body>
</html>