-
Notifications
You must be signed in to change notification settings - Fork 3
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
Explain the reason of this project in README #150
Comments
Hmmm I never compared mine with others. 🙂 But it's a good idea to put why I created it. Thanks! I'll update it. |
I can see 3 arguments if I compare maven2sbt to sbt-pom-reader maven2sbt is more "reliable" than sbt-pom-readerEven if maven2sbt doesn't work correctly when it compiles some part of pom.xml, user still can manually fix the output build.sbt in order to get a runnable build.sbt. He won't never be blocked because a bug in maven2sbt. So even if maven2sbt isn't mature, contains bugs, it is still usable. sbt-pom-reader is contradictoryA developer want want use sbt tool on maven project, because he doesn't know/want maven pom.xml langage and maven cli tool. maven2sbt is more reusable than sbt-pom-readerIf it exists a compiler from sbt builder configuration to mill builder configuration: So the project can also interest the community of others builder. ConclusionI see many advantages in your project against sbt-pom-reader. If it is possible to list all interested sides of the project in the README. And give more visibility of the project in Scala community(ie: register the project in scaladex, or Awesome Scala), it is possible to attract many user/contributor. 🙂 But I still doesn't know why you have created a new maven2sbt project? |
Task
Description
There are already projects to using sbt on maven project, can you explain in the README why you created a new project for that and how it is better than others projects, in order to be able to attract more users and contributors.
The text was updated successfully, but these errors were encountered: