You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Also note that using maven macro functions <groupId>${project.groupId}</groupId> and <version>${project.version}</version> in your bom will not always populate these fields with the values of your bom but with values of the importing project. It's a known issue and folks typically generate their bom without maven macro functions.
The text was updated successfully, but these errors were encountered:
Thank you @bertramn for this finding. Blame on me, I forgot to change the name in the bom after renaming the artifacts.
The fix is pretty trivial. What I am however curios about is your note about maven properties I used for groupdId and version in the bom. To be honest, I've never encountered the issue you're talking about. I also failed to find something related to it via google. Do you know some resources, I can take a closer look at to get more insights into it?
The groupId is simple, but version could introduce headaches - I would like the version for each referenced module in the bom to be updated automatically during the release. But maven-release-plugin does not support this is far as I remember. How would you address this?
Looks like the bom descriptor includes invalid dependencies. Lines pom.xml#L19 and pom.xml#L24 should not be
jpa-unit-junitX
but justjpa-unitX
.No artifact found for jpa-unit-junit4 but I can spot jpa-unit4.
Also note that using maven macro functions
<groupId>${project.groupId}</groupId>
and<version>${project.version}</version>
in your bom will not always populate these fields with the values of your bom but with values of the importing project. It's a known issue and folks typically generate their bom without maven macro functions.The text was updated successfully, but these errors were encountered: