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
Use JGit/EGit or the gradle-git plugin instead of native Git #27
Comments
|
Hi Michael, I'll have a look at https://github.com/ajoberstar/grgit. Best regards, |
|
Hi Damien, thanks for your response. Does that mean you will switch to grgit? Would be great! In the meantime I will use it directly. Regards, |
|
Hi Michael, I'll probably use either grgit or jgit (done that in my other projects - but I'm using Best regards, |
|
Thanks! |
|
As I feared, the I have to find another way to get this information. |
|
In the end, I'm using the long version ( |
…lt to extract exact tag - more details in case of error
…not take into account - removed an obsolete test
|
Available in version 1.7.0 - published in Bintray, can take some time (< one hour) before it's available. Note that I keep using the |
|
What a pity! Please make this optional, like in Maven's git-commit-id plugin. Why would I want to use JGit when native git is available and MUCH faster? |
Not every developer has a native git executable in the path. If that's the case, the build.gradle file will fail with an exception. Telling developers/users to install yet another tool does not simplify the build process ;) IDEs such as Netbeans and Eclipse use a Java based Git infrastructure which works nicely in many cases. Another problem with native Git might be compatibility. Although the git repository-format is pretty stable, the native CLI might be incompatible with this plugin. IT is complicated to force a specific, well-tested git-version Therefore, I'm suggesting a switch from native Git to JGit/EGit or the gradle-git plugin.
The text was updated successfully, but these errors were encountered: