[BUG] poms of two modules show up as untracked after build and are not updated on release

[line-o]

Describe the bug

When building exist I have two changed pom.xml files in my working directory.

• exist-core-jcstress/dependency-reduced-pom.xml
• exist-core-jmh/dependency-reduced-pom.xml

Expected behavior

Building exist from source does not add untracked files to the working directory. They should either be ignored or stay unchanged.

To Reproduce

1. checkout develop
2. run mvn clean package
3. run git status
4. the two poms mentioned above are shown as untracked files

Screenshots

When checking out the current master branch and building it both subprojects still show up as 6.1.0-SNAPSHOT (see screenshot below):

Context (please always complete the following information):

• Build: eXist-6.1.0-SNAPSHOT (b8e7349)
• Java: 1.8.0_352 (Azul Systems, Inc.)
• OS: Mac OS X 12.6.2 (aarch64)

Additional context

• How is eXist-db installed? built from source (develop, master)
• Any custom changes in e.g. conf.xml? none

[line-o]

This seems to even cause the test workflow in CI to fail see https://github.com/eXist-db/exist/actions/runs/3940322485/jobs/6741277473#step:4:21

[joewiz]

It appears that the 6.1.0 release didn't touch the poms of exist-core-jcstress or exist-core-jmh.

Compare the files listing of the 6.0.0 and 6.1.0 releases.

[joewiz]

My results when running mvn package on develop HEAD:

[joewiz]

... and I don't get any untracked pom files. But I definitely see the mismatch between 6.2.0-SNAPSHOT for most of the build targets except for exist-core-jcstress and exist-core-jmh.

[line-o]

@joewiz try mvn clean package

[joewiz]

@line-o Running mvn clean package, I do get the 2 untracked dependency-reduced-pom.xml files in exist-core-jcstress and exist-core-jmh that you described. Does the issue description need to be updated to say mvn clean package instead of mvn package?

[line-o]

Well, on a clean checkout you would see it without clean I suppose

[joewiz]

Fair point! Then I suppose the more precise advice than "checkout develop" would be "Clone the repository and checkout develop; or, for an existing clone, run mvn clean"?

[joewiz]

... I'm not being nitpicky. I'm just trying to ensure others trying to reproduce are able to follow the instructions clearly so they can effectively investigate.

[line-o]

I changed it