Skip to content

Add build system with dependency management#21

Open
morgenkaffe3 wants to merge 181 commits into
GodDragoner:masterfrom
morgenkaffe3:master
Open

Add build system with dependency management#21
morgenkaffe3 wants to merge 181 commits into
GodDragoner:masterfrom
morgenkaffe3:master

Conversation

@morgenkaffe3
Copy link
Copy Markdown

@morgenkaffe3 morgenkaffe3 commented Nov 16, 2019

Add gradle as build system in order to manage dependencies properly.

This also enables us to use Github Actions for running tests and creating artifacts for every major OS.

I had to disable the updater though as it is not compatible with the new architecture yet.

GodDragoner and others added 30 commits October 26, 2018 01:31
Changes to your commit to improve performance and removed unnecessary code
Changes i told u about in skype
Fixed image scaling issue, showTaggedImage issue, domme imageset now shows untagged images
Still need to make refresh work though and look at image downloading
efficiency
@GodDragoner
Copy link
Copy Markdown
Owner

Why Gradle instead of maven?

@morgenkaffe3
Copy link
Copy Markdown
Author

Why Gradle instead of maven?

I kind of was using Gradle lately so I just used it for this too.
Also I kind of prefer the way Gradle configurations work.

And since there was no build tooling in this project yet I didn't really think that you would have a strong opinion on that?
Do you have an issue with Gradle?

On the update logic: I am still working on that. I just had to figure some thing out.

@morgenkaffe3
Copy link
Copy Markdown
Author

morgenkaffe3 commented Nov 28, 2019

@GodDragoner I've finished creating the configuration for update4j now.
For this to work I've used Github Pages. Therefore it would be necessary to have a detached gh-pages branch:

git checkout --orphan gh-pages
git rm -rf .
touch README.md
git add README.md
git commit -m 'initial gh-pages commit'
git push origin gh-pages

Additionally to access this from Github Actions you need to create a personal access token here with the repo permission.

That token must then be entered in the repository settings under secrets. The name must be ACCESS_TOKEN and the value the just generated token.

In order to try this you can download update4j here and run it with:
java -jar update4j-1.4.4.jar --remote https://morgenkaffe3.github.io/TeaseAIJava/releases/update
in an empty directory.

Edit:
I also created a simple Launcher:
https://github.com/morgenkaffe3/TAJUpdater

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

Successfully merging this pull request may close these issues.

3 participants