octoleo/plantuml
1
0
Fork 0
mirror of https://github.com/octoleo/plantuml.git synced 2024-12-22 19:09:03 +00:00
Code Issues Releases Wiki Activity
1,165 Commits 10 Branches 89 Tags 56 MiB
06978b87d0
Commit Graph

35 Commits

Author SHA1 Message Date
Arnaud Roques
957dfea0b5 Add project name and description 2023-03-09 19:44:20 +01:00
soloturn
4b5d5d703b update versions 2023-02-18 08:27:59 +01:00
Gábor Lipták
9fa39de8b2
Set POM details for publishing 
Signed-off-by: Gábor Lipták <gliptak@gmail.com>
 2022-09-28 19:49:44 -04:00
Gábor Lipták
38e01ca98c
Publish to OSSRH 
Signed-off-by: Gábor Lipták <gliptak@gmail.com>
 2022-09-26 19:51:56 -04:00
soloturn
64fe77dc58 update jupiter to 5.9.1, batik to 1.15 2022-09-24 11:09:53 +02:00
soloturn
e87413acda update gradle to 7.5.1, assertj, jupiter, setup-java. 
gradle-7.5.1 supports java-18.
 2022-09-17 19:01:12 +02:00
soloturn
809c239b29 suppress warning for pdf variant not published at the moment 2022-03-13 11:44:28 +01:00
soloturn
9fd761b1d1 add maven publiccation sonatype oss, new 2022-03-13 11:43:33 +01:00
soloturn
b85ad6e7ae add maven publication, first, to local filesystem 2022-03-13 10:37:03 +01:00
soloturn
18e6c41bfb use gradle in-memory asci-armored keys to sign artifacts 
on the commadn line this allows as before:
  gradle -q signMavenPublication signPdfJar -Psigning.gnupg.keyName=... - -Psigning.gnupg.passphrase=...

on github this allows to put the key and password into environment variables:
  ORG_GRADLE_PROJECT_signingKey: ${{ secrets.ARTIFACT_SIGNING_KEY }}
  ORG_GRADLE_PROJECT_signingPassword: ${{ secrets.ARTIFACT_SIGNING_PASSPHRASE }}
  gradle -q signMavenPublication signPdfJar
 2022-02-14 13:46:59 +01:00
soloturn
92e955ef03 upgrade fop, and mvn plugins 2022-02-14 13:33:27 +01:00
soloturn
2c44343fad gradle, sign plantuml-pdf.jar, and gh upload 2022-02-14 13:33:27 +01:00
soloturn
d582935e04 gradle pdfJar produces plantuml-pdf-<version>.jar 2022-02-13 14:54:25 +01:00
soloturn
858903fec3 pdf optional dependencies 2022-02-13 08:40:15 +01:00
soloturn
6fe6a4c988 gradle, reorder to permit fat jar and features 2022-02-13 08:21:51 +01:00
soloturn
b18175b25c gradle, avoid configuring tasks not run 2022-02-13 08:21:51 +01:00
soloturn
255b5180fe gradle, javadoc, add class-use + utf8 2022-02-13 08:20:58 +01:00
soloturn
06b6493f69 gradle, only sign when properties are there 2022-02-13 07:44:56 +01:00
soloturn
ad222ccc1b build.gradle.kts, project uses tab, not space indent 2022-02-11 11:13:46 +01:00
soloturn
1bb80c929c gradle, permit 'gradle test' with java8 2022-02-10 17:11:11 +01:00
soloturn
e15c58d9a2 allow "gradle build -PjavacRelease=17" to build java-17 binary 
for gradle now one could do:
gradle clean build -x test -x javaDoc -PjavacRelease=17

for maven something like this works to build a different target binary:
mvn clean package -Dmaven.test.skip=true -Dmaven.javadoc.skip=true -Dmaven.compiler.release=17
 2022-02-08 11:12:24 +01:00
soloturn
ecc8dfe60a gradle javadoc, addBooleanOption instead of addStringOption 2022-02-08 11:11:50 +01:00
soloturn
856cef2478 javac --release to build for java8, with java11+ 
javac since java9 has a new flat --release to build a binary which can be run
with an older java. the public API of that older release must be followed as
well.

the flags used before, -source, -target do not do this. therefor it got
unnoticed that plantuml did not compile and run in java7 any more, despite
beeing compiled for for java7.

https://github.com/plantuml/plantuml/issues/898
 2022-02-05 19:04:17 +01:00
soloturn
5476a75602 source code java8 compatible 2022-02-04 06:57:48 +01:00
PlantUML
7ea36d5090
Merge pull request #896 from soloturn/java7 
gradle, source code java7 compatible
 2022-02-04 00:14:41 +01:00
soloturn
2a43a7f616 simplify gradle structure 2022-02-04 00:02:32 +01:00
soloturn
a0d02b4f06 gradle, source code java7 compatible 2022-02-03 23:39:24 +01:00
soloturn
558c74abcb build.gradle.kts, add gpg signing 2022-01-15 23:23:06 +01:00
soloturn
eb37b1f33b gradle, version can now be set on command line. 
the default version is in gradle.properties, to change it e.g. to 1.0.0 call:
gradle build -Pversion=1.0.0
 2022-01-11 17:40:00 +01:00
soloturn
8479cf0898 build.gradle.kts, include manifest.txt, Build-Jdk-Spec 
the manifest classpath is to accomodate running it with pdf or not.
mvn can build via a profile. when building a binary without pdf,
the dependencies could be added later, and plantuml would know it
anyway as they are listed in the manifest.

the gradle way would be to use variant aware builds,
predominatntly this is used for android builds. multi-release
builds are not something for plantuml:
* https://developer.android.com/studio/build/build-variants
* https://docs.gradle.org/current/userguide/variant_model.html
* https://blog.gradle.org/mrjars
 2022-01-09 13:59:27 +01:00
soloturn
06ca72c650 build.gradle.kts, bump assertj-core to 3.22.0, junit-jupiter to 5.8.2 2022-01-09 01:42:06 +01:00
soloturn
284285140c build.gradle.kts, add unit testing 
improves #47
 2022-01-09 01:41:55 +01:00
soloturn
8058b11d27 reformat build.gradle.kts 2 indent 
project uses 2 spaces indent, lf as line ending, utf-8. make it easier
to follow this rule by adding a .editorconfig file which vscode and
intellij respect out of the box.
 2022-01-07 02:28:17 +01:00
soloturn
39331af67e build.gradle.kts, add javadoc 2022-01-07 01:45:46 +01:00
soloturn
fed524cd6d add basic gradle files to allow conversion to gradle in future, #47 2022-01-06 03:13:46 +01:00