SLF4J / SLF4J-437 [Resolved] Create a BOM POM ==============================
Here's what changed in this issue in the last few minutes. There is 1 comment. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-437 ============================== 1 comment ------------------------------ Garret Wilson on 23/Aug/23 16:30 Good morning, [~ceki]. I have good news and not-so-good news. It turns out that [m2e-core Issue #1501|https://github.com/eclipse-m2e/m2e-core/issues/1501], in which Eclipse Maven support wasn't correctly resolving dependencies, turned out to be a bug they introduced into the latest development version. It had nothing to do with the BOM POM structure. It only seemed related because that's what I had been changing when I discovered the new dependency calculation bug. (For what it's worth, they just committed a fix for that bug.) The not-so-good is that the [Nexus Staging Maven Plugin|https://github.com/sonatype/nexus-maven-plugins/blob/main/staging/maven-plugin/README.md] seems to have a bug that makes it not deploy the top-level POM if another POM is at the same directory level. Thus the structure we were using with the {{parent-pom.xml}} file in the root of the project alongside {{pom.xml}} will cause {{pom.xml}} not to be deployed!!! I filed bug [{{MVNCENTRAL-8292}}|https://issues.sonatype.org/browse/MVNCENTRAL-8292], but I may have to file another ticket for the Nexus Staging Maven Plugin. I don't know the likelihood of it being fixed though; we'll have to see. In the meantime, we'll have to move {{parent-pom.xml}} back into {{parent/pom.xml}}. Don't forget 1) to update the aggregation to say {{<module>parent</module>}}, 2) to remove the {{<relativePath>pom.xml</relativePath>}} inside {{parent/pom.xml}}, and 3) to change the other POMs from {{<relativePath>../parent-pom.xml</relativePath>}} to {{<relativePath>../parent/pom.xml</relativePath>}}. In other words, we'll have to follow the second-to-last structure in my BOM article. I only just now updated [{{MVNCENTRAL-8292}}|https://issues.sonatype.org/browse/MVNCENTRAL-8292] with this latest discovery, so it's possible they could quickly fix this in the Nexus Staging Maven Plugin. In the meantime I'm going to redeploy my {{globalmentor-base}} and {{globalmentor-web}} projects as described in this comment so they wont' be broken. ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af) _______________________________________________ slf4j-dev mailing list [email protected] https://mailman.qos.ch/cgi-bin/mailman/listinfo/slf4j-dev
