[
http://jira.codehaus.org/browse/MOJO-1236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=149275#action_149275
]
Benjamin Bentmann commented on MOJO-1236:
-----------------------------------------
Instead of unit tests, you could also consider to create integration tests,
i.e. tests that check the actual plugin JAR against a real/full Maven. This
could be done using either the [Maven Invoker
Plugin|http://maven.apache.org/plugins/maven-invoker-plugin/] or the [SHITTY
Maven Plugin|http://mojo.codehaus.org/shitty-maven-plugin/].
> Jupiter Maven Plugin
> --------------------
>
> Key: MOJO-1236
> URL: http://jira.codehaus.org/browse/MOJO-1236
> Project: Mojo
> Issue Type: Wish
> Components: _Plugin Submission
> Environment: Maven2
> Reporter: Rolf Kulemann
> Priority: Minor
> Attachments: jupiter-maven-plugin.zip
>
>
> --- Sorry for not posting to the dev list first, but I could not subscribe to
> the list ---
> Jupiter is an Eclipse plugin for code reviews. I developed a maven 2 plugin
> to generate html reports for the review issues recored with Jupiter. The
> plugin also provides a mojo to setup reviewing in an eclipse project.
> TODOs
> --------------
> * Provide more JUnit tests. Unfortunately, I have some problems using maven
> testing harness
> * Summary section in Jupiter Review Report
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
