Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Automate launch scripts generation #46

Open
Toparvion opened this issue Aug 26, 2020 · 1 comment
Open

Automate launch scripts generation #46

Toparvion opened this issue Aug 26, 2020 · 1 comment
Labels
enhancement help wanted Issues whose solution needs help from the community (i.e. from you)
Milestone
The essential CI

Comments

@Toparvion
Copy link
Owner

Currently, to prepare a new distribution of AnaLog, several manual steps are required to make the launch scripts fully operational. In particular, environmental variable with the path to tail should be included as well as some JVM options should be specified (see the archives in the latest release for example).

The generation of the scripts should be fully automated, i.e. a single Gradle task (possibly parameterized somehow) should be enough to produce a fully operational AnaLog distribution.
@Toparvion Toparvion added enhancement help wanted Issues whose solution needs help from the community (i.e. from you) labels Aug 26, 2020
@Toparvion
Copy link
Owner Author

Possible solutions may come from these resources:

@Toparvion Toparvion added this to the The essential CI milestone Nov 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement help wanted Issues whose solution needs help from the community (i.e. from you)
Projects
None yet
Milestone
The essential CI
Development

No branches or pull requests
1 participant
@Toparvion