execution stuck #95
Comments
|
Can you repeat this in an open repository? Something that I can access. |
|
I tried it in https://github.com/apache/maven/ and it works fine. The commit history is clean and short. The repository I work on is a different story. The history is labyrinthine and with hundreds of merge commits. There over 500 separate projects in this multi-module build, and I need the plugin to run for each, getting the last 100/1000 commits that touched anything in the directory. You can tell me if this is possible, but if the plugin is going to trawl through every commit in the history I doubt it. |
|
It seems like a get-the-dom approach, rather than a pull-as-needed approach. If my template doesn't ask for anything, why query the repo at all? To replicate It should get stuck. BTW, why do I need to have a master branch? |
|
I'll have a look when I find the time.
https://github.com/tomasbjerre/git-changelog-command-line |
ReproduceIf it's of any help: It seems that I have the same issue. It should theoretically be reproducible:
This leads to WorkaroundStarting it with Here is the output of this for comparison. There is much more going on within the configuration: |
tomasbjerre
added a commit
that referenced
this issue
Mar 12, 2023
|
Thanks @JohT ! This algorithm is a mess... but I think I fixed it. I was able to generate your changelog with: npx git-changelog-command-line -t showcase-quarkus-eventsourcing/changelogTemplate.mustache -ut "Next Release" -of showcase-quarkus-eventsourcing/CHANGELOG.md |
|
@tomasbjerre thank you so much for your time. How can I "translate" the node command to maven? I was able to generate the changelog with If this is currently the way to do it, then I'll be fine with it. |
|
I guess Maven does not pick up same configuration with those two commands, I don't know. I found the issue while debugging a test case in this library where I point at your repository. |
|
@tomasbjerre, the problem is solved at least on my side as far as I can see for now with Update dependency se.bjurr.gitchangelog:git-changelog-maven-plugin to v1.96.1. 🎉 Thank you very much. Well done.👏 |
|
@JohT use pluginManagement to configure the plugin without necessarily executing it (no need to skip) @tomasbjerre I don't know what's changed, but the behaviour since 1.64 is still the same: out of lifecycle execution completes, while binding the execution to a phase in the default lifecycle gets stuck. If changelog:changelog is going to be the only way, then the docs at git-changelog-maven-plugin need attention. Someone new is not going to find this ticket. You might have luck bringing this issue up at dev@maven.apache.org |
|
@JohT I failed to build your showcase-quarkus-eventsourcing repo. Do you still need to run changelog:changelog outside the default lifecycle? |
|
@delanym i probably should have mentioned that you need to change into the project directory showcase... if you are in Repository root. Also I need to mention that my master branch works now with the new version. So you might change the version number of the changelog plugin as well if you did the clone recently. |
|
@JohT the jasmine-maven-plugin is failing with which looks like a platform issue. But then I noticed your Maven Wrapper was only added with a Windows startup script. I'm building on Linux. @tomasbjerre JohT's repo is my best hope at the moment for a reproducer |
|
@delanym, my pipeline (GitHub Actions) runs on Ubuntu (22.04.2) with Open Adapt Java 17 https://github.com/adoptium/temurin17-binaries/releases/download/jdk-17.0.6%2B10/OpenJDK17U-jdk_x64_linux_hotspot_17.0.6_10.tar.gz. It also works on Linux. I don't know how the container is configured in detail though. Here is my GitHub Actions Configuration: |
|
Perhaps you can add a Maven Wrapper with intended version. I did I tested with: And I am getting: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi. I tried this basic config on my project.
When I run
mvn clean install -e -Xthe output goes on ad infinitum.The text was updated successfully, but these errors were encountered: