Conversation
Support sbt build.
Remove 2.10 support because scala-logging does not support scala 2.10.X.
# Conflicts: # README.md # pom.xml
|
If you want to switch to SBT, you can just make the switch. Doubling of the project build files will prove to be a maintenance pain-point. Otherwise let it be Maven. All I'm asking is just to pick one.
It's the developer's private thing, which environment he has, and hence which files to ignore. You can have your version of To have |
### ReflectionSuite.scala fix reflection name. ### FieldTestSuite1.scala Comment out oracle test. This test was skipped in maven test.
|
.gitignore is normally shared by git. SBT have a great advantage to cross build. |
It does not. It only prevents miss-adding of files, which are mentioned in it. The ones that aren't can still be added. To make your statement true, all the possible names, which don't relate to the project need to be mentioned. Which is kinda impossible. A person is responsible for what he does, a committer is expected to review his commits. I'm pretty sure you wouldn't be satisfied with one of the "gitignore" files that you've mentioned. So you'd be doing commits to that file. So, merges, discussions... All about what? Something that has zero value for the project. So I've found it wisest to just keep out of this problem and hence keep it out of my projects. Trust me, once you'll add the ".gitignore" line to your local ".gitignore" file you'll forget we ever had this conversation.
No problem. Switch to it, if you feel the need to.
What? |
Make to generate pom.xml by "sbt makePom" command
|
Remove .gitignore and pom.xml. |
pjfanning
left a comment
There was a problem hiding this comment.
Could you change the build.sbt common settings sorm version to 0.3.22-SNAPSHOT?
Also, could you change the sext version to 0.2.26.
I would also like to see the c3p0 dependency set to 0.9.2 instead of the current pre-release version.
| test("H2 initialization") { instance(DbType.H2).close() } | ||
| test("MySQL initialization") { instance(DbType.Mysql).close() } | ||
| test("Oracle initialization") { instance(DbType.Oracle).close() } | ||
| //test("Oracle initialization") { instance(DbType.Oracle).close() } |
There was a problem hiding this comment.
Is there a reason to turn this part of test off?
There was a problem hiding this comment.
Oracle tests ware broken, and I can't fix it because i'm not familiar with Oracle database.
| @@ -0,0 +1,82 @@ | |||
| package sorm.macroimpl | |||
There was a problem hiding this comment.
If we don't continue to do sorm 2.10 builds, do we need this class?
| // Comment to get more information during initialization | ||
| logLevel := Level.Warn | ||
|
|
||
| addSbtPlugin("com.typesafe.sbt" % "sbt-pgp" % "0.8.3") No newline at end of file |
There was a problem hiding this comment.
Could we look at using sbt-release plugin for publishing jars to maven repos? I use it in https://github.com/swagger-akka-http/swagger-akka-http and it is very effective.
|
@takezoux2 I did some testing of sorm 0.3.21 and found it only works in scala 2.11. It does look like for 2.12 support, we will need the cross compile support. What do you think it will take to get the sbt stuff merged? |
|
I have pushed a sorm_2.12 to the sonatype snapshots repo, based on https://github.com/scala212-forks/sorm. This is just an interim solution. |
|
Any reason this hasn't been merged to master? |
Scala 2.12 coming soon.So should support multi scala versions.
And I have a question. .gitignore file is removed. What was wrong?