Gunnar Morling

The idea being to make it easy to identify "god components" as they have a more intense color. It could be an indication to split them up.

Provide more abstract concept than the package level for describing the target architecture

2

Currently the target architecture to validate a code base against is described in terms of allowed package references. This does the job, but it is desirable to have the possibility...

Implement all checks for kinds of type references

10

Currently still missing are references in: - [x] method return values - [x] (nested) type arguments - [x] constructor calls - [x] super-class and implemented interfaces - [x] annotations -...

By design Deptective works at compile time of individual modules and the defining use case has been to ensure the architecture _within_ single modules. But it's desirable to also enforce...

Add package cycle check

3

While Deptective already implicitly addresses the detection of package cycles by validating a code base against a target architecture (provided that architecture is defined in a cycle-free way), there's demand...

Add check to prevent exposing internal types in public API

2

When declaring the public API of a Java module in _module-info.java_, the Java compiler doesn't prevent exposure of any non-public types in the API signatures. That situation should be detected...

Enable usage of modules from runtime image in layers

18

Hey @aalmiray, this just [came up](https://www.reddit.com/r/java/comments/j9dxcg/modular_tiles_a_sample_dynamic_modular_javafx/) on Reddit: Can we load modules from a modular runtime image (jlink) into a layered Layrry app? I think this will require some work,...

The idea would be to keep a `WeakReference` for the class loader of each plug-in. If a plug-in gets removed, and this weak reference does not get enqeued after some...