cucumber-confluence

The aim of this project is to provide a set of tools to automate tasks that involve gherkin/cucumber Feature files as an input and Confluence as a consumer of this output.

At the moment there is the possibility to transform feature files to confluence storage format (XHTML) through a command line interface or a maven plugin.

# java -jar cucumber-confluence-cli-1.0-SNAPSHOT.jar 

usage: [-f FILEORDIR] [[-nt]|[-j SERVERNAME]] [-o DIR]
 -j,--jira-server   Name of the Jira-Server as it is known to Confluence.
 -o,--output-dir    Path to save xhtml files to. Default is working
                    directory
 -nt,--no-tags      Wheter tags should be suppressed from the output. Tags
                    are processed by default
 -f,--file          File to read or path to scan for '.feature' files.
                    Default is working directory

<plugins>
  <plugin>
    <groupId>org.plafue.cucumber-confluence</groupId>
    <artifactId>cucumber-confluence-maven-plugin</artifactId>
    <version>1.0-SNAPSHOT</version>
    <executions>
      <execution>
        <id>parse</id>
        <goals>
          <goal>parse</goal> 
          <!-- Currently only the goal "parse" is provided. 
          The plugin is not hooked to any lifecycle phase. Use as you see fit. -->
        </goals>
      </execution>
      <configuration>  <!-- All settings are optional -->
        <outputDirectory>
           <!-- Output directory.  All output files match the name of the source, 
                but with the suffix .xhtml instead of .feature.
                Default: ${project.build.directory}/cucumber-confluence" 
                (aka "target/cucumber-confluence") -->
         </outputDirectory>
        <inputFile> 
          <!-- If a directory, all "*.feature" files within it will be parsed. 
               Default: ${basedir} (aka location of your pom.xml) -->
        </inputFile>
        <ignoreTags>
          <!-- Whether Tags are ignored. Default: false -->
        </ignoreTags>
        <jiraServer>
          <!-- When set, implicitly activates the parsing of Jira issues when used 
          in tags, eg (@PLB-122). This option and ignoreTags are mutually exclusive.
          Default: null -->
        </jiraServer>
      </configuration>
    </executions>
  </plugin>
</plugins>