Please be aware that some listings have been temporarily delisted from our marketplace in order to improve the security of the platform. We apologize for any inconvenience this may caused.
For more information on this matter, please visit #1.
If you are a listing owner and would like to have your listing(s) reinstated, please open a ticket at https://gitlab.eclipse.org/eclipsefdn/it/websites/marketplace.eclipse.org/-/issues.
Thank you for your understanding and cooperation.
Reviews Sign in to post reviews
Version 3.1.1 released
Submitted by Albert Tregnaghi on Fri, 2023-02-10 16:58
There was a bug inside auto refresh for external previews (when TOC was enabled). Has been fixed with this hotfix.
Version 3.1.0 released
Submitted by Albert Tregnaghi on Fri, 2023-02-10 11:39
Version 3.1.0 has been relesaed on marketplace. For details look at
Version 3.0.1 released
Submitted by Albert Tregnaghi on Mon, 2023-01-23 12:50
Version 3.0.1 has been released. The hotfix fixes the problems with base dir calculation (for example diagrams were no longer correctly resolved).
For details look at https://github.com/de-jcup/eclipse-asciidoctor-editor/releases/tag/v3.0.1
Version 3.0.0 has been released
Submitted by Albert Tregnaghi on Fri, 2023-01-20 13:14
This version has some breaking changes + some new features
Version 2.7.0 released
Submitted by Albert Tregnaghi on Sat, 2022-07-30 19:32
Version 2.7.0 has been released on marketplace.
It contains hyperlinking for cross references.
The You Tube Video shows the new feature.
Version 2.6.1 released - fixes bug from 2.6.0
Submitted by Albert Tregnaghi on Tue, 2022-07-26 17:02
V2.6.0 had a base path calculation bug inside which resulted in problems with diagrams. I just released V2.6.1 which fixes this problem.
Version 2.5.1 released, fixes Windows path problem
Submitted by Albert Tregnaghi on Wed, 2022-05-04 21:29
Just released Version 2.5.1 on eclipse marketplace which handles a bug on Windows with 2.5.0
See Release V2.5.1 on GitHub for details.
Image generation always timing out.
Submitted by Michael Moser on Sat, 2021-05-22 17:37
I have installed the asciidoctor plugin on a second machine. Before I did I installed the GraphViz stuff and tested it and its working (you see - I learned my lesson with this plugin).
But now I have another most annoying effect:
If I create a testfile containing just
and save it then the plugin kicks in and a few seconds later I get an "image" that reads:
So, the config seems to be working.
However, as soon as I save a file that contains more than just 2-3 components or classes then the image generation always hangs "forever" (i.e. a minute or so) and all I ever get is a message like:
My Laptop is pretty fast (i7 CPU (10th gen), 16GB RAM, 1TB SSD, etc.) so I doubt that a simple picture with maybe 10 rectangles can really be taking so long that the graph generation times out.
Any idea what could cause this?
This is on eclipse 2021-03.
Re: Image generation always timing out.
Submitted by Albert Tregnaghi on Wed, 2021-07-07 18:11
you have put a lot of effort into providing the information, but please create an issue in GitHub project issue tracker and provide a sample file there that triggers the problem, so I can try to reproduce it.
Re: Image generation always timing out.
Submitted by Albert Tregnaghi on Sun, 2021-05-23 20:58
@Michael Moser: I just released v2.4.1 on eclipse marketplace which contians the bugfix.
Please update and try out. Changes are described at at https://github.com/de-jcup/eclipse-asciidoctor-editor/releases/tag/v2.4.1
Re: Re: Image generation always timing out.
Submitted by Michael Moser on Mon, 2021-05-31 04:12
Odd: on one system it's much better. On my second it's still incredibly lame (but no more timeouts, so that's definitely an improvement).
Re: Image generation always timing out.
Submitted by Albert Tregnaghi on Sun, 2021-05-23 16:41
I created issue #358 and copied your text there.
Please do me a favor and create issues always in official GitHub issue tracker . It's much easier to communicate and you can also update comments, examples etc.
Please refer the created issue for updates.
Version 2.3.0 released - fixes p2 update site location problem
Submitted by Albert Tregnaghi on Fri, 2021-05-07 21:49
I just deployed Version 2.3.0 to eclipse marketplace. Just do the update by the eclipse marketplace client (as usual).
The update site will automatically be updated and the new version fetched.
For details please look at https://github.com/de-jcup/eclipse-asciidoctor-editor/releases
Updatesite no longer available - alternatives?
Submitted by Hermann Kneissel on Wed, 2021-05-05 01:33
Marketplace install fails with
No repository found at ... dl.bintray.com/de-jcup/asciidoctoreditor
Is there an alternative update-site?
Re: Updatesite no longer available - alternatives?
Submitted by Albert Tregnaghi on Wed, 2021-05-05 19:56
I just tested - and most plugins are no longer hosted at https://bintray.com/de-jcup ! Only 3 repositories are listed: yamleditor, sqleditor, test-generic but not this one.
OMG. I have no idea why this happened - it seems this is an issue at bintray.
Nevertheless I will migrate other plugins as soon as possible and provide a new update url at marketplace.
I think I will provide a new version until end of this week.
For details look at https://github.com/de-jcup/eclipse-asciidoctor-editor/issues/333#issueco...
No more P2 on bintray
Submitted by Nicolas PERANSIN on Tue, 2021-05-04 12:40
I love the tool but Bintray is closed for free accounts. (I had the same issue)
Can you deploy in an other container please ? (I am considering Github-page myself)
Thanks for the great job.
Re: No more P2 on bintray
Submitted by Albert Tregnaghi on Wed, 2021-05-05 20:07
Yes it's always a 401 - unauthenticated...
When I first read https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-char... and their later updates on their website I was pretty sure that the repository data would be still available to Mai 2022.
But it seems its only for JCenter and not for bintray parts.
For details look at https://github.com/de-jcup/eclipse-asciidoctor-editor/issues/333
So this becomes now very urgent. I think I will provide a new version until end of this week.
Submitted by Andy Man on Tue, 2021-04-06 08:20
I'm trying to use C4-PlantUML via the the !include command. Unfortunately this seems to not work with Asciidoctor. I simply copied the first example from them. The example works fine if i just use PlantUML itself.
Would be great i that would work :)
PS: I cannot include the links to their github because links are forbidden (lol), if you google "C4-PlantUML" you should find it easily.
puml functionality not working
Submitted by Michael Moser on Sun, 2020-11-01 15:23
Freshly installed the plugin into my Eclispe 2020-09.
When I try to render a .puml file all I get is:
Any hint or guess what's not working?
Eclipse Version: 2020-09 (4.17.0) / Build id: 20200910-1200
Later edit: providing a test-file as suggested by the error message yields another error stating:
PlantUML version 1.2019.12 (Sun Nov 03 11:24:54 CET 2019)
The environment variable GRAPHVIZ_DOT has not been set
Dot executable is null
Error: Not dot executable found
Error: Only sequence diagrams will be generated.
That's at least telling a bit more. But what should I set this environment variable to? Some hints or instructions what one needs to (install and) configure before being able to use this plugin would have been helpful! Because I would have expected that this would run as-is after installing the plugin...
Re: puml functionality not working
Submitted by Alessandro Aiezza on Thu, 2020-12-03 10:17
I too, would benefit from a fix.
In the meantime, @Michael Moser, the PlantUML plugin seems to still work great!
Re: puml functionality not working
Submitted by Michael Moser on Sun, 2020-11-01 15:37
Googling further brought me here: https://github.com/de-jcup/eclipse-asciidoctor-editor/issues/47 which - among other stuff - had a link to- the download page for the graphviz utility (which is obviously required to render these files): https://www.graphviz.org/download/
I downloaded and installed the "Development Windows install packages" (x64 version) and after that the .puml visualization now works!
You may want to provide these instructions here on the plugin download page somewhere.
Re: Re: puml functionality not working
Submitted by Albert Tregnaghi on Wed, 2021-03-03 17:06
With #322 the editor will support also other install locations - in the meantime Plantuml must be installed standard way (as described in comment before).
yml rendering configuration usage
Submitted by Mario Janu on Tue, 2020-09-29 10:42
hi, how am i able to let the ascii doctor editor use my custom yml file to render it in the eclipse editor?
it is used correctly when i render via mvn.
thanks & regards
Re: yml rendering configuration usage
Submitted by Albert Tregnaghi on Sat, 2020-10-03 11:10
I think you were talking about inlcuding a yaml file example inside an asciidoc file.
I created Issue #96 at github to check for problems with yaml rendering.
Tried out embedded variant and also by including a file.
Both ways work out of the box, as shown in picture inside github issue.
If there are still questions/problems please add them to github issue.
Submitted by Jorge Menoyo on Thu, 2019-07-11 08:08
Its a good post from reolve the problem.
I have a [www.bilbolink.com/]
Version 2.0.2 available - fixes Windows OS startup problem
Submitted by Albert Tregnaghi on Tue, 2019-07-09 19:09
Release 2.0.0 did not work with Windows OS - see https://github.com/de-jcup/eclipse-asciidoctor-editor/issues/248 for details.
Is fixed with 2.0.2
Version 1.4.2 now available, install problems fixed
Submitted by Albert Tregnaghi on Thu, 2019-04-11 18:31
There were some issues with 1.4.0, 1.4.1 and 1.4.2 installation. This is fixed now and 1.4.2 can be installed without problems.
Sorry about the inconvenience.
PS: Parts inside library plugin has been updated as well, so this update is bigger than usual (~37 MB)
Submitted by Ole Jonny Vikevry on Tue, 2018-12-18 03:40
When I try to install the plugin, the process fails with the log statement shown below. The same error occurs both via the Install link on this site, Eclipse marketplace and Update site:
Using Eclipse 2018-09 on Win10.
(I have padded urls with whitespace due to form validation)
An error occurred while collecting items to be installed session context was:(profile=epp.package.jee, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). Unable to read repository at h t t p s : / / dl.bintray.com/de-jcup/asciidoctoreditor/plugins/de.jcup.asciidoctoreditor_1.2.0.jar. Received fatal alert: handshake_failure Unable to read repository at h t t p s : //dl.bintray.com/de-jcup/asciidoctoreditor/plugins/de.jcup.asciidoctoreditor.libs_1.2.0.jar. Received fatal alert: handshake_failure
Re: Handshake failure
Submitted by Albert Tregnaghi on Tue, 2018-12-18 10:16
I tried following: I downloaded https://dl.bintray.com/de-jcup/asciidoctoreditor/plugins/de.jcup.asciido... directly inside my browser (e.g. chrome) and had no certificate problems - or just open https://dl.bintray.com/de-jcup/asciidoctoreditor/plugins/
I also got a fresh eclipse 2018-09 and installed Asciidoctor Editor by marketplace (from a german location) and had no problems. Installation was done.
So I was not able to reproduce your problem.
About the problem
This sound like a SSL problem. Maybe you got the same probleme as described at https://github.com/gnu-mcu-eclipse/eclipse-plugins/issues/171 (other plugin but same issue)
Possible next steps
Please try to download the jar file or view the folder with your browser as described above.
If you have also SSL problems with your browser you could have a either
- proxy problems
- bintray is rolloing out new certificates (in this case please try a little bit later asgain)
- a "man in the middle"...
If it works in your browser than you could have a problem with your java version running your eclipse.
To solve this you can do either:
- import bintray certificates in java store of your JVM used for eclipse
- update your JVM used for starting eclipse or
- start your eclipse with another - suitable - JVM instance
Hope this helps