You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our product today consists of just a single executable jar-with-dependencies.
We want to have appassembler generate a startup batch and shell script but we cannot afford for backward compatibility reasons to follow the standard appassembler directory layout. What we need is a simple flat structure containing both the jar and the startup scripts.
I tried to make such a layout work with appassembler to no avail. The generated batch script always looks for the parent directory of the script and then looks for a nested directory $repositoryName}.
Are we missing something?
We've been testing with 1.10 and 2.1.0 versions of appassembler.
Our product today consists of just a single executable jar-with-dependencies.
We want to have appassembler generate a startup batch and shell script but we cannot afford for backward compatibility reasons to follow the standard appassembler directory layout. What we need is a simple flat structure containing both the jar and the startup scripts.
I tried to make such a layout work with appassembler to no avail. The generated batch script always looks for the parent directory of the script and then looks for a nested directory $repositoryName}.
Are we missing something?
We've been testing with 1.10 and 2.1.0 versions of appassembler.
Our pom.xml:
The text was updated successfully, but these errors were encountered: