Explain the reason of this project in README

[dev590t]

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.

• Why it is better to use maven2sbt than sbt-pom-reader?
• Why you have choosen to create this project instead of contribuate to ebiznext/maven2sbt? And why it is better to use Kevin-Lee/maven2sbt instead of ebiznext/maven2sbt.

[kevin-lee]

Hmmm I never compared mine with others. 🙂 But it's a good idea to put why I created it. Thanks! I'll update it.

[dev590t]

I can see 3 arguments if I compare maven2sbt to sbt-pom-reader

maven2sbt is more "reliable" than sbt-pom-reader

Even 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 contradictory

A developer want want use sbt tool on maven project, because he doesn't know/want maven pom.xml langage and maven cli tool.
With sbt-pom-reader, it solves only the problem of "doesn't know/want maven cli tool". If the user want modify/read the builder configuration file, he still need use pom.xml. It is contradictory with the reason that why he want use sbt on a maven project.
With maven2sbt, he doesn't have this problem.

maven2sbt is more reusable than sbt-pom-reader

If it exists a compiler from sbt builder configuration to mill builder configuration: sbt2mill.
It is possible to create a new compiler maven builder configuration to mill builder configuration
def maven2mill = maven2sbt compose sbt2mill

So the project can also interest the community of others builder.

Conclusion

I 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?