Environment

IntelliJ version: 2023.2
jMolecules: 0.8.1
jvm memory options: -Xmx6144m
Os Arch: ARM64
Shared build process heap size (Mbytes): 2048

Problem Description

When browsing a package within the IDE it fails with a StackOverflow error (Stacktraces below). Below are some details about the package.

1. Source files: Java
2. Number of files: 5
3. Package Info: 1
4. Java classes: 4
5. SLOC: ~175

StacTrace added as comment (Hitting issue character limit)

Would be cool if the Spring native annotations were supported out of the box. There will be a jMolecules build plugin to translate jMolecules annotations into Spring ones relatively soon but as long as that's not available, users are forced to use Spring's native annotations as well. To benefit of the project view decoration they would have to use both sets of annotations on their types.

Also, recognizing Spring Data repositories (extending org.springframework.data.repository.Repository or annotated with org.springframework.data.repository.RepositoryDefinition would be cool as well.

It would be cool if the stereotype annotations would also be detected in the type hierarchy, i.e. if a type implements or extends another type annotated (or recursively above) it should extract the stereotype as well.

It look like it not support Kotlin projects ?

To configure which decorations to activate. This might be helpful.

To help to understand that jMolecules is not package :)

Is it possible to introduce a grouping layer between a package and the types contained in them?

Now:

com.acme.mypackage
+ MyAggregateRoot <<AggregateRoot>>
+ MyServiceClass <<Service>>
+ MyOtherServiceClass <<Service>>

Alternative:

com.acme.mypackage
+ Services
  + MyServiceClass
  + MyOtherServiceClass
+ AggregateRoots
  + MyAggregateRoot

It would be cool if type based building block declarations would be picked up as well. E.g. a type implements org.jmolecules.ddd.types.AggregateRoot (also by indirection) should also be detected as aggregate root.