# Managing Cross-Dependencies Between cn1libs

DevFeed: [Managing Cross-Dependencies Between cn1libs](<https://devfeed.tech/articles/tip-nest-cn1libs-cross-dependencies-19589.md>)

Original publisher: [Read original article](<https://www.codenameone.com/blog/tip-nest-cn1libs-cross-dependencies/>)

Author: Shai Almog

Published: 2017-01-08T00:00:00Z

Content type: tutorial

Language: en

Sources: [CodeName One](<https://devfeed.tech/sources/codename-one.md>)

Topics: [Dependency management](<https://devfeed.tech/topics/dependency-management.md>), [Zip](<https://devfeed.tech/topics/zip.md>)

Tags: [dependencies](<https://devfeed.tech/tags/dependencies.md>), [dependency-management](<https://devfeed.tech/tags/dependency-management.md>), [developers](<https://devfeed.tech/tags/developers.md>), [zip](<https://devfeed.tech/tags/zip.md>)

## AI overview

This tutorial explains how to add one cn1lib as a dependency of another by unpacking the dependent library and updating the compile path and IDE classpath. It also notes that both libraries must be installed in the project and mentions the library extension tool's dependency declarations.

## Source excerpt

On occasion developers ask us for cn1lib dependencies, e.g. allowing one cn1lib to use functionality in another cn1lib. This isn't something we rolled into the cn1lib infrastructure because we strongly believe in simplicity. Dependency management solutions become fragile once nesting sets in and often mask over-engineering which is really dangerous for a tool that depends on small footprint. A cn1lib is really just an ant project that packages the results into a zip containing nested zips with the data relevant to all the platforms. To add another cn1lib lib to the classpath first you need to unzip that cn1lib.