@@ -1674,20 +1674,23 @@ in your endeavor to write idiomatic Clojure code.
16741674
16751675## Library Organization
16761676
1677- * If you are publishing libraries to be used by others, make sure to
1677+ * <a name=" lib-coordinates" ></a>
1678+ If you are publishing libraries to be used by others, make sure to
16781679 follow the [Central Repository
16791680 guidelines](http://central.sonatype.org/pages/choosing-your-coordinates.html)
16801681 for choosing your `groupId` and `artifactId`. This helps to prevent
16811682 name conflicts and facilitates the widest possible use. A good
16821683 example is [Component](https://github.com/stuartsierra/component).
16831684 <sup>[[link](#lib-coordinates)]</sup>
16841685
1685- * Avoid unnecessary dependencies. For example, a three-line utility
1686+ * <a name=" lib-min-dependencies" ></a>
1687+ Avoid unnecessary dependencies. For example, a three-line utility
16861688 function copied into a project is usually better than a dependency
16871689 that drags in hundreds of vars you do not plan to use.
16881690 <sup>[[link](#lib-min-dependencies)]</sup>
16891691
1690- * Deliver core functionality and integration points in separate
1692+ * <a name=" lib-core-separate-from-tools" ></a>
1693+ Deliver core functionality and integration points in separate
16911694 artifacts. That way, consumers can consume your library without
16921695 being constrained by your unrelated tooling prefences. For example,
16931696 [Component](https://github.com/stuartsierra/component) provides
0 commit comments