Skip to content
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

Track the year of a file creation through license-maven-plugin-git #145

Merged

Conversation

sic2
Copy link

@sic2 sic2 commented Feb 1, 2019

Reason behind this PR:
Sometimes you are required to include in your license header only the
date of the file creation.
These changes allow us to look at the git history and find the year of
reation for a given file.

Note:
Sometimes git is unable to figure out the date of creation of a file if
this has moved/renamed without git being able to detect such change.
A potential future solution could be to avoid dates to be overwritten.
I would leave that for another PR though.

Additionally, this PR reduces a bit of duplicated code in the git plugin.

Reason behind this PR:
Sometimes you are required to include in your license header only the
date of the file creation.
These changes allow us to look at the git history and find the year of
reation for a given file.

Note:
Sometimes git is unable to figure out the date of creation of a file if
this has moved/renamed without git being able to detect such change.
A potential future solution could be to avoid dates to be overwritten.
I would leave that for another PR though.

Additionally, this PR reduces a bit of duplicated code in the git plugin.
@ghost ghost assigned sic2 Feb 1, 2019
@ghost ghost added the under-review label Feb 1, 2019
@sic2
Copy link
Author

sic2 commented Feb 1, 2019

@mathieucarbou I opened a new PR since I had setup that wrong being it in the master branch of my fork.

@sic2 sic2 mentioned this pull request Feb 1, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants