-
Notifications
You must be signed in to change notification settings - Fork 561
[SUREFIRE-1964] Support for method filtering on excludesFile and includesFile #440
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
Conversation
6f0fe45 to
be7a443
Compare
|
@imonteroperez |
|
The docs and IT does not exist in here. |
slawekjaranowski
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does not impact on any ITs tests?
| + pattern ); | ||
| } | ||
| throw new MojoFailureException( "Method filter prohibited in " | ||
| + "includes|excludes|includesFile|excludesFile parameter: " |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
includesFile|excludesFile should not be supported?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good catch!
The commit 6e06d2a did not employ any ITs in 2015.
|
Great! Do you mind including some new ITs? like the ones provided in: https://github.com/apache/maven-surefire/pull/400/files#diff-03a936fa7cdbcd585a7539659e12039d761e549c55b3f98183b2eea56860990c |
1a3cf0e to
768bb15
Compare
|
Hi @imonteroperez ;-) |
Hi @Tibor17 sorry for the late response, I got infected by COVID last week. I did not perform any update on Javadoc in #400, so feel free to update this yourself. Only commit that you can use is the one about the ITs that I was mentioning in the previous comment. I saw that you updated the Something like: FTR as side note, I early test this approach internally with +30K tests and everything working as expected 🚀 |
|
@imonteroperez |
olamy
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
very nice feature to have.
@Tibor17 definitely ship it!
768bb15 to
505d862
Compare
|
Hi @imonteroperez |
Work in progress in #460 |
|
@slawekjaranowski |
|
does this include the commits from #460? |
Yes, I got confused also, seems all the content from my PR was force-pushed and my mention as a contributor get lost 😞 |
Agree you deserve some credits for the work you did. |
|
@imonteroperez |
yes but the problem is you didn't preserve the author id and so @imonteroperez doesn't get the credit he deserve! |
|
@olamy |
please try to understand, there are potentially 2 problems here:
|
|
@olamy |
|
Sorry for being late in this discussion. Not sure to follow your concerns/ statements @Tibor17
I asked about it on #460 (comment) and the only answer I got was #460 (comment). I assumed based on your latest comment that everything was ok from your side and you will cherry-pick my changes here (in order to prevent who is the author of the changes)
No idea about previous releases or discussions around this topic (or whatever) BUT (1) @olamy is not my speaker (2) I would say exactly the same that he said in terms of respect contributors credit in whatever project. As mentioned in #440 (comment), I'm confused about this situation.
Yes, it seems you took my code from Given said that, please feel free to do whatever you want with this. I will let you decide. |
|
@imonteroperez There was 6 days between two messages #460 (comment) and #460 (comment) and with the like 👍 so it was a signal for me that we can shift the changes to the target module immediately. @imonteroperez |
Now this new feature has been merged, I want to drop here my last comment and thoughts about what happened here:
Given said that, please fix this internal situation as soon as possible. This is a bad symptom for Apache community health and contribution culture. |
|
Resolve #2883 |
Following this checklist to help us incorporate your
contribution quickly and easily:
for the change (usually before you start working on it). Trivial changes like typos do not
require a JIRA issue. Your pull request should address just this issue, without
pulling in other changes.
[SUREFIRE-XXX] - Fixes bug in ApproximateQuantiles,where you replace
SUREFIRE-XXXwith the appropriate JIRA issue. Best practiceis to use the JIRA issue title in the pull request title and in the first line of the
commit message.
mvn clean installto make sure basic checks pass. A more thorough check willbe performed on your pull request automatically.
mvn -Prun-its clean install).If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.
To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.
I hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004
In any other case, please file an Apache Individual Contributor License Agreement.