Update to latest plantuml

[iloveeclipse]

I see that there is a 1.2021.14 version available : https://github.com/plantuml/plantuml/releases/tag/v1.2021.14

Can we update to this version?

Or, other way around: what is the relationship between Eclipse plugin and library - can we always update to latest, or is there some API that can be broken etc?

[hallvard]

There is no way to drop in a new library, it needs to be wrapped in an Eclipse plugin and published on the update site. This should ideally be automated, but that requires an effort I haven't found time for. I'll make sure to update the library for the next release, hopefully in a couple of weeks.

[iloveeclipse]

OK, thanks.

[elfwine]

Is there a way we can add latest plantUML library then build the plugin by ourselves and manually install the plugin into eclipse?

[travkin79]

Hello @hallvard,
what would be necessary to automate updating the Eclipse-plug-in to the newest plantuml.jar? Did you already have an idea how to do that?

[hallvard]

The (manual) process I use to update to a newer plantuml.jar is as follows:

• acquire the EPL-ed version of the jar and drop it into the libs folder of the corresponding plugin project
• update all references (to the previous jar) so they refer to the new one
• update the version of the plugin and feature projects to match the library's and update the reference in the site project
• build to create the packaged plugin and feature jars
• metadata about the new library feature must be added to the site composite and it must be pushed to the update site

All steps can be automated, but it will take time to make it right. You may be able to simplify it, e.g. by renaming the library jar to a standard name. Another approach is hosting the composite library site at plantuml.com and integrate this into their build process.

[kmierzeje]

Hi,

Maybe it would be easier to let the user provide an alternative path to plantuml.jar he downloads on his own?

There could be a note about potential compatibility issues and "do it at your own risk".

Optionally plugin might verify the version and maybe raise a warning to the user that his version of library was not tested with this version of extension, or something like that.

[travkin79]

Hi,
Since this issue cannot easily be solved, I started a discussion. Maybe we can somehow simplify making releases.