Skip to content

Commit

Permalink
Fix path of jar in zip artifact
Browse files Browse the repository at this point in the history
Closes  #500

The tar operation was automatically relativizing the path, but not the
zip. So I went back to just using a relative path for the jar.
  • Loading branch information
shonfeder committed Jan 28, 2021
1 parent 31e144f commit 25a1f27
Show file tree
Hide file tree
Showing 2 changed files with 6 additions and 2 deletions.
3 changes: 3 additions & 0 deletions UNRELEASED.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,3 +10,6 @@
* Another change description, see #124
DO NOT LEAVE A BLANK LINE BELOW THIS PREAMBLE -->
## Bug fixes

* Fixed path of jar in ZIP distribution, reported in #500, see #506
5 changes: 3 additions & 2 deletions script/release-publish.sh
Original file line number Diff line number Diff line change
Expand Up @@ -42,8 +42,9 @@ cd "$PROJ_ROOT"
make clean
make apalache

# Location of the jar that get's published in releases
RELEASE_JAR="${PROJ_ROOT}/mod-distribution/target/apalache-pkg-${VERSION}-full.jar"
# Relative location of the jar that gets published in releases
# This must be a relative path. Aboslute paths break the zip archive.
RELEASE_JAR="mod-distribution/target/apalache-pkg-${VERSION}-full.jar"

# Confirm the jar was produced
if [ ! -f "$RELEASE_JAR" ]; then
Expand Down

0 comments on commit 25a1f27

Please sign in to comment.