# Logging module name clash in Vapor 3

**URL:** <https://forums.swift.org/t/logging-module-name-clash-in-vapor-3/25466>\
**Category:** Vapor\
**Created:** [June 8, 2019, 6:35pm UTC](https://forums.swift.org/t/logging-module-name-clash-in-vapor-3/25466 "2019-06-08T18:35:18Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![IanPartridge](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/ianpartridge/32/434_2.png) [@IanPartridge](https://forums.swift.org/u/IanPartridge)\
**Post date:** [June 10, 2019, 9:04am UTC](https://forums.swift.org/t/logging-module-name-clash-in-vapor-3/25466/8 "2019-06-10T09:04:27Z")

</div>

👋 [GitHub - Kitura/LoggerAPI: Logger protocol](https://github.com/IBM-Swift/LoggerAPI) maintainer here...

I'm very sorry that this breakage has occurred. It did not occur to us that adding a dependency in SemVer minor could break people like this.

I can't see anything we could have done differently, beyond doing this in a SemVer major release which is not really practical for us...

We would be very happy if we could namespace our stuff as `io.kitura.*` but that's not an option...

---

_[View the full topic](https://forums.swift.org/t/logging-module-name-clash-in-vapor-3/25466)._
