edulify / play-hikaricp.edulify.com

HikariCP Plugin for Playframework 2.2.x and 2.3.x

Home Page:http://edulify.github.io/play-hikaricp.edulify.com/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Play 2.2.2 with play hikari plugin 1.0.0 not working

lalkhum opened this issue · comments

I am using Play 2.2.2 version and I followed the instruction details as specified in Readme.
My scala version being 2.10, still I got the following error.

com.edulify#play-hirakicp_2.10;1.0.0: not found

Also got anoother error which is

     com.edulify.play.hikaricp.HikariCPConfig.maxPoolSize(HikariCPConfig.scala:81)
                    <pre><span class="line">&nbsp;</span><span class="code">    com.edulify.play.hikaricp.HikariCPConfig.mapFromPlayConfiguration(HikariCPConfig.scala:65)</span></pre>             
                    <pre><span class="line">&nbsp;</span><span class="code">    com.edulify.play.hikaricp.HikariCPConfig.getHikariConfig(HikariCPConfig.scala:31)</span></pre>              
                    <pre><span class="line">&nbsp;</span><span class="code">    com.edulify.play.hikaricp.HirakiCPDBApi$$anonfun$1.apply(HirakiCPDBApi.scala:34)</span></pre>
                    <pre><span class="line">&nbsp;</span><span class="code">    com.edulify.play.hikaricp.HirakiCPDBApi$$anonfun$1.apply(HirakiCPDBApi.scala:32)</span></pre>

Any help appreciated.

Unfortunately the version 1.0.0 was not was not build with Scala 2.10 support. I think that is something we could do and will investigate it later.

Actually, it was build with scala 2.10 also. Did you add the Edulify repository to your build?

@megazord Actually, I figured out a way to configure up my Play 2.2.2 with scala 2.10 support by having created a file "hikaricp config file" that stores the database details as follows.

  1. In my play conf environment "dev.conf", I need the following line.
    db.default.hikaricp.file="conf/environments/hikaricp.dev.properties"
  2. The "conf/environments/hikaricp.dev.properties" file now contains
    {code}
    jdbcUrl=somejdbcUrl
    username=someuser
    password=***
    {code}

However, it is not able to pick up the default play config details from my environment config (for example dev.conf) as specified in the release note. My approach as above seems to be the only-working solution for this.

Note: It would be very useful to have a link to the specific version RELEASE note as another column in your play version support table.

Could you try with version 1.2.0 of the plugin? This is the last version that is binary compatible with Play 2.2.x.

Yes, I tried and it is working perfectly for me. Btw, I think it would be nice to add an extra column about the link to release notes/info in your play version support table(?)

Good idea. Do you mind submitting a PR with this change?

Done. Please find the created PR.

Merged. :-)

Thank you very much, @lalkhum.