eltimn / lift-mongoauth Goto Github PK

Hi,

Is a mongoauth for Lift 2.5-RC6 planned, or will you wait for the final version before publishing a new 2.5? This is not a show stopper for me, as I am fine using the RC4 at the moment, for which a version exists. Just asking.

Regards

Rudolf

[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[warn] :: UNRESOLVED DEPENDENCIES ::
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[warn] :: net.liftmodules#mongoauth_2.10;2.5-RC6-0.4: not found
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[trace] Stack trace suppressed: run 'last *:update' for the full output.
error sbt.ResolveException: unresolved dependency: net.liftmodules#mongoauth_2.10;2.5-RC6-0.4: not found

I'm using lift-mongoauth in one project. I've found that the Role class is defined with private constructor, so it cannot be extended. For example in my case I want to add description field to each role, but I suppose there can be different scenarios.

Is there any reason to hide Role constructor?

I've created a branch for consideration: d6y_sonatype

This is a simplification to the build to publish the module without the full Lift version in the module version number.

This means rather than a Lift project depending on...

"net.liftmodules" %% "mongoauth" % "2.5-M4-0.4"

...it instead depends on:

"net.liftmodules" %% "mongoauth_2.5" % "0.4"

This is because the version number (2.5-M4-0.4) is not strictly a valid Maven version number, which causes problems for some people who run their own repository proxy.

Additionally, by including the Lift edition ("2.5") in the name of the module, we do not have the publish the module again for the whole life of Lift 2.5. (Unless the module changes, of course).

If you're happy with this I can publish:

"net.liftmodules" %% "mongoauth_2.5" % "0.4"
"net.liftmodules" %% "mongoauth_2.5" % "0.5-SNAPSHOT"
"net.liftmodules" %% "mongoauth_3.0" % "0.5-SNAPSHOT"

As Lift 3.0 is only SNAPSHOT, I've assumed you'd want just 0.5-SNAPSHOT there.

Hi all

I am working with Lift 3 (the last version) and I am getting exceptions because some classes are still using .save instead of .save()

I'll send a pull request with the fixes

Thanks!

Any chance this can be made compatible with Lift 2.5-M1 release? Thank you.