Introduce a demo-profile inside the pom, see #181 #184
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Collaborator
Author
|
Hi @ktoso, |
TheSnoozer
pushed a commit
that referenced
this pull request
Apr 12, 2015
Introduce a demo-profile inside the pom, see #181
Collaborator
|
Great idea and good to merge commits whenever you feel a PR is good to go :-) |
Collaborator
|
Let's keep doing things as PRs so we have a chance to discuss of something more up-for-debate :-) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As suggested in #181, I would like to introduce a demo-Profile where anybody can just run the plugin right away.
This would speed up to live test wheather something is broken under some conditions or not. I used this in one of my own plugins to discover some nasty bugs.
However, this will not avoid writing Testcases. This should only help to track down a problem and then writing test cases for it.
For my own plugin I once had included it in the regular-build (so run everytime for everytime), However when i screwed up, I had no chance to re run
mvn clean installwithout removing the config of the plugin. Therefore I needed to moved it to a different profile where I could choose if I would like to run it or not.