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

Clean build.sbt #124

Closed
sebinside opened this issue Aug 19, 2019 · 0 comments
Closed

Clean build.sbt #124

sebinside opened this issue Aug 19, 2019 · 0 comments
Assignees
Milestone

Comments

@sebinside
Copy link
Member

@sebinside sebinside commented Aug 19, 2019

Description

After the project rework, the main build.sbt becomes somewhat cluttered. Since it seems to be possible, to split up all the information in multiple sbt files, we should do that, e.g. a dependencies.sbt like in the build project. Also, the project structure should be not documented in a sbt file, as mentioned in #123.

/*
 * A brief introduction of the sbt related folder structure:
 *       root
 *       |  build.sbt
 *       |  plugins.sbt (produced by the fetch task)
 *       |  -> api project (required to build plugins and the framework)
 *       |  -> a plugin source directory
 *       |  -> -> a plugin folder = plugin
 *       |  -> -> -> build.sbt
 *       |  -> -> -> source etc.
 *       |  -> -> another folder = another plugin
 *       |  -> -> -> build.sbt
 *       |  -> -> -> source etc.
 *       |  -> another plugin source directory (optional)
 *       |  -> gui project (build will be skipped, if missing)
 *       |  -> bootstrap launcher (for end-user deployments)
 *       |  -> build project (contains code for all sbt tasks and sbt related things)
 */
@sebinside sebinside added this to the pre-alpha 3 milestone Aug 19, 2019
@sebinside sebinside self-assigned this Aug 19, 2019
@sebinside sebinside closed this Oct 31, 2019
daniel0611 added a commit to codeoverflow-org/chatoverflow-launcher that referenced this issue Oct 31, 2019
daniel0611 added a commit that referenced this issue Oct 31, 2019
#124

93ddc3f has done this for the main repo
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.