Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Citrus-Maven-Plugin: Documentation differs from actual implementation #452

Closed
mischcon opened this issue Aug 23, 2018 · 1 comment
Closed
Labels
State: Won't fix For issues that will not be fixed

Comments

@mischcon
Copy link

Citrus Version Tested with 2.7.6 and 2.8.0-SNAPSHOT

According to the official documentation the Citrus-Maven-Plugin should have 4 goals.

image

The actual implementation of the plugin has not only more goals, but some of the goals mentioned in the documentation are (not long) part of the plugin.

[INFO] citrus-maven-plugin 2.7.6
  Citrus Maven Plugin

This plugin has 5 goals:

citrus:create-docs
  Creates test documentation in interactive mode. Either uses mode excel for MS
  Excel output or html for HTML web page output.

citrus:create-test
  Creates new Citrus test cases with empty XML test file and executable Java
  class. Mojo offers an interactive mode, where the plugin prompts for
  parameters during execution.

citrus:generate-docs
  Generates test overview documentation based on plugin configuration. Html
  documentation creates a web page that contains a list of all available tests
  with meta information. Excel documentation creates a table of all available
  tests with meta information such as name, author, status and so on.

citrus:generate-tests

citrus:help
  Display help information on citrus-maven-plugin.
  Call mvn citrus:help -Ddetail=true -Dgoal=<goal-name> to display parameter
  details.

I am not sure whether or not this is the right place for this issue, since there is also a repository for the citrus website. Please move the issue if you think it should be located elsewhere.

@svettwer
Copy link
Contributor

Hi!

Thx for the hint. I've created citrusframework/citrus-website#1 in the website repo, so I'll close this one.

BR,
Sven

@svettwer svettwer added the State: Won't fix For issues that will not be fixed label Sep 18, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
State: Won't fix For issues that will not be fixed
Projects
None yet
Development

No branches or pull requests

2 participants