What are the plans regarding the future of the analysis library?

[chriskn]

Question

Hi, I recognized with version 1.21.0 of structurizr-core the code elements were removed from components. Besides this, further compatibility issues exist with the latest versions of structurizr-core and structurizer-analysis.

What are the plans regarding the future of the analysis library? Will it be maintained in future?

Kind regards

[simonbrowndotje]

I may resurrect it in the future, but I have plenty of other code to maintain and there's been almost no demand for this library for a couple of years now.

[Riduidel]

Seems like there are some uses ;-) (https://mvnrepository.com/artifact/com.structurizr/structurizr-spring/usages)

[simonbrowndotje]

I don't know how accurate the Usages count is, but it's 0 for everything except the "CIA" project (which is 1) and that itself doesn't seem to have component diagrams -> https://hack23.github.io/cia/architecture.html

I still like the concept of generating component diagrams from code but, in my experience anyway, there's very little real-world interest at this time.

[chriskn]

I may resurrect it in the future, but I have plenty of other code to maintain and there's been almost no demand for this library for a couple of years now.

That's understandable but removing the code elements from the model looks, at least for me, like there is no further interest in supporting model generation from code with structurizr at all.

Is that the case? If not, could you please elaborate on the reasons? If help is welcome, I would try to make this lib compatible again with the latest version of the model.

[simonbrowndotje]

I have no plans at this time (and will likely archive the repo later this year), but yourself and @Riduidel (see structurizr/java#204) are more than welcome to fork the repo to make it compatible.

[chriskn]

Thank you for the explanation. My question is answered.

[simonbrowndotje]

removing the code elements from the model

None of the core Structurizr tooling used the CodeElement class, and the presence of it caused people to raise questions about why all sorts of other level 4 concepts (non-OO languages, data models, etc) were not supported natively by the tooling. As I said in structurizr/java#204 (reply in thread) ... there are ways to achieve the same result without CodeElement being in the core library.