[ 
https://issues.apache.org/jira/browse/OFBIZ-11315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17009191#comment-17009191
 ] 

Mathieu Lirzin commented on OFBIZ-11315:
----------------------------------------

As explained by Jacques, the --graph option is very lightweight utility 
exploiting the functionality of the graph traversal code that is already used 
when loading components.

This tool is useful to have in the core because it enables the management of an 
important set of plugins that depend on each others and will likely require 
some analysis/debugging. One motivation was to have a unified view of the 
components like what is provided partially by component-load.xml files. The 
difference is that the graph representation have better semantics because it 
represents faithfully the partially ordered relation of component dependency 
which is missing from component-load.xml.

> Add “--graph” option
> --------------------
>
>                 Key: OFBIZ-11315
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-11315
>             Project: OFBiz
>          Issue Type: New Feature
>          Components: framework
>    Affects Versions: Trunk
>            Reporter: Mathieu Lirzin
>            Assignee: Mathieu Lirzin
>            Priority: Minor
>         Attachments: 0001-Implemented-Add-graph-option.patch, 
> OFBIZ-11315-complete.patch, 
> OFBIZ-11315_standard-no-prefix-format_0001-Implemented-Add-graph-option.patch,
>  ofbiz.dot
>
>
> In order to inspect what components are loaded by OFBiz and their dependency
> relationship, it is convenient to have a visual graph representation.
> {code}
> gradlew "ofbiz --graph"
> {code}
> will output a {{ofbiz.dot}} file that can be processed with Graphviz:
> {code}
> cat ofbiz.dot | dot -T png -o ofbiz.png
> {code}
> Currently there is no dependency relationship specified by components but to 
> check the kind of graph is produced it is possible to revert commit 
> aae1c8a8f5fed7de717290c938297be62c0460fa



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to