Skip to content

Commit 75eb8f1

Browse files
committed
Add the .local/bin to PATH env
1 parent aac52b5 commit 75eb8f1

4 files changed

Lines changed: 11 additions & 6 deletions

File tree

.github/workflows/release.yml

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,10 @@ jobs:
1212
# parse the release version from the github ref
1313
# https://stackoverflow.com/questions/58177786/get-the-current-pushed-tag-in-github-actions
1414
- name: Set env
15-
run: echo "RELEASE_VERSION=${GITHUB_REF#refs/*/}" >> $GITHUB_ENV
15+
run: |
16+
echo "RELEASE_VERSION=${GITHUB_REF#refs/*/}" >> $GITHUB_ENV
17+
echo "$HOME/.local/bin/" >> $GITHUB_PATH
18+
1619
- name: show release version
1720
run: echo ${{ env.RELEASE_VERSION }}
1821

@@ -27,7 +30,9 @@ jobs:
2730

2831
# this setup is all for the github pages deployment to work
2932
- name: install sphinx
30-
run: pip3 install --user sphinx sphinx_rtd_theme
33+
run: |
34+
pip3 install --user sphinx sphinx_rtd_theme
35+
which sphinx-build
3136
3237
- name: setup git
3338
run: |

src/sphinx/archetypes/java_app/customize.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ configuration file during execution. You can define the configuration file locat
3030

3131

3232
The configuration path is the path on the **target** system. This means that native-packager needs to process this path
33-
to create a valid ``universal:mapping``s entry.
33+
to create a valid ``universal:mapping`` s entry.
3434

3535
* ``${app_home}/../`` is removed
3636
* ``%APP_HOME%`` is removed and ``\`` is being replaced with ``/``

src/sphinx/archetypes/java_server/customize.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
Application Configuration
55
=========================
66

7-
After :doc:`creating a package <my-first-project>`, the very next thing needed, usually, is the ability for users/ops to customize the application once it's deployed. Let's add some configuration to the newly deployed application.
7+
After :doc:`creating a package <java_app/index.rst>`, the very next thing needed, usually, is the ability for users/ops to customize the application once it's deployed. Let's add some configuration to the newly deployed application.
88

99
There are generally two types of configurations:
1010

src/sphinx/formats/graalvm-native-image.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
.. _graalvm-native-image-plugin:
22

33
GraalVM Native Image Plugin
4-
=============
4+
===========================
55

66
GraalVM's ``native-image`` compiles Java programs AOT (ahead-of-time) into native binaries.
77

@@ -48,7 +48,7 @@ Settings
4848
--------
4949

5050
``native-image`` Executable Command (Pay attention if you are using Windows OS)
51-
~~~~
51+
5252
Putting ``native-image`` in ``PATH`` does not work for Windows. ``native-image`` is a batch file in Windows that calls another executable to compile the Java classes to a standalone executable. Therefore, the full path to the batch file e.g. ``C:\Program Files\Java\graalvm\bin\native-image.cmd`` must be provided. It is important to include ``.cmd``.
5353

5454
``graalVMNativeImageCommand``

0 commit comments

Comments
 (0)