-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Caused by: pl.project13.maven.git.GitCommitIdExecutionException: .git directory is not found! Please specify a valid [dotGitDirectory] in your pom.xml #91
Comments
Hi @javaHelper. How do you download the source code? With a git clone or directly the zip archive? I suppose the second one. I've fixed the issue with #92. Could you test it? |
I download the zip file and simply trying to build the code > mvn clean install -DskipTests With the .zip project. How to fix the error ? |
@javaHelper could you please download the new zip then execute a |
Any news? |
No feedback. Please reopen this issue if your problem persists. |
Hi Arey I am experiencing the same issue and I ran mvn clean install |
[INFO] Reactor Summary for Spring Petclinic :: Parent POM 2.1.3: |
Try to fix the Maven issue references in #91
@VictorJabu I don' reproduce this error on my laptop but I've blinded commited this patch : 101ffbd |
Hey Antoine
I downloaded the project instead of cloning it from git. After cloning it
the problem went away
Kind regards
Victor Kabine
…On Thu, May 6, 2021 at 7:16 PM Antoine Rey ***@***.***> wrote:
@VictorJabu <https://github.com/VictorJabu> I don' reproduce this error
on my laptop but I've blinded commited this patch : 101ffbd
<101ffbd>
Could you please retry?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#91 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANZHGOALQR6OW5RA53DALWLTMLFFFANCNFSM4FWVNTOQ>
.
|
Great, thank you for the feedback @VictorJabu |
* Complete Apache 2.0 license * Upgrade to Spring Cloud 2020.0.1 (aka Ilford) and Spring Boot 2.4.2 (spring-petclinic#173) * Added chaos monkey setup (spring-petclinic#177) * Added chaos monkey setup * Update scripts/chaos/call_chaos.sh Co-authored-by: Jonatan Ivanov <[email protected]> * Added docs Co-authored-by: Jonatan Ivanov <[email protected]> * Do not fail packaging if repo info is absent spring-petclinic#91 Try to fix the Maven issue references in spring-petclinic#91 * Bump Spring Cloud version to 2020.0.2 and Spring Boot version to 2.4.5 spring-petclinic#178 * Bump up version to 2.4.5 (spring-petclinic#179) also fixing spring-boot-starter-parent version * Upgrade to Spring Cloud 2020.0.2 and Spring Boot 2.5.1 (spring-petclinic#181) * Migrate from Travis CI to GitHub actions (spring-petclinic#187) * Use Github Actions for CI * Change Travis Badge to Github Actions one * Delete .travis.yml * Added Log Analytics * Added Log Analytics * Added Log Analytics * Added Log Analytics Co-authored-by: Antoine Rey <[email protected]> Co-authored-by: Marcin Grzejszczak <[email protected]> Co-authored-by: Jonatan Ivanov <[email protected]>
* Complete Apache 2.0 license * Upgrade to Spring Cloud 2020.0.1 (aka Ilford) and Spring Boot 2.4.2 (spring-petclinic#173) * Added chaos monkey setup (spring-petclinic#177) * Added chaos monkey setup * Update scripts/chaos/call_chaos.sh Co-authored-by: Jonatan Ivanov <[email protected]> * Added docs Co-authored-by: Jonatan Ivanov <[email protected]> * Do not fail packaging if repo info is absent spring-petclinic#91 Try to fix the Maven issue references in spring-petclinic#91 * Bump Spring Cloud version to 2020.0.2 and Spring Boot version to 2.4.5 spring-petclinic#178 * Bump up version to 2.4.5 (spring-petclinic#179) also fixing spring-boot-starter-parent version * Upgrade to Spring Cloud 2020.0.2 and Spring Boot 2.5.1 (spring-petclinic#181) * Migrate from Travis CI to GitHub actions (spring-petclinic#187) * Use Github Actions for CI * Change Travis Badge to Github Actions one * Delete .travis.yml * Added Log Analytics * Added Log Analytics * Added Log Analytics * Added Log Analytics * updated cli step to create Azure Spring Cloud Co-authored-by: Antoine Rey <[email protected]> Co-authored-by: Marcin Grzejszczak <[email protected]> Co-authored-by: Jonatan Ivanov <[email protected]>
* Complete Apache 2.0 license * Upgrade to Spring Cloud 2020.0.1 (aka Ilford) and Spring Boot 2.4.2 (spring-petclinic#173) * Added chaos monkey setup (spring-petclinic#177) * Added chaos monkey setup * Update scripts/chaos/call_chaos.sh Co-authored-by: Jonatan Ivanov <[email protected]> * Added docs Co-authored-by: Jonatan Ivanov <[email protected]> * Do not fail packaging if repo info is absent spring-petclinic#91 Try to fix the Maven issue references in spring-petclinic#91 * Bump Spring Cloud version to 2020.0.2 and Spring Boot version to 2.4.5 spring-petclinic#178 * Bump up version to 2.4.5 (spring-petclinic#179) also fixing spring-boot-starter-parent version * Upgrade to Spring Cloud 2020.0.2 and Spring Boot 2.5.1 (spring-petclinic#181) * Migrate from Travis CI to GitHub actions (spring-petclinic#187) * Use Github Actions for CI * Change Travis Badge to Github Actions one * Delete .travis.yml * Added Log Analytics * Added Log Analytics * Added Log Analytics * Added Log Analytics * updated cli step to create Azure Spring Cloud * added jq as pre-requisite * updated pre-requisites Co-authored-by: Antoine Rey <[email protected]> Co-authored-by: Marcin Grzejszczak <[email protected]> Co-authored-by: Jonatan Ivanov <[email protected]>
Try to fix the Maven issue references in spring-petclinic#91
I am getting below error. No code changes done. No customization
The text was updated successfully, but these errors were encountered: