-
Notifications
You must be signed in to change notification settings - Fork 13
Add license header template for com.mycila:license-maven-plugin #1
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
6ee28b1
to
a6212ca
Compare
This PR introduces a license header template for com.mycila:license-maven-plugin. Please refer to this branch to see how the template is supposed to be consumed by projects: https://github.com/ppalaga/rhq-metrics/tree/150116-license There are two use cases: |
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.
Minor comment
AFAIC, I don't see the value in extracting all versions to properties (I do see value when the version number is used twice or more)
Is this a rule for POM writing we're supposed to obey or only your own practice?
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.
Because that's how it is done - not only usually but also in the Hawkular family. It is practical to do things in uniform ways so that one can find them quickly in a well defined location. Moreover, doing it the same way in the whole family of hawkular projects will make it easier to keep the same versions on multiple place. As far as I can see now, it will be inevitable to copy e.g. com.puppycrawl.tools.checkstyle
version between here and the hawkular
ur-parent.
You are right that there is no re-use in this particular place but for the named reasons, I'd keep it like this.
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.
Because that's how it is done - not only usually but also in the Hawkular family
If it's been agreed then ok.
I did not really take the time to look at the details of the JGit code, I trust you for the how and your JUnit tests for the correctness. I have one question on the Also, it means that it's no longer possible to download the sources without Git and build the project: a Git repository becomes mandatory. |
I have no exact numbers. The subjective feeling is that I have not noticed any substantial delay. Should I try to get some exact numbers through running with and without license checks?
This is probably a valid point. But there is an easy work around: one can run with |
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.
What for ist that? As we allow Java 8 for Hawkular in general, do we need to restrict to 6 here?
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.
That's just for having it easier to contribute some parts of the code to upstream. Is that an acceptable reason?
It's not necessary, we can revisit that later if needed
That's ok for me. Any objection @pilhuhn ? Other than that, +1 on merging |
+1 from @pilhuhn on IRC |
Add license header template for com.mycila:license-maven-plugin
No description provided.