Code Search for Developers
 
 
  

state.xml from SmartFrog at Krugle


Show state.xml syntax highlighted

<project name="state">

  <description>

    This is a modelling of the state of a system.

    These targets do not contain any actions, instead they are things you can
    depend on an application being in before a next operation.

    This represents an alternate way of viewing a build. Instead of describing
    targets as actions "compile", "deploy", etc, you can have state targets that
    represent states an application passes through during a build. The action targets
    are those transformations applied to an application to get from one state to another.

  </description>
  <target name="initialized" />

  <target name="ready-to-compile" depends="initialized"/>

  <target name="compiled" depends="ready-to-compile"/>

  <target name="ready-to-package" depends="compiled"/>

  <target name="packaged" depends="ready-to-package"/>

  <target name="ready-to-compile-tests" depends="packaged"/>

  <target name="tests-compiled" depends="ready-to-compile-tests"/>

  <target name="ready-to-package-tests" depends="tests-compiled"/>

  <target name="tests-packaged" depends="ready-to-package-tests"/>

  <target name="ready-to-test" depends="tests-packaged"/>

  <target name="ready-to-system-test" depends="ready-to-test"/>

  <target name="system-tested" depends="ready-to-system-test"/>

  <target name="tested" depends="system-tested"/>

  <target name="test" depends="tested"/>

  <target name="ready-to-deploy" depends="tested"/>

  <target name="deployed" depends="ready-to-deploy"/>

  <!-- documentation states -->

  <!--state in which all other docs are finished.-->

  <target name="ready-to-javadoc" depends="compiled"/>

  <target name="javadocs-finished" depends="ready-to-javadoc"/>

  <target name="ready-to-process-other-docs" depends="ready-to-javadoc" />

  <target name="other-docs-finished" depends="ready-to-process-other-docs"/>

  <target name="documents-processed"
      depends="javadocs-finished,other-docs-finished"/>

  <target name="ready-to-package-documents" depends="documents-processed">

  </target>

  <target name="documents-packaged" depends="ready-to-package-documents" />

  <!--publishing ::= saving the artifacts to a (shared) repository-->
  <target name="ready-to-publish" depends="packaged,documents-processed"/>

  <target name="published" depends="ready-to-publish"/>

  <!--installing ::= saving the artifacts to SFHOME-->
  <target name="ready-to-install" depends="packaged"/>

  <target name="installed" depends="ready-to-install"/>

  <target name="ready-to-clean" />

  <target name="cleaned" depends="ready-to-clean"/>


  <target name="ready-to-dist" depends="packaged,documents-packaged" />

  <target name="dist" depends="packaged"
      description="create a distribution"/>

  <target name="published-distribution" depends="dist,published"/>

  <!-- a noop state by default-->
  <target name="pdf-doc-folder" />
</project>



See more files for this project here

SmartFrog

SmartFrog (Smart Framework for Object Groups) is a framework for configuring and automatically activating distributed applications. \r\nThe SmartFrog framework is released under LGPL license.\r\nMore info at: www.smartfrog.org

Project homepage: http://sourceforge.net/projects/smartfrog
Programming language(s): Java,XML
License: other

  checkstyle/
    checkstyle-config
    checkstyle-frames.xsl
    checkstyle-policy.xml
    checkstyle-text.xsl
    checkstyle-xdoc.xsl
  checkstyle.xml
  classpaths.xml
  compile-and-jar-mixin.xml
  core.xml
  daemon.xml
  dist.xml
  gui.xml
  ivy-mixin.xml
  javadoc-mixin.xml
  m2.xml
  macros-mixin.xml
  maven-v4_0_0.xsd
  rpm.xml
  security-mixin.xml
  sftasks.xml
  state.xml
  systemtest.xml
  unittest.xml