1
0
mirror of https://github.com/octoleo/plantuml.git synced 2024-12-21 02:19:14 +00:00
Commit Graph

79 Commits

Author SHA1 Message Date
soloturn
357720e4cb gradle upload artifacts in any case, like mvn did before 2022-02-13 15:44:16 +01:00
soloturn
8417f23d3e gradle, github publish plantuml-pdf jar
plantuml-pdf-<version>.jar is not signed at the moment.
2022-02-13 15:44:12 +01:00
soloturn
ba4c7da3e4 gradle, separate test, and build/upload 2022-02-12 09:46:43 +01:00
soloturn
defeb87909 gradle, clean, maven publication, same version for build/sign 2022-02-12 08:13:40 +01:00
soloturn
fc674de09f sign step checks environment var from gpg step 2022-02-11 13:00:55 +01:00
soloturn
8603c8da91 gradle, build and sign artifacts in 2 steps
release is not from windows 2019, daemon can be used
2022-02-11 12:10:58 +01:00
soloturn
12fce2cfd6 no gradle daemon so windows 2019 can use the cache.
in case somebody wonders about the confusing message that a daemon
is started, an explanation here:
https://discuss.gradle.org/t/no-daemon-switch-ineffective-if-jvm-settings-cause-new-fork/14919/7
2022-02-11 10:00:05 +01:00
soloturn
7d256adde6 switch default build to gradle, fixes #47 2022-02-11 09:41:40 +01:00
soloturn
b27c1fc50d revert github workflows to use java8, java11, java17
github workflow should use the various java versions to test,
which permits to test especially 2d rendering differences.

the javac release flag is set to produce java8 binaries in
any case. not perfect, but we only loose a warning that
applets are to be removed after java17, trivial to display
by adding the javac release property, when using java17:

  mvn --batch-mode compile -Dmaven.compiler.release=17
  gradle clean build -x javaDoc -PjavacRelease=17

better would be to separate build and test, as suggested
by https://github.com/matthew16550, here:
https://github.com/plantuml/plantuml/pull/904
2022-02-11 08:13:03 +01:00
soloturn
2baa696e60 github workflow with various release again
it runs on all platforms with java-17, but the javac release flag
is set to 8, 11, and 17 respectively. artifact upload happens
from latest ubuntu LTS, 20.04, java-8.
2022-02-08 12:53:41 +01:00
soloturn
2bdb2f8300 github workflow --release flag needs build with 11
https://github.com/plantuml/plantuml/issues/898
2022-02-05 19:04:17 +01:00
soloturn
1b25c3c00b github workflow can use gradle.
workflow and scripts are duplicated so nothing existing breaks.
ci-gradle triggers are commented apart from the workflow trigger
which allows manual start, so one can compare artifacts.
2022-01-20 06:45:51 +01:00
matthew16550
fe66147806 Fix snapshot release when workflow does not sign artifacts 2021-12-09 21:03:26 +11:00
matthew16550
cb1468d8b3 Add artifact signing to CI workflow & publish signature files in snapshot releases. 2021-12-09 11:54:04 +11:00
The-Lum
1854dcc2b9
Sup Upload simple jar and no ci on .md or docs
Mod:
- Suppress `Upload simple jar` on artifact
- No CI on `.md` or `docs`

Ref.:
- https://github.com/plantuml/plantuml/discussions/653#discussioncomment-1684866
- https://docs.github.com/en/actions/learn-github-actions/workflow-syntax-for-github-actions#example-ignoring-paths
- https://github.blog/changelog/2019-09-30-github-actions-event-filtering-updates/
2021-12-01 22:54:25 +01:00
matthew16550
4be34fa45b Remove "windows-2016" runner from build matrix in github actions because it is deprecated. 2021-12-01 10:16:24 +11:00
matthew16550
54d0bf27b5 Update CI to create snapshot releases in GitHub 2021-11-13 17:37:17 +11:00
matthew16550
33cbfdd951 Minor syntax simplifications in ci.yml 2021-11-13 16:28:35 +11:00
The-Lum
3e9ea863ce
Update ci.yml
Add another artefact, with only the plantuml.jar 
See:
https://github.com/plantuml/plantuml/discussions/653#discussioncomment-1631002
2021-11-12 15:59:02 +01:00
matthew16550
96b5eba7c1 Speed up CI by only running "mvn package" when strictly necessary 2021-11-02 17:59:16 +11:00
matthew16550
0ca723a6d8 Change CI workflow to use multiple java versions & operating systems 2021-10-31 15:28:23 +11:00
dependabot[bot]
1ebd727d9f
Bump actions/setup-java from 2.3.0 to 2.3.1
Bumps [actions/setup-java](https://github.com/actions/setup-java) from 2.3.0 to 2.3.1.
- [Release notes](https://github.com/actions/setup-java/releases)
- [Commits](https://github.com/actions/setup-java/compare/v2.3.0...v2.3.1)

---
updated-dependencies:
- dependency-name: actions/setup-java
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
2021-09-30 01:13:05 +00:00
Matthew Leather
a35fa3e61c
Combine test & release workflows into single CI workflow 2021-09-03 15:57:59 +10:00
matthew16550
62933e2c9e Bump setup-java version to support "temurin" Java 2021-08-30 16:00:47 +10:00
matthew16550
f3226a1fa7 Change GitHub Workflows to use "temurin" Java.
(Docs for https://github.com/actions/setup-java were changed a few days ago to warn that "adopt" Java won't be updated anymore)
2021-08-30 15:49:55 +10:00
Asbjørn Ulsberg
9500aac9c4
Use AdoptOpenJDK
As setup-java@2 requires `distribution`, set it to `adopt`.

https://github.com/actions/setup-java/blob/main/README.md#Supported-distributions
2021-07-31 23:47:07 +02:00
dependabot[bot]
39465bdadf
Bump actions/setup-java from 1 to 2.1.0
Bumps [actions/setup-java](https://github.com/actions/setup-java) from 1 to 2.1.0.
- [Release notes](https://github.com/actions/setup-java/releases)
- [Commits](https://github.com/actions/setup-java/compare/v1...v2.1.0)

---
updated-dependencies:
- dependency-name: actions/setup-java
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
2021-07-31 17:10:24 +00:00
matthew16550
b6b8f7f537 Use GitHub workflow to attach JAR to GitHub Releases (resolves #557). 2021-05-23 15:30:08 +10:00
Arnaud Roques
c4540da8d7 Add a first Github Action for JUnit 2021-03-21 14:03:23 +01:00