circular dependency between jcabi-log and jcabi-aspects

[reegnz]

jcabi-log depends on jcabi-aspects and vice-versa.

This circular dependency can be resolved by splitting jcabi-log into jcabi-log-api and jcabi-log-impl. The dependency to jcabi-aspects is only required bz jcabi-log-impl, and jcabi-aspects can only depend on jcabi-log-api.

[yegor256]

@reegnz Yes, they depend on each other, but in fixed versions. How does it affect you? What problem do you experience? Can you post your pom.xml?

[reegnz]

It doesn't affect anyone probably, since it is a project-architectural issue, not a bug.
Just trying to make constructive criticism of this promising little project. 👍

Anyways it still feels weird to see this. If it depends on a fixed version, how come it is not the latest version?

[yegor256]

That's a valid question. The thing is that jcabi-aspects needs just basic functionality from jcabi-log, which existed since version 0.7 (or even earlier). That's why it's enough for jcabi-aspects to be dependent on jcab-log:0.7.

[yegor256]

see jcabi/jcabi-aspects@58d2c80

[yegor256]

@reegnz is it still an open bug? please close the issue if the problem is solved. thanks

[ittaiz]

We hit this issue when trying to migrate a project from maven to bazel.
Bazel doesn't have version resolution mechanisms like maven and so we aligned on one version and got cyclic problems.
These can be worked around via depending on the "old" jcabi-log under a different name but it's brittle so we just stopped depending on jcabi all together.
Just another data point.

[flowgrad]

Got this when trying to use it in OSGi environment. Dropped this project faster then anything. Circular dependecies are a hint on low quality and lack of vision. Fix it.