Error when using a worktree of a bare repository

[LucasKuhlemann]

Using this plugin with a git worktree, where the original repo is bare, results in an error:

[...]
Caused by: org.eclipse.jgit.errors.NoWorkTreeException: Bare Repository has neither a working tree, nor an index
    at org.eclipse.jgit.lib.Repository.getWorkTree (Repository.java:1582)
    at me.qoomon.gitversioning.commons.GitUtil.worktreesFix_getCommonRepository (GitUtil.java:147)
[...]

Whatever the issue is, it's fixed by upgrading to the latest version of jgit (currently 7.5.0.202512021534-r).

I created a pull request for this, could you please take a look @qoomon?

[matjazs]

Additional reproduction case: packed-refs breaks worktree builds

We hit a related failure on v9.11.0 when git gc packs the branch ref:

Steps to reproduce:

1. Create a worktree: git worktree add ../my-worktree my-branch
2. Run git gc (or let auto-gc run) - this packs refs/heads/my-branch into packed-refs and removes the loose file
3. Run mvn clean in the worktree

Error:

[FATAL] Non-readable POM /path/pom.xml: /path/.git/worktrees/my-worktree/../../refs/heads/my-branch

Root cause: GitUtil.worktreesFix_resolveHead() reads the loose ref file directly (new File(commonGitDir, refPath)) but doesn't fall back to packed-refs when the file doesn't exist.

Git itself works fine - git rev-parse HEAD reads packed-refs. The issue is the manual workaround bypassing JGit.

Workaround: Recreate the loose ref file manually:

git rev-parse HEAD > /path/to/.git/refs/heads/my-branch

The JGit 7.5.0 bump in #407 would likely fix this if JGit 7.x properly resolves worktree refs through packed-refs (not verified on our end).