[logback-dev] [JIRA] Updates for LOGBACK-1631: logback-classic-db contains unexpected values in pom (artifactId + version dependency)

QOS.CH (JIRA) noreply-jira at qos.ch
Wed Apr 20 11:47:00 CEST 2022


logback / LOGBACK-1631 [Open]
logback-classic-db contains unexpected values in pom (artifactId + version dependency)

==============================

Here's what changed in this issue in the last few minutes.
This issue has been created
This issue is now assigned to you.

View or comment on issue using this link
https://jira.qos.ch/browse/LOGBACK-1631

==============================
 Issue created
------------------------------

Juan Pablo Santos Rodríguez created this issue on 20/Apr/22 11:33 AM
Summary:              logback-classic-db contains unexpected values in pom (artifactId + version dependency)
Issue Type:           Bug
Affects Versions:     1.2.11
Assignee:             Logback dev list
Components:           logback-classic
Created:              20/Apr/22 11:33 AM
Priority:             Major
Reporter:             Juan Pablo Santos Rodríguez
Description:
  logback-classic-db artifactId is mispelled {{logback-clasisc-db}} so its deployed under unexpected coordinates at central, see: [https://search.maven.org/artifact/ch.qos.logback.db/logback-clasisc-db/1.2.11/jar]. The fix is really straightforward, but can provide a PR if its useful.
  
  Also, the ch.qos.logback:logback-core:test-jar dependency seems to be downloading the 1.2.10 version instead of the 1.2.11 one, which is somewhat unexpected too (the logback-db artifacts were released the same day as 1.2.11). This seems to be due to {{logback-parent-db:1.2.11}} setting {{logback.version}} to 1.2.10. Again, not that this is wrong, but unexpected.
   
  
  


==============================
 This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)



More information about the logback-dev mailing list