Brett,

I noticed that some of the content that you cleaned was mine..  What steps
did you follow to do this?  I try and keep with the existing format on xml
files, but find it hard sometimes..

Eric

> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Saturday, June 26, 2004 4:30 AM
> To: [EMAIL PROTECTED]
> Subject: cvs commit: maven-plugins/cruisecontrol/xdocs faq.fml
>
>
> brett       2004/06/25 19:30:14
>
>   Modified:    cruisecontrol/xdocs faq.fml
>   Log:
>   clean format
>
>   Revision  Changes    Path
>   1.2       +33 -39    maven-plugins/cruisecontrol/xdocs/faq.fml
>
>   Index: faq.fml
>   ===================================================================
>   RCS file: /home/cvs/maven-plugins/cruisecontrol/xdocs/faq.fml,v
>   retrieving revision 1.1
>   retrieving revision 1.2
>   diff -u -r1.1 -r1.2
>   --- faq.fml 31 May 2004 15:56:22 -0000      1.1
>   +++ faq.fml 26 Jun 2004 02:30:14 -0000      1.2
>   @@ -1,14 +1,14 @@
>    <?xml version="1.0" encoding="ISO-8859-1"?>
>   -<!--
>   +<!--
>    /*
>     * Copyright 2001-2004 The Apache Software Foundation.
>   - *
>   + *
>     * Licensed under the Apache License, Version 2.0 (the "License");
>     * you may not use this file except in compliance with the License.
>     * You may obtain a copy of the License at
>   - *
>   + *
>     *      http://www.apache.org/licenses/LICENSE-2.0
>   - *
>   + *
>     * Unless required by applicable law or agreed to in writing, software
>     * distributed under the License is distributed on an "AS IS" BASIS,
>     * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either
> express or implied.
>   @@ -23,24 +23,21 @@
>
>      <part id="General">
>        <title>General</title>
>   -
>   +
>        <faq id="change-template">
>          <question>How do I change the template used to generate
> <code>cruisecontrol.xml</code> configuration file?</question>
>          <answer>
>   -           If you specify your own
> maven.cruisecontrol.template, then that will be used
>   -           instead.  If you want to wrap all of your logic up
> in your own plugin so that
>   -           you don't have to set each project individually,
> then specify it like this:
>   -
> <code>maven.cruisecontrol.template=${maven.home}/plugins/my-compan
> y-plugin-0.1/plugin-resources/cruisecontrol.jsl</code>
>   -           and add to your plugin.xml this:
>   -           <source>
>   -<![CDATA[
>   +        If you specify your own maven.cruisecontrol.template,
> then that will be used
>   +        instead.  If you want to wrap all of your logic up in
> your own plugin so that
>   +        you don't have to set each project individually, then
> specify it like this:
>   +
> <code>maven.cruisecontrol.template=${maven.home}/plugins/my-compan
> y-plugin-0.1/plugin-resources/cruisecontrol.jsl</code>
>   +        and add to your plugin.xml this:
>   +        <source><![CDATA[
>    <preGoal name="build:start">
>   -           <ant:property name="maven.cruisecontrol.template"
> value="${anite.cruisecontrol.template}"/>
>
>   -           <maven:pluginVar
> plugin="maven-cruisecontrol-plugin"
> property="maven.cruisecontrol.template" var="loc"/>
>   -</preGoal>
>   -]]>
>   -           </source>
>   -           Note, this is a very brittle solution and
> suggestions on how to not hardcode the path would be appreciated!
>   +  <ant:property name="maven.cruisecontrol.template"
> value="${anite.cruisecontrol.template}"/>
>   +  <maven:pluginVar plugin="maven-cruisecontrol-plugin"
> property="maven.cruisecontrol.template" var="loc"/>
>   +</preGoal>]]></source>
>   +        Note, this is a very brittle solution and suggestions
> on how to not hardcode the path would be appreciated!
>          </answer>
>        </faq>
>
>   @@ -57,25 +54,22 @@
>          <answer>
>            I specified it like this in my own plugin, this would
> work in your maven.xml as well:
>            <p>
>   -        <source>
>   -<![CDATA[
>   +          <source><![CDATA[
>    <preGoal name="cruisecontrol:validate">
>   -   <ant:echo message="Generating CruiseControl configuration
> for ${systemScope['os.name']} platform. "/>
>   -           <j:choose>
>   -           <j:when
> test="${systemScope['os.name'].startsWith('Windows')}">
>   -                           <ant:property
> name="maven.cruisecontrol.home"
> value="${anite.cruisecontrol.windows.home}"/>
>   -                   <ant:property
> name="anite.cruisecontrol.mavenscript"
> value="${myplugin.cruisecontrol.windows.mavenscript}"/>
>   -           </j:when>
>   -                   <j:otherwise>
>   -                                   <ant:property
> name="maven.cruisecontrol.home"
> value="${myplugin.cruisecontrol.linux.home}"/>
>   -                           <ant:property
> name="myplugin.cruisecontrol.mavenscript"
> value="${myplugin.cruisecontrol.linux.mavenscript}"/>
>   -                   </j:otherwise>
>   -           </j:choose>
>   -   <ant:echo
> message="maven.cruisecontrol.template:${maven.cruisecontrol.template}"/>
>   -</preGoal>
>   -           ]]>
>   -           </source>
>   -           </p>
>   +  <ant:echo message="Generating CruiseControl configuration
> for ${systemScope['os.name']} platform. "/>
>   +  <j:choose>
>   +    <j:when test="${systemScope['os.name'].startsWith('Windows')}">
>   +      <ant:property name="maven.cruisecontrol.home"
> value="${anite.cruisecontrol.windows.home}"/>
>   +      <ant:property name="anite.cruisecontrol.mavenscript"
> value="${myplugin.cruisecontrol.windows.mavenscript}"/>
>   +    </j:when>
>   +    <j:otherwise>
>   +      <ant:property name="maven.cruisecontrol.home"
> value="${myplugin.cruisecontrol.linux.home}"/>
>   +      <ant:property name="myplugin.cruisecontrol.mavenscript"
> value="${myplugin.cruisecontrol.linux.mavenscript}"/>
>   +    </j:otherwise>
>   +  </j:choose>
>   +  <ant:echo
> message="maven.cruisecontrol.template:${maven.cruisecontrol.template}"/>
>   +</preGoal>]]></source>
>   +        </p>
>          </answer>
>        </faq>
>
>   @@ -84,15 +78,15 @@
>          <answer>
>            A neat trick of the cruisecontrol plugin is that if
> you specify a single configuration file for all your
>            projects, then the plugin will just install/update the
> one your are working on.  So, in your project.xml
>   -        set
> <code>maven.cruisecontrol.config=c:/cruisecontrol.xml</code> or maybe
>   +        set
> <code>maven.cruisecontrol.config=c:/cruisecontrol.xml</code> or maybe
>
> <code>maven.cruisecontrol.config=${maven.cruisecontrol.home}/cruis
> econtrol.xml</code> for use in cross
>            platform situations.  Unfortunantly, I haven't been
> able to have a plugin set this value, so you need
>            to put it in all your projects.
>          </answer>
>   -    </faq>
>   +    </faq>
>
>
>      </part>
>   -
>   +
>    </faqs>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to