Dependency issue

[Joel]

Adding lift-mongodb-record to my LiftProject.scala file[1] gives me
this[2].

Why is it changing 2.4-M2 to 2.4-SNAPSHOT?
http://scala-tools.org/repo-releases/net/liftweb/lift-mongodb-record_2.8.1/2.4-M2/lift-mongodb-record_2.8.1-2.4-M2.jar
exists, but
http://scala-tools.org/repo-releases/net/liftweb/lift-mongodb-record_2.8.1/2.4-SNAPSHOT/lift-mongodb-record_2.8.1-2.4-SNAPSHOT.jar
doesn't.

1 - http://pastie.org/2185465
2 - http://pastie.org/2185462

[Joel]

Even more fun, if I change that entry to
"net.liftweb" %% "lift-mongodb-record_2.8.1" % liftVersion

Then it will look for lift-mongodb-record_2.8.1/2.4-SNAPSHOT/..., but
it will also look for lift-mongodb-record_2.8.1_2.8.1/2.4-M2/...
(which doesn't exist either but at least 2.4-M2 doesn't disappear) so
I'm starting to think this is some kind of cache error.

[Tim Nelson]

Hi,

Snapshot versions are in a different repo. If you want to use the snapshot version you need to add

val scalatoolsSnapshot = ScalaToolsSnapshots

to your project file.

Tim

[Joel]

I don't want the snapshot version, I want the 2.4-M2 version. sbt is
automatically looking for the snapshot version and I want to make it
not do that.

[Derek Chen-Becker]

It appears that one of your dependencies is itself depending on 2.4-SNAPSHOT. A quick look at

https://github.com/foursquare/rogue/blob/release_1_0_9/project/build.properties

says Rogue is the culprit. I'm not 100% certain, but I think that trying to mix 2.4-M2 with Rogue 1.0.9 is going to cause some pain and suffering. It doesn't appear that a version of Rogue has been built against 2.4-M2. In case you were worried, our SNAPSHOT releases are generally very stable, but I don't know if you have other reasons for wanting to use M2.

Derek

--
You received this message because you are subscribed to the Google Groups "Lift" group.
To post to this group, send email to lif...@googlegroups.com.
To unsubscribe from this group, send email to liftweb+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.

[Joel]

Works fine with the snapshot version, thank you.

On Jul 8, 11:43 pm, Derek Chen-Becker <dchenbec...@gmail.com> wrote:
> It appears that one of your dependencies is itself depending on
> 2.4-SNAPSHOT. A quick look at
>

> https://github.com/foursquare/rogue/blob/release_1_0_9/project/build....

>
> says Rogue is the culprit. I'm not 100% certain, but I think that trying to
> mix 2.4-M2 with Rogue 1.0.9 is going to cause some pain and suffering. It
> doesn't appear that a version of Rogue has been built against 2.4-M2. In
> case you were worried, our SNAPSHOT releases are generally very stable, but
> I don't know if you have other reasons for wanting to use M2.
>
> Derek
>
>
>
>
>
>
>
> On Fri, Jul 8, 2011 at 5:41 PM, Joel <ho...@joeldt.net> wrote:
> > Adding lift-mongodb-record to my LiftProject.scala file[1] gives me
> > this[2].
>
> > Why is it changing 2.4-M2 to 2.4-SNAPSHOT?
>

> >http://scala-tools.org/repo-releases/net/liftweb/lift-mongodb-record_...
> > exists, but
>
> >http://scala-tools.org/repo-releases/net/liftweb/lift-mongodb-record_...
> > doesn't.
>
> > 1 -http://pastie.org/2185465
> > 2 -http://pastie.org/2185462

[Naftoli Gugenheim]

Is that a typo, that you have a %% and _2.8.1? Two percent signs means sbt adds the scala version itself.

[Indrajit Raychaudhuri]

The other thing you can (rather, encouraged to) consider is just depending on the right version of rogue and let the relevant lift dependencies pulled up transitively.

Thus, just having "com.foursquare" %% "rogue" % "1.0.9" as your project dependency is sufficient, you can remove all the other "net.liftweb" ... modules.

BTW, for Rogue, 1.0.9 is quite old, try 1.0.13 instead :)

- Indrajit

On Sunday 10 July 2011 at 1:57 AM, Joel wrote:

> Works fine with the snapshot version, thank you.
>

> On Jul 8, 11:43 pm, Derek Chen-Becker <dchenbec...@gmail.com (http://gmail.com)> wrote:
> > It appears that one of your dependencies is itself depending on
> > 2.4-SNAPSHOT. A quick look at
> >
> > https://github.com/foursquare/rogue/blob/release_1_0_9/project/build....
> >
> > says Rogue is the culprit. I'm not 100% certain, but I think that trying to
> > mix 2.4-M2 with Rogue 1.0.9 is going to cause some pain and suffering. It
> > doesn't appear that a version of Rogue has been built against 2.4-M2. In
> > case you were worried, our SNAPSHOT releases are generally very stable, but
> > I don't know if you have other reasons for wanting to use M2.
> >
> > Derek
> >
> >
> >
> >
> >
> >
> >
> > On Fri, Jul 8, 2011 at 5:41 PM, Joel <ho...@joeldt.net (http://joeldt.net)> wrote:
> > > Adding lift-mongodb-record to my LiftProject.scala file[1] gives me
> > > this[2].
> >
> > > Why is it changing 2.4-M2 to 2.4-SNAPSHOT?
> >
> > > http://scala-tools.org/repo-releases/net/liftweb/lift-mongodb-record_...
> > > exists, but
> >
> > > http://scala-tools.org/repo-releases/net/liftweb/lift-mongodb-record_...
> > > doesn't.
> >
> > > 1 -http://pastie.org/2185465
> > > 2 -http://pastie.org/2185462
> >
> > > --
> > > You received this message because you are subscribed to the Google Groups
> > > "Lift" group.

> > > To post to this group, send email to lif...@googlegroups.com (mailto:lif...@googlegroups.com).

> > > To unsubscribe from this group, send email to

> > > liftweb+u...@googlegroups.com (mailto:liftweb+u...@googlegroups.com).

> > > For more options, visit this group at
> > > http://groups.google.com/group/liftweb?hl=en.
>

> --
> You received this message because you are subscribed to the Google Groups "Lift" group.

> To post to this group, send email to lif...@googlegroups.com (mailto:lif...@googlegroups.com).
> To unsubscribe from this group, send email to liftweb+u...@googlegroups.com (mailto:liftweb+u...@googlegroups.com).