The plantuml library implements a DSL and renderer for many UML diagrams (class, sequence, objects, states, activities, ...). See http://plantuml.com for more info about the DSL and renderer.
This project integrates plantuml's functionality into Eclipse, by means of a view that shows a diagram for the currently active editor. The rendered diagram is typically based on explicit DSL code embedded in the editor, or generated from the content of the editor.
We currently support generating diagrams for
- DSL code embedded in text in any text editor inheriting from the standard eclipse text editor
- the class in the Java editor, based on the Eclipse Java model
- the EClasses in Ecore models in the Ecore editor
- OSGi Manifest files
There's also support for generating a diagram for all the Java classes within one or more Java packages.
Diagram generation is handled by (implementations of) an extension point, called diagram intent providers (supersedes diagram text providers), so you can customize the process of generating a diagram for other file types or editor content. Each diagram intent provider supports a certain way of generating a diagram from a source, typically the content of an editor. There may be several diagram intent providers for a certain source, so the user may select the desired one.
Each diagram intent provider may support properties that affect details of how diagrams are generated, that may be changed pr. workspace by adding properties in a specific properties file in a specific folder. The folder is settable in the PlantUML property sheet. E.g. the diagram intent provider for class diagrams supports two properties, that controls how attributes' name and type are rendered. Certain other behavior is also controlled by properties in properties files, details can be found in Customization.
This repo uses the EPL license.
We use Issues for issue tracking, so head there concerning bugs or suggest features (check if they already exist before adding).
However, we have now (September 2021) started using Discussions, so please consider it, before use Issues, as the dialog may resolve the issue before it is even raised! Of course, you can also ask questions about how to use PlantUML, tell us about how you use it, comment on where the plug-in should be heading, etc.
We use github pages @ https://hallvard.github.io/plantuml/ as the update site URL, in the Help > Install New Software... dialog.
You'll find some developer documentation here:
- net.sourceforge.plantuml.composite/README.md (how to build, run, and release)
- net.sourceforge.plantuml.lib/README.md (how to update PlantUML library)
- lib - plantuml.jar packaged as a bundle
- lib.jlatexmath - fragment to the lib bundle that adds the jlatexmath lib
- lib.elk - fragment to the lib bundle that adds the ELK layout engine lib
- eclipse - core Eclipse integration, including the extension point for providing diagrams
- eclipse.imagecontrol - the control for viewing the generated images
- svg - the browser-based svg view
- text - diagrams based on explicit DSL code, with support for editors based on the standard Eclipse text editor
- jdt - diagrams based on the Eclipse Java model, with support for Java and Class File editors
- ecore - diagrams based on Ecore models, with support for most Ecore editors
- osgi - component diagrams based on OSGi meta-data
- (xcore - diagrams based on Xcore models, with support for the Xtext editor)
- (uml2 - diagrams based on UML2 models, obsolete)
Notable features in recent releases, details are found in releases. Note that the version numbers of the plantuml.lib plugin are a bit special, since they use the version of the included plantuml.jar
- Updated PlantUML library version to 1.2024.5, see changes.
- Updated PlantUML library version to 1.2024.4 (issue #145), see changes.
- Automated some of the steps needed to update to a new PlantUML library version (issue #145)
- Updated target platform to Eclipse 2023-12 and to Java 17.
- Fixed access to environment variables from PlantUML code, using PlantUML functions like %getenv("MY_ENV_VAR"), see PlantUML security profiles.
- Fixed installation on Windows without having to explicitly install Graphviz (issue #175)
- Updated PlantUML library version to 1.2023.11 (issue #145), see changes.
- Updated PlantUML library version to 1.2023.10 (issue #145), see changes.
- Fixed duplicated Java type members entries in diagrams created from Java packages.
- Updated to use PlantUML library version 1.2023.5 (issue #145), see changes.
- Updated target platform to Eclipse 2022-09 and JRE 11 (JavaSE-11).
- Support for injecting code into diagrams, based on regular expressions on the diagram text, e.g. custom styles can be inserted all state diagrams. See section about custom properties.
- Updated to use PlantUML library version 1.2022.7 (issue #145), see changes.
- Fix for issue #152 to more gracefully handle "empty" line.
- Fix for issue #144 concerning installation in Eclipse 2021-09.
- Fix for issue #140 where methods for selecting relevant diagrams weren't called.
- Fix for issue #139 preventing diagram from appearing.
- The svg view can use a jmustache template (according to a preference) when generating its contents issue #116
- Updated to use PlantUML library version 1.2021.5 see changes.
- Support for the ELK layout engine, see plantuml.com/changes.
- Fix for issue #132
- Updated to use PlantUML library version 1.2021.3 (see changes).
- Added new extension point that supports generating several alternative diagrams for the same content (issue #109) and delays the computation of the diagram so it can run on a non-UI thread (issue #82). Uses of old extension point should still work, but should be updated to use new one.
- I needed to remove (for now) the feature that recomputes saved diagram images during builds, when their source have changed.
- Experimental PlantUML SVG view that handles zooming better (issue #116)
- Association is generated when type is Optional and for methods with a specific signature. (thanks to dpolivaev)
- Changes generated diagrams to use
name : typeUML format for attributes instead of java styletype name(issue #115) - Source features (issue #104)
- Support for diagrams in more text formats, including markdown (issue #65 and issue #91).
- Support for jlatexmath in separately installable feature (issue #72)
- Fixed bugs (issue #93 and (issue #95)
- Updated to use PlantUML library version 1.2019.11 (which includes support for mindmaps).
- Support for generating diagrams for views, e.g. Java element selected in Package Explorer (issue #84).
- Support for generating diagrams from console output.
- Preference page for enabling/disabling diagram providers.
- Avoid generating diagram (image) when PlantUml view is hidden.
- Moved list of diagram into sub-menu of view menu, handles issue #87.
- Now requires Java 1.8.
- Fixes bug (issue #77) concerning incompatibilit with Photon 2018.12.
- The view menu now lists the (explicit) diagrams in a file, so you can select and view it, without navigating inside the file. See (issue #61)
- Updated to use PlantUML library version 1.2019.0.
- Fixes include bug (issue #73).
- Updated to use PlantUML library version 1.2018.12, which fixes another include bug.
- Fixes include bug (issue #35) and copying, exporting and printing pages of multi-page diagrams.
- Fixes problem with dangling Ecore objects (issue #36)
- Fixes problem with object attribute values with newlines and braces (issue #37) by truncating. Also truncates long attribute value strings, to make object boxes smaller.
- Support for marker:/.../ hyperlinks to specific objects within a file, using the Marker API. Ecore object diagrams now use this kind of marker.
- Fixes problem with missing void operation (issue #40). Also appends "[]" to many-valued types.
- Save action, for exporting image or puml file into workspace, and auto-save feature, for automatically updating saved files when the source changes (issue #41).
- Updated to use PlantUML library version 1.2018.9
- Support for the newpage directive. Multi-page diagrams are rendered as numbered tabs (issue #11).
- Support generating packages for project class diagram, and a preference to turn on/off (issue #18).
- Object diagram generator, currently used as a default for Ecore model instances. To support overriding this behavior, e.g. so an Ecore model for state machines can be rendered as state diagrams, diagram text providers can now have a priority (issue #33).
- Refactored project layout, to conform to Eclipse conventions. Prepared for separating PlantUML library and Eclipse plugins update sites, so they can be released separately. The library plugin and feature has changed to same versioning as the jar.
- Support links to fully qualified java classes with java scheme links (issue #31), e.g. java:java.lang.String. Add a fragment to navigate to a specific member. Default diagram generation from java source now uses this kind of link.
- Fix problem with enums in project class diagrams, where associations where generated for the literals (issue #30).
- Hyperlinks that are just paths or use the platform scheme are opened in the default Eclipse editor (issue #25). Class diagrams generated from Java code utilize this feature by including navigatable path links.
- Open several PlantUML views and pin them to a specific resource (issue #21). Please comment on the behaviour.
- Support for hyperlinks, see http://plantuml.com/link (issue #24)
- Experimental support for generating a class diagram for a set of Java files (issue #18). Open the PlantUML Project Class Diagram and drag a Java project or package into the view (suggest improvements by adding a comment to the issue).
- support for generating class diagram for .class files shown in the Class File editor
- Includes EPL-ed version of plantuml.jar
- Fix for issue #13 - recompute diagram on activate not just broughtOnTop