Skip to content

NPE on gitLoadData #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

Closed
ktoso opened this issue Feb 21, 2011 · 1 comment
Closed

NPE on gitLoadData #1

ktoso opened this issue Feb 21, 2011 · 1 comment
Labels

Comments

@ktoso
Copy link
Collaborator

ktoso commented Feb 21, 2011

NPE loadGitData(GitCommitIdMojo.java:164)

@ktoso
Copy link
Collaborator Author

ktoso commented Feb 21, 2011

reported and fixed by ags :-)

TheSnoozer pushed a commit to TheSnoozer/git-commit-id-maven-plugin that referenced this issue Jun 7, 2016
…tIdMojoDirtyFilesTest has been moved to GitCommitIdMojoIntegrationTest, since the determination of the dirty state should work regardless of native or the jgit implementation. Fix git-commit-id#2: The FileSystemMavenSandbox is intended to just be able to copy the git-Repository itself. As a result having the files besides the repository does no make sense. With that being said the repositories _git_with_no_changes and _git_with_changes needed to be refactored. Since the FileSystemMavenSandbox just copies the git-Repository itself all the repositories are dirty by default as long as they have files tracked. Hence the new _git_with_no_changes currently does no have files in it to be able to represent a repository with no changes. Fix git-commit-id#3 (git-commit-id#236): The ProcessBuilder inside NativeGitProvider always told the user that the 'git status -s' command was not issued correctly and printed the usage manual of the command itself. Since the 'git status -s' command just checks if there was a return value from the command the NativeGitProvider always assumed that the repository was in a dirty state....
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant