plantuml / backlog

Contains all issues for plantuml that are not currently working-in-progress
0 stars 0 forks source link

-output is misleading #40

Open Kernald opened 4 years ago

Kernald commented 4 years ago

The documentation of -output states:

To generate images in the specified directory

But it's not what it does. The images are in this directory hierarchy relative to the diagram source.

Let's imagine this folder structure:

.
├── input
│   └── test_graph.puml
└── output

And run plantuml -o output input/test_graph.puml. The result is incoherent:

.
├── input
│   ├── output
│   │   └── test_graph.png
│   └── test_graph.puml
└── output

Verbose log:

(0.000 - 240 Mo) 234 Mo - PlantUML Version 1.2019.11
(0.014 - 240 Mo) 234 Mo - GraphicsEnvironment.isHeadless() true
(0.015 - 240 Mo) 234 Mo - Forcing -Djava.awt.headless=true
(0.015 - 240 Mo) 234 Mo - java.awt.headless set as true
(0.015 - 240 Mo) 234 Mo - Forcing resource load on OpenJdk
(0.079 - 240 Mo) 234 Mo - Found 1 files
(0.079 - 240 Mo) 234 Mo - Working on /home/kernald/puml/input/test_graph.puml
(0.097 - 240 Mo) 233 Mo - Setting current dir: .
(0.097 - 240 Mo) 233 Mo - Setting current dir: /home/kernald/puml/input
(0.098 - 240 Mo) 233 Mo - Using default charset
(0.108 - 240 Mo) 233 Mo - Reading from test_graph.puml
(0.170 - 240 Mo) 232 Mo - Reading file: input/test_graph.puml
(0.361 - 240 Mo) 225 Mo - Compilation duration 188
(0.362 - 240 Mo) 225 Mo - Regex total/invoked/compiled 66/35/24
(0.363 - 240 Mo) 225 Mo - Matches created 25
(0.520 - 240 Mo) 219 Mo - Creating file: /home/kernald/puml/input/output/test_graph.png
(0.602 - 240 Mo) 215 Mo - Creating image 275x216
(0.651 - 240 Mo) 214 Mo - Ok for com.sun.imageio.plugins.png.PNGMetadata
(0.740 - 240 Mo) 213 Mo - File size : 6879
(0.742 - 240 Mo) 213 Mo - Number of image(s): 1
weiyu10 commented 4 years ago

I meet same bug

swmatisa commented 4 years ago

try plantuml -o ../output input/test_graph.puml

arnaudroques commented 1 year ago

Can we close this one?

Kernald commented 1 year ago

Unless either the behaviour or documentation changed, I don't think it should be closed.