[Lift] Re: Proper way to upgrade Lift and Scala libs?

2009-09-16 Thread Ike

On Sep 16, 8:58 am, David Pollak feeder.of.the.be...@gmail.com
wrote:

 So, that's the Lift policy.  We will have to figure out if we're going to do
 a 1.0.3 release for Scala 2.8.  We're planning to release Lift 1.1 a few
 weeks after 2.8 goes live (which I'm expecting to be in late November-early
 January sometime.)

  It would be great if we could do something
  like mvn upgrade 1.0.2 or mvn upgrade current to take care of this, at
  least for minor upgrades.

 Maybe a Maven maven on the list will describe if that's possible.

Thanks again for your quick response David. I'll keep an eye on this
list for any related posts. I still think it would be a good idea to
have a central resource that lists official Lift releases for
reference. Maybe on the Wiki? Something like:

Current Stable Release: 1.0.2
Compiled with Scala: 2.7.5
Documentation: http://xxx
New project sample Maven line: mvn ...

Latest Milestone Release: 1.1-M5
Compiled with Scala: 2.7.5
Documentation: http://xxx
New project sample Maven line: mvn ...

Last SNAPSHOT Release: 1.1-SNAPSHOT
Compiled with Scala: 2.8-b4
Documentation: http://xxx
New project sample Maven line: mvn ...

I'm thinking a simple version of the Springsource download page for
example: http://www.springsource.org/download

I'll be happy to set up the initial page but I can't commit to keeping
it up-to-date at this point.

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



[Lift] Proper way to upgrade Lift and Scala libs?

2009-09-15 Thread Ike

Hi all,

I've seen in a couple of posts here that I can just update the
corresponding dependencies in the POM and get the updated libraries. I
did this for both the Lift libs (1.0 - 1.0.2) and the Scala lib
(2.7.5 - 2.7.6). Although Maven did download the new libraries now
I'm seeing the following warning on mvn jetty:run:

[WARNING] Multiple versions of scala libraries detected!

Should I just delete the previous version of the lib from somewhere?
removing it from the .m2/repository location didn't help.

Is there a reference for a suggested way to upgrade the Lift and Scala
version of *existing* projects? I couldn't find it in the Wiki. I
think this should be clearly documented somewhere (specially for a
v1.0) and I'll be happy to write a couple of paragraphs on it if I can
figure out best practices.

Thanks,

Ike

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



[Lift] Re: Proper way to upgrade Lift and Scala libs?

2009-09-15 Thread Ike

On Sep 15, 11:44 pm, David Pollak feeder.of.the.be...@gmail.com
wrote:
 On Tue, Sep 15, 2009 at 8:28 PM, Ike ikes...@gmail.com wrote:

  Hi all,

  I've seen in a couple of posts here that I can just update the
  corresponding dependencies in the POM and get the updated libraries. I
  did this for both the Lift libs (1.0 - 1.0.2) and the Scala lib
  (2.7.5 - 2.7.6).

 Lift (1.1-X and 1.0.1/1.0.2) is compiled against Scala 2.7.5  This is the
 version you should be using.

 Do not upgrade to 2.7.6  2.7.6 is a broken release.

Got it. Thanks David.

What about the upgrade process itself? Is editing the POM the
recommended way? What would be the proper way to verify the proper
versions/combinations to use in the future?

Any plans in the works for upgrading existing projects and keeping the
lift/scala libs in sync? It would be great if we could do something
like mvn upgrade 1.0.2 or mvn upgrade current to take care of this, at
least for minor upgrades.

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