8000 Automatic packaging of USE after successfull build · Issue #14 · useocl/use · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Automatic packaging of USE after successfull build #14

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.

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

Closed
h-man2 opened this issue Sep 17, 2021 · 0 comments · Fixed by #19
Closed

Automatic packaging of USE after successfull build #14

h-man2 opened this issue Sep 17, 2021 · 0 comments · Fixed by #19
Labels
enhancement New feature or request refactoring Internal improvements

Comments

@h-man2
Copy link
Contributor
h-man2 commented Sep 17, 2021

Is your feature request related to a problem? Please describe.
USE is currently not packaged as an easy to go archive.
Therefore, starting USE ist not as easy as before by executing a batch or bash file.

Describe the solution you'd like
Package the relevant artifacts of USE to a single Archive. Exclude source or solit into use.zip and use-src.zip

Describe alternatives you've considered
Only publishing USE to Maven-Repo, but this would exclude many non-developers.

Additional context
Structure before switch to Maven:
grafik

@h-man2 h-man2 added the refactoring Internal improvements label Sep 17, 2021
@h-man2 h-man2 changed the title Atomatic packaging of USE after successfull build Automatic packaging of USE after successfull build Sep 30, 2021
@h-man2 h-man2 added the enhancement New feature or request label Sep 30, 2021
@h-man2 h-man2 closed this as completed in #19 Oct 1, 2021
h-man2 added a commit that referenced this issue Oct 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request refactoring Internal improvements
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant
0