jqassistant-archive/jqassistant-plantuml-rule-plugin

@jQAssistant plugin for interpreting PlantUML diagrams as executable rules.

jqassistant-plantuml-rule-plugin's Issues

Allow creation of nodes using UML diagram

Currently it is not possible to create nodes using the PlantUML jQA plugin. If specific nodes are required, e.g. for defining an architecture metamodel, one has to create the nodes using a cypher query (and can visualize this afterward using the plugin).

It'd be beneficial to have both (creation and visualization) in one step, i.e. in a PlantUML diagram.

Proposal:

component "+{name:'Application'}" AS application <<Layer>>
component "+{name:'Domain'}" AS domain  <<Layer>>
application -> domain : +:DefinesDependency

This would create two nodes each with the specified name, the specified labels, and a relationship between those two.

What am I missing?

(Please tag as question instead of bug)

I wanted to try out JQAssistant + PlantUML. So I started a project with Spring Initializr, and I added JQAssistant and your plugin.

Maybe I am missing something here, but where should the input files be located? And where will the output files be placed?

Here is a link to my project https://github.com/gabrieloshiro/jqassistant-pov

Thanks

Allow nodes without stereotypes

Hi guys,

before I state my issue I like to thank you for JQA and this nice plugin as well. I really like it!

Sometimes when I'm writing a PlantUml I forget to add a stereotype for every node. This leads
currently to a Nullpointer during the Maven build. The same happens if a relation does not have a label.

I would prefer to allow nodes without a stereotype so that these nodes are ignored during the Cypher rendering. For example this would allow me to use a node to abstract a detail not relevant to the Cypher but useful for understanding the diagram.

Please see my Nullpointer fix in the Pull-Request. The fix also logs the ignored nodes and relation as info instead of a warning in oder to allow my preference from before.