This repository was archived by the owner on Aug 18, 2020. It is now read-only.
Add deployment for plugin developers #103
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Damn you regex.....
…vs with the new gui.
|
Works fine! But needs the same framework reload that i forgot in #109. We should totally write a wiki entry for this @derNiklaas. Please not that I updated the project sbt file to match the new gui jar, when you're reworking the |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #21.
This adds a new sbt command called
deployDevwhich works the same as the normaldeploytasks but doesn't copy the api and bootstrap launcher, copies additional files fromdeployment-files-devinstead fromdeployment-filesand includes the raw api project directory.It also includes IntelliJ run configurations, a stripped down
build.sbtand the required files of the meta build to allow for plugin development.The original idea was to also use the bootstrap launcher used in normal "user" deployments for this, but when everything was started through the bootstrap launcher jar the IntelliJ debugger didn't work at all. With the current implementation dependencies are handled by sbt, the framework jar is added to sbt and everything is started by IntelliJ.