-
Notifications
You must be signed in to change notification settings - Fork 59
[MWRAPPER-158] Remove incorrect license header #166
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
[MWRAPPER-158] Remove incorrect license header #166
Conversation
The "This code is licensed to ASF" license header on the generated ./mvn/wrapper/maven-wrapper.properties file does not make sense. The file is the user's, not ASF's. It is generated as a convenience for the user. The file is logically part of the user's own code. We don't know what license that has, so adding a license header is bound to be wrong.
b1792c1
to
fda8ab1
Compare
CI pipeline currently blocked by MWRAPPER-159 |
I don't understand why the test failed. I've never seen this check before:
|
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.
Is that true? .mvn/wrapper/maven-wrapper.properties would ont normally be part fo the user's project. It's maven configuration and would not be checked into the source repo. Or is that not the code being generated here? Which file does this code generate?
Resolve #323 |
1 similar comment
Resolve #323 |
It's not true. A lot of projects do add the wrapper configuration in the source tree. |
I think rebasing on current master should work. Can you do that @lbruun ? |
Done! |
@gnodet Please assign appropriate label to PR according to the type of change. |
The "This code is licensed to ASF" license header on the generated
./mvn/wrapper/maven-wrapper.properties
file does not make sense. The file is the user's, not ASF's. It is generated as a convenience for the user.The file is logically part of the user's own code. We don't know what license that has so adding a license header is bound to be wrong. Therefore removed completely.
I'm guessing the code comes from a time when the Plugin was only (meant to be) used internally in the Apache Maven
project. Then it would make sense.
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.
[MWRAPPER-XXX] - Fixes bug in ApproximateQuantiles
,where you replace
MWRAPPER-XXX
with 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 verify
to make sure basic checks pass. A more thorough check willbe performed on your pull request automatically.
mvn -Prun-its clean verify
).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.