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.

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

Add release artifact to travis build #530

Open
codeallthethingz opened this issue Nov 4, 2017 · 0 comments
Open

Add release artifact to travis build #530

codeallthethingz opened this issue Nov 4, 2017 · 0 comments

Comments

@codeallthethingz
Copy link
Member

As this project is managed by maven, the lib folder seems to bloat the project unnecessarily.
I may be wrong but the reason the lib folder seems to exist is to have a runnable version of the product at git checkout. I feel that having a runnable version of the product should be accomplished by releasing a tagged version of the product that can be downloaded from the github release page. This tagged version can be automatically created as part of the travis build process and then downloaded and run with a simple java -jar htm.java-X.X.X.jar or, alternatively/additionally, download a tagged zipped version with included dependencies. htm.java-X.X.X-with-dependencies.zip

lf this makes sense I'd like to have a go at:

  1. Updating the travis build to include releasing artifacts: Travis + Github Releases
  2. Remove the libs folder
  3. Provide a script to the numenta git admin to obliterate the lib folder from git history so checkouts are nice and fast.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant