Open
Conversation
Owner
|
I would not like to include such launch configurations. they break all the time. |
Author
|
It's your decision to include something or not, as it's your repository :-) As an alternative to commit launch configurations, it is possible to generate them (InstrumentedDemoRunner is the only relevent one) by having a corresponding pom.xml-entry, so everything is in one place, and the launch configuration is generated only when using Eclipse. An other alternative would be to go without the runner classes at all, and instead using JUnit. In this case, the AspectJ-agent can be set through the surefire-plugin. Drawback: The "tests" have to be run via Maven. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Particularly, the InstrumentedDemoRunner should be launchable out of the box.