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

Move Sparkler to sbt build #184

Open
karanjeets opened this issue Jun 3, 2020 · 3 comments
Open

Move Sparkler to sbt build #184

karanjeets opened this issue Jun 3, 2020 · 3 comments
Assignees
Milestone

Comments

@karanjeets
Copy link
Member

Issue Description

Please describe our issue, along with:

  • expected behavior - should behave same what's on master
  • encountered behavior - N/A

How to reproduce it

If you are describing a bug, please describe here how to reproduce it.
N/A; Maven scala build plugins are not scalable

An external links for reference

Wondering what others are thinking? - https://www.jetbrains.com/research/devecosystem-2018/scala/

@karanjeets karanjeets self-assigned this Jun 3, 2020
@thammegowda
Copy link
Member

@karanjeets good to see you again buddy. whats going on here with this issue?

@karanjeets
Copy link
Member Author

hey @thammegowda,
I'm done with most of the work including, move pom to sbt build files, package app & plugins, exclude conflicting transitive dependencies, and resolve build issues. Left with the following items before I make a PR:

  • Version Control
  • CI
  • sparkler-ui - this is tricky! Our current war-overlay solution may not work. I would probably go the route of git submodule and package it via sbt. Anyway they have not updated maven since 2015 :-/
  • Final Testing
  • Coverage (may be only if I have time ?)

This would take another 2 weeks, probably

@thammegowda
Copy link
Member

wow that's exciting. Thanks.

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

3 participants