ExtCore is MIT Licensed and a candidate for JSArtifacts impl [1].
I started dabbling with an implementation of ExtCoreArtifacts sometime
back, but didn't have enough bandwidth to carry it forward.
In case somebody is willing to run with this, there is a ticket for
this already [2]
Non ExtCore
Most certainly, yes! Quite like what Anthony is looking for. But (a)
this is different from JSArtifacts implementation for ExtCore that we
talked about couple of times and (b) Cappuccino isn't license
compatible either (for the purpose of integration within Lift).
Anthony, fwiw, David did some
, at 09:40, Mads Hartmann Jensen wrote:
+1 for cappuccino
Played around with it a while back - it's pretty amazing.
What kind of intergration are we talking about? I wouldn't mind taking a look
at intergrating cappuccino.
On 10/03/2010, at 10.37, Indrajit Raychaudhuri wrote:
ExtCore is MIT
Folks,
As discussed earlier, lift-core would be removed from repository
sometime soon. For the deprecation notice and the rationale, please take
a look at the announcement posted earlier [1].
If your application is still using lift-core, make the changes NOW! Soon
it would stop working with
On 08/03/10 11:48 PM, David Pollak wrote:
On Mon, Mar 8, 2010 at 10:01 AM, Jeppe Nejsum Madsen je...@ingolfs.dk
mailto:je...@ingolfs.dk wrote:
Hi,
Just found out why the Logging stuff doesn't work on the 2.8 branch.
Details here:
Mads/Ross,
You have the requisite rights now. Feel free to post to lift-announce :)
Cheers, Indrajit
On 05/03/10 2:08 PM, Mads Hartmann Jensen wrote:
Tried to post this to lift-announce but I don't have permission - I did join
the group though so not sure why. How do i optain permission? I
Lukasz,
We don't have non-SNAPSHOT version of Lift for scala 2.8 branch yet.
You are encouraged to use 2.0-scala280-SNAPSHOT and report any issue
that you encounter.
Cheers, Indrajit
On 04/03/10 2:41 PM, Lukasz Kuczera wrote:
Hi Folks.
I'm working on lift 2.0-scala280-SNAPSHOT. What is
On 04/03/10 3:26 PM, Jeppe Nejsum Madsen wrote:
On Thu, Mar 4, 2010 at 10:39 AM, Indrajit Raychaudhuri
indraj...@gmail.com wrote:
Lukasz,
We don't have non-SNAPSHOT version of Lift for scala 2.8 branch yet.
You are encouraged to use 2.0-scala280-SNAPSHOT and report any issue that
you
On 04/03/10 10:42 PM, Stuart Roebuck wrote:
Trying this on 2.8 with the 2.8 Lift Snapshot.
The Logger trait seems to work fine though looking at the code I can't
see how setup gets called.
The Loggable trait is throwing a null pointer exception.
Yes, this is a known one. We encountered
You can modify smile dependency declaration to exclude slf4j-jdk14 as thus:
dependency
groupIdnet.lag/groupId
artifactIdsmile/artifactId
exclusions
exclusion
groupIdorg.slf4j/groupId
artifactIdslf4j-jdk14/artifactId
/exclusion
On 05/03/10 1:05 AM, harryh wrote:
OK, did that (like so in sbt):
override def ivyXML =
dependencies
dependency org=net.lag name=smile rev=0.8.12
exclude module=slf4j-jdk14/
/dependency
/dependencies
I'm also getting this error when running my app from within
which needs to be
removed after today's release
On 01/03/10 3:00 AM, Indrajit Raychaudhuri wrote:
I reopened #363 because according to Lift convention, JQuery14Artifacts
should actually refer to the compressed version of jquery-1.4.2 min that
is generated by yuicompressor-maven-plugin
On 03/03/10 9:21 PM, Jeppe Nejsum Madsen wrote:
Indrajit Raychaudhuriindraj...@gmail.com writes:
A quick followup on this minified js concern...
[...]
So the question is, should we:
1. Continue using yuicompressor (to compress js files at build time)
and apply the strategy universally
On 03/03/10 9:58 PM, David Pollak wrote:
On Tue, Mar 2, 2010 at 5:53 AM, Timothy Perrett timo...@getintheloop.eu
mailto:timo...@getintheloop.eu wrote:
Probally worth sticking this on the wiki
Cheers, Tim
Sent from my iPhone
Wait... you've got a broken hand and you can still
On 03/03/10 10:21 PM, Jeppe Nejsum Madsen wrote:
Indrajit Raychaudhuriindraj...@gmail.com writes:
[...]
My interest in the current context, is to have consistent behavior in
the js artifacts bundled with Lift.
To me (and Marius) #2 is also worth consideration. True that you'd
have a
The Lift Web Framework team is pleased to announce the framework-2.0-
M3 release!
Lift is an expressive and elegant framework for writing web
applications. Lift stresses the importance of security,
maintainability, scalability and performance while allowing for high
levels of developer
+1 Huge honor to be a part of the community.
Thank you David, thank you early committers, thank you early adopters.
- Indrajit
On 27/02/10 7:16 PM, Heiko Seeberger wrote:
I am proud to be on board and looking forward to the next three years
Heiko
On Saturday, February 27, 2010, David Pollak
Finally! Great job, Jeppe.
- IRC
On 28/02/10 9:44 PM, Jeppe Nejsum Madsen wrote:
The new logging code is now in master and should be fully usable.
Therefore, the existing logging code has been deprecated.
I've added a Wiki article here:
http://wiki.github.com/dpp/liftweb/logging-in-lift
You are using scalajpa-1.2-SNAPSHOT which is built with Scala 2.7.x and
thus binary incompatible with Scala 2.8.
To use 2.8 port of scalajpa, you should be using the version
scalajpa-1.2-scala280-SNAPSHOT.
Your best bet would be to start with a lift-jpa archetype from 2.8
branch. You could
I reopened #363 because according to Lift convention, JQuery14Artifacts
should actually refer to the compressed version of jquery-1.4.2 min that
is generated by yuicompressor-maven-plugin (and not minified version
available for download).
Marius, let me know if you agree to this, if not we
Done in master. Wait for Hudson to respin.
Committers, sorry for direct commit to master and breaking the rule but
Tim's need was urgent.
Have done quick smoke test locally.
- Indrajit
On 24/02/10 6:56 PM, Timothy Perrett wrote:
I can verify that the issue causing this is:
Given that setting initParams is the usual webapp idiom, should we not
consider that at all? That would have served the purpose for Petr.
So the calcRunMode could roughly have something like:
customRunMode or context.initParam(run.mode) or
Box.!!(System.getProperty(run.mode))
with provision
Understood, just wanted to ensure.
Cheers, Indrajit
On 22/02/10 4:25 PM, tbje wrote:
Hi Indrajit,
I was a little bit lazy and updated an old pom by hand.
Just pushed a new pom.xml using the following mvn
archetype:generate :
mvn archetype:generate -U -DarchetypeGroupId=net.liftweb -
Heavens! Need to give this a shot.
On 22/02/10 4:55 PM, Mads Hartmann wrote:
Hello everyone,
I've been working a bit on a TextMate bundle for Lift projects that
has codecompletion. It's still very beta but I'm sure someone would
find it helpfull :)
If you're interested you can read a bit more
On RB: http://reviewboard.liftweb.net/r/223/
Cheers, Indrajit
On Feb 3, 9:36 pm, Indrajit Raychaudhuri indraj...@gmail.com wrote:
Thanks Adam, I'll take this one up :)
- Indrajit
On 03/02/10 12:48 PM, Adam Warski wrote:
Sure:
(a)http://github.com/dpp/liftweb/issues/issue/320
(b
Folks,
If you are an i18n type, read it!
Going forward we are making two policy changes in the naming
convention for i18n resource keys; viz., Discontinuing the usage of
white space to separate keys and preferring all.lower.case for the
keys.
So in you locale properties file, instead of:
On 22/02/10 3:22 PM, Indrajit Raychaudhuri wrote:
Given that setting initParams is the usual webapp idiom, should we not
consider that at all? That would have served the purpose for Petr.
So the calcRunMode could roughly have something like:
customRunMode or context.initParam(run.mode) or
Box
Trond,
From cursory glance it appears that some old form of archetype (pre
Lift 2.0) had been used to generate the project. What command line
option did you use in mvn archetype:generate to create the project?
This is just a request for qualification.
Cheers, Indrajit
On 19/02/10 8:22 PM,
On 18/02/10 6:26 PM, harryh wrote:
If this does happen please take care to include this information in
the release notes for M3 (or whatever milestone first has this change)
as people using json serialization for caching purposes will need to
invalidate their caches.
Putting the note in BIG
No it wasn't. Would do over the weekend.
- Indrajit
On 17/02/10 8:31 PM, Ross Mellgren wrote:
Did the repo ever get converted for autocrlf? I don't remember seeing the
email. I have my autocrlf left alone and I don't have this issue.
-Ross
On Feb 17, 2010, at 9:46 AM, Heiko Seeberger wrote:
On 17/02/10 8:21 PM, Jeppe Nejsum Madsen wrote:
On Wed, Feb 17, 2010 at 3:45 PM, Heiko Seeberger
heiko.seeber...@googlemail.com wrote:
Hi,
Since a week or so I get modified files even when I create a fresh
clone of the repo. These are some js and css files from lift-widgets
and stuff from
On Feb 15, 1:52 pm, Heiko Seeberger heiko.seeber...@googlemail.com
wrote:
On 15 February 2010 09:45, Jeppe Nejsum Madsen je...@ingolfs.dk wrote:
Even if (probably) not needed, we should try to name it the best possible
way. Changing now causes no pain at all, but later ... you know.
On 15/02/10 7:46 PM, Jeppe Nejsum Madsen wrote:
On Mon, Feb 15, 2010 at 9:52 AM, Heiko Seeberger
heiko.seeber...@googlemail.com wrote:
On 15 February 2010 09:45, Jeppe Nejsum Madsenje...@ingolfs.dk wrote:
Even if (probably) not needed, we should try to name it the best
possible
way.
Nice, very nice!
On Feb 12, 2:26 pm, Timothy Perrett timo...@getintheloop.eu wrote:
Congratulations Ross.
Cheers, Tim
On Feb 12, 5:07 am, Ross Mellgren dri...@gmail.com wrote:
I've just pushed the CouchDB integration using Lift-JSON and Dispatch that
I've talked about on the list a
On 12/02/10 2:36 PM, Jeppe Nejsum Madsen wrote:
David Pollakfeeder.of.the.be...@gmail.com writes:
Jeppe Co.,
I've been thinking about the logging changes.
(would have been nice with this before I went and updated all the
archetypes examples...oh well :-)
How about a different
The Lift Web Framework team is pleased to announce the framework-2.0-
M2 release!
Lift is an expressive and elegant framework for writing web
applications. Lift stresses the importance of security,
maintainability, scalability and performance while allowing for high
levels of developer
On 11/02/10 10:37 PM, David Pollak wrote:
On Thu, Feb 11, 2010 at 9:05 AM, GA my_li...@me.com
mailto:my_li...@me.com wrote:
Thanks I am gonna try and test it.
When is 2.0-M2 going to be released?
Yesterday... trying to figure out why it didn't happen. Likely today.
The
scalacheck_2.8.0.Beta1 used in the branch 280_port_refresh now.
Tim, see if your build works on this branch now.
Cheers, Indrajit
On 04/02/10 12:12 PM, Indrajit Raychaudhuri wrote:
Sure, I will. This would go in as regular 280_port_refresh update activity.
Cheers, Indrajit
On 04/02/10 3:13
Hey Naftoli,
Man, it would be great *not to* mix up 2.7 and 2.8 codes inline.
Keeping it in sync with master would get very confusing and error prone
(personally I don't find that aesthetically pleasing either).
In fact, with some adjustment, it's possible to have parts of code
friendly
Hi Murtaza,
Everything since Lift 1.0 is new on Lift 2.0 [1].
There is a good chance that you'll find most as part of the changelog
that we maintain.
See the static version in project docs [2] or milestone-wise details in
Assembla [3] (we have them since 1.1-M6 here).
Cheers, Indrajit
Folks,
If your project has dependency on lift-core, this is important for you!
lift-core stands deprecated and Lift 2.0-M2 would be the penultimate
milestone with support for lift-core. Subsequently (after the milestone
2.0-M3) it would be unsupported.
lift-core is a 'meta' module that can
On 10/02/10 9:49 PM, David Pollak wrote:
On Wed, Feb 10, 2010 at 8:13 AM, Adam Warski a...@warski.org
mailto:a...@warski.org wrote:
Hello,
Yes, in fact there is a timespan method in CometActor. You
should be using Lift 2.0-M1 or 2.0-SNAPSHOT.
I'm using 2.0-SNAPSHOT:
Adam,
As mentioned earlier, please try *lifespan* instead.
def lifespan: Box[TimeSpan] is what you probably want.
- Indrajit
On 10/02/10 10:58 PM, Adam Warski wrote:
Hello,
to be extra sure I pulled the latest sources from git and recompiled.
And I still get an error:
error: method
Welcome Javier!
- a wild crowd member
On 09/02/10 9:39 PM, David Pollak wrote:
Folks,
Please join me in welcoming Javier Goday to the Lift committers. Javier
wrote the Lift LDAP module and now that he's a committer, he can make
the LDAP module part of the official Lift distribution (and the
...@gmail.com wrote:
On Sat, Feb 6, 2010 at 12:12 PM, Indrajit Raychaudhuri
indraj...@gmail.comwrote:
Go ahead! create tickets in Assembla.
Excellent job and a huge round of applause to Indrajit and Naftoli for
moving the tickets over the Assembla. Thanks guys!
Cheers, Indrajit
On 05/02/10 10
You have to register yourself as Watcher of the space liftweb to see
the New Ticket button :) We have this rule to avoid (Anonymous) spams
in the ticket.
Cheers, Indrajit
On 08/02/10 2:48 PM, aw wrote:
On Feb 7, 11:31 pm, Mariusmarius.dan...@gmail.com wrote:
Please open a defect
+1
Need to send a **BREAKING CHANGE** notice to lift-announce and liftweb
and update the Wiki possibly carrying the rationale behind.
Also clearly mentioning how the existing applications would behave
without making these changes (and what needs to be done to get the
existing behavior
Hmm, specs_2.8.0.Beta1 is the appropriate version aligned with Scala
2.8.0Beta1.
If you really find the expected behavior with specs_2.8.0.Beta1-RC8 but
not with specs_2.8.0.Beta1, we have an interesting behavior at hand.
Cheers, Indrajit
On 08/02/10 3:41 PM, Lukasz Kuczera wrote:
It seems
I digg this :)
Assembla docs has this to say on email alerts:
http://www.assembla.com/wiki/show/breakoutdocs/FAQ#EmailsAlerts
FWIW, I couldn't find admin settings to set this as space level default.
Cheers, Indrajit
On 08/02/10 5:41 PM, Erkki Lindpere wrote:
I noticed that Assembla sends a
Folks,
Lift 2.0 Milestone 2 release is coming soon!
This also means the master would get 'slushy' by end of day today
(PST) !
Committers please:
- merge all branches for outstanding ticket to master (subject to RB
approval)
- associate corresponding tickets in Assembla to appropriate milestone
Umm, the source jas are actually available in the repository along with
the binary jars :) Looks for lift-module-2.0-M1-sources.jar in the
same place as lift-module-2.0-M1.jar.
See any of the module location in
http://scala-tools.org/repo-releases/net/liftweb/lift-module/2.0-M1
for example.
+1 Welcome James!
Cheers, Indrajit
On 08/02/10 11:22 PM, Timothy Perrett wrote:
Wow, that was a long time comming!!
Welcome to the team James... great to finally have another UK bod!
Cheers, Tim
On 8 Feb 2010, at 17:16, David Pollak wrote:
Folks,
I'm wicked pleased that James Strachan
Migration complete!
Please DO NOT use GitHub Issue tracking facility anymore.
Use http://www.assembla.com/spaces/liftweb/tickets instead.
Cheers, Indrajit
On 04/02/10 2:05 AM, David Pollak wrote:
Folks,
On today's committer call, we made the final decision to move the Lift
ticketing system
Go ahead! create tickets in Assembla.
Cheers, Indrajit
On 05/02/10 10:49 AM, Naftoli Gugenheim wrote:
Indrajit and I are working on importing tickets into Assembla. The first
ticket on GitHub is #3 and there are now two on Assembla.
So please don't create any Assembla tickets until further
, 2010, at 3:12 PM, Indrajit Raychaudhuri wrote:
Go ahead! create tickets in Assembla.
Cheers, Indrajit
On 05/02/10 10:49 AM, Naftoli Gugenheim wrote:
Indrajit and I are working on importing tickets into Assembla. The first
ticket on GitHub is #3 and there are now two on Assembla.
So please don't
Folks,
Following David's announcement about moving our ticketing system to
Assembla [1], the migration is complete and we have now completely
moved from GitHub issues to Assembla tickets.
Please DO NOT use GitHub to create issues anymore (the GitHub URL
would be disabled), instead use this
On 05/02/10 5:28 PM, Jeppe Nejsum Madsen wrote:
Naftoli Gugenheimnaftoli...@gmail.com writes:
David and all,
QUESTION 1
I'm working on issue #258. Here are two options for an overridable parser
(applies to formatting too):
1. def parse(s: String): Box[Date] = ConversionRules.parseDate()(s)
Great stuff! Where did you get the github issue xml?
Cheers, Indrajit
On 03/02/10 10:14 AM, Naftoli Gugenheim wrote:
If anyone finds github's issue manager too limited, I made a teeny
little app that lets you list the issues in a more configurable way. All
comments welcome!
1. Fix in head/master (2.0-SNAPSHOT) and prepone 2.0-M2.
2. Backport in 1.0.x branch and spin 1.0.4. We haven't marked 1.0.x
'unsupported' yet. Forcing apps to move to 2.0-M2 just for this
vulnerability fix isn't fun.
Cheers, Indrajit
On 03/02/10 3:34 PM, Timothy Perrett wrote:
+1
Fix it
Naftoli,
Yes, looked at your source. I was curious about the source of the
downloaded xml you have in there.
http://develop.github.com/p/issues.html seems to have them all. Thanks!
Cheers, Indrajit
On 03/02/10 7:57 PM, Naftoli Gugenheim wrote:
They have an API. I think the site is
Thanks Adam, I'll take this one up :)
- Indrajit
On 03/02/10 12:48 PM, Adam Warski wrote:
Sure:
(a) http://github.com/dpp/liftweb/issues/issue/320
(b) http://gist.github.com/293435
I've also updated the wiki.
On Feb 2, 2010, at 8:10 PM, Indrajit Raychaudhuri wrote:
Adam, can you please
build.
Cheers, Tim
On Jan 31, 7:44 pm, Indrajit Raychaudhuri indraj...@gmail.com wrote:
I was suspecting Java 1.5 (if you were on 10.5). That's not the
case. So
I am completely stumped now.
See if you can compare with the Hudson copy
(http://hudson.scala-tools.org/view/Lift/job/lift-framework
Takeuchi-san,
Can you please set project.build.sourceEncoding=UTF-8 in your pom.xml
and check if it works?
You can set project.build.sourceEncoding in pom.xml the following way:
properties
project.build.sourceEncodingUTF-8/project.build.sourceEncoding
...
...
/properties
Cheers,
Look for MappedText. That maps to DriverType.clobColumnType (LONGTEXT
for MySQL).
Cheers, Indrajit
On 02/02/10 11:27 AM, XiaomingZheng wrote:
hi guys:
my app needs to use one field of mysql text type, but in Lift mapper
package, and i don't find any MappedField is suitable. any ideas?
thanks
Thanks for spotting this. Yes, DB drivers should be either in runtime
scope with optional=true or in test scope.
I missed out the optional=true declaration during recent DB dependency
refactoring (#307). But test scope is more appropriate in this case
(instead of runtime scope with
How about setting some global variable on a field change
(http://jqapi.com/#p=change) and then checking for the variable when you
navigate out (probably onunload or something)?
Cheers, Indrajit
On 03/02/10 12:01 AM, Naftoli Gugenheim wrote:
Hi, in Lift how would one implement functionality
Adam, can you please (a) open a ticket and (b) create a gist
(http://gist.github.com/) of the patch and refer to it from the ticket?
We'll take it up from there.
Tim, +1 on not having spaces in properties.
Cheers, Indrajit
On 02/02/10 10:41 PM, Timothy Perrett wrote:
Sure - one of us will
Yep, I did ;)
Cheers, Indrajit
On 03/02/10 1:21 AM, Timothy Perrett wrote:
Indrajit, I think you just volunteered to take this on good chap ;-)
Cheers, Tim
On 2 Feb 2010, at 19:10, Indrajit Raychaudhuri wrote:
Adam, can you please (a) open a ticket and (b) create a gist
(http
Welcome back, Tim!
I am suspecting that an incorrect spec version is sneaking in.
Just to confirm - the maintained 2.8 port branch is 280_port_refresh.
Cheers, Indrajit
On 31/01/10 11:02 PM, Timothy Perrett wrote:
I just attempted to build the branch and got the following:
Running
:4.7:test
Which is somewhat puzzling...
Cheers, Tim
On 31 Jan 2010, at 18:07, Indrajit Raychaudhuri wrote:
Welcome back, Tim!
I am suspecting that an incorrect spec version is sneaking in.
Just to confirm - the maintained 2.8 port branch is 280_port_refresh.
Cheers, Indrajit
On 31/01/10 11:02
I was suspecting Java 1.5 (if you were on 10.5). That's not the case. So
I am completely stumped now.
See if you can compare with the Hudson copy
(http://hudson.scala-tools.org/view/Lift/job/lift-framework-scala280/)
- IRC
On 01/02/10 12:55 AM, Timothy Perrett wrote:
Let's keep the unpacked excanvas for the sake of consistency. Using YUI
compressor at build time is what lift-webkit does at the moment.
How about injecting the excanvas JS conditionally (via ieMode)? This is
mostly cosmetic though.
Cheers, Indrajit
On 30/01/10 6:14 AM, Peter Robinett
On 30/01/10 3:23 AM, Jeppe Nejsum Madsen wrote:
David Pollakfeeder.of.the.be...@gmail.com writes:
On Fri, Jan 29, 2010 at 2:40 AM, Jeppe Nejsum Madsenje...@ingolfs.dkwrote:
Indrajit Raychaudhuriindraj...@gmail.com writes:
I am not sure you need to add yet another adapter on top of
On 30/01/10 2:47 PM, Jeppe Nejsum Madsen wrote:
David Pollakfeeder.of.the.be...@gmail.com writes:
[...]
If you're 100% sure that nothing will break, go for the slf4j-based
approach.
100% certainty is difficult :-)
How about this:
1) Implement new MDC functionality only for Slf4j
+0
Hi Lachlan,
In the mvn goal, you have to use -DarchetypeVersion=2.0-scala280-
SNAPSHOT instead :)
The full command should be:
mvn archetype:generate -U -DarchetypeGroupId=net.liftweb -
DarchetypeArtifactId=lift-archetype-basic -DarchetypeVersion=2.0-
scala280-SNAPSHOT
On 30/01/10 3:06 PM, Jeppe Nejsum Madsen wrote:
Indrajit Raychaudhuriindraj...@gmail.com writes:
On 30/01/10 2:47 PM, Jeppe Nejsum Madsen wrote:
David Pollakfeeder.of.the.be...@gmail.com writes:
[...]
If you're 100% sure that nothing will break, go for the slf4j-based
approach.
100%
David,
It's an honor. You are welcome!
- Indrajit
On 30/01/10 11:21 PM, David Pollak wrote:
Indrajit,
Thanks for yet again spinning a build and moving Lift forward!
Rock on!
David
On Fri, Jan 29, 2010 at 10:33 PM, Indrajit Raychaudhuri
indraj...@gmail.com mailto:indraj...@gmail.com wrote
Hi Lachlan,
On Jan 30, 5:50 pm, Lachlan Deck lachlan.d...@gmail.com wrote:
Hi Indrajit,
On 30/01/2010, at 8:43 PM, Indrajit Raychaudhuri wrote:
Hi Lachlan,
In the mvn goal, you have to use -DarchetypeVersion=2.0-scala280-
SNAPSHOT instead :)
Ah. That makes all the difference. Thanks
I am not sure you need to add yet another adapter on top of slf4j for
MDC support. Enhancing the existing slf4j wrapper for the purpsoe might
be worth an attempt instead.
Slf4j supports MDC (org.slf4j.MDC) and automatically delegates MDC
functionality to the underlying logging framework if it
Most certainly, the groupId for maven-jetty-plugin is missing.
The minimal configuration for jetty plugin would be:
plugin
groupIdorg.mortbay.jetty/groupId
artifactIdmaven-jetty-plugin/artifactId
version6.1.22/version
/plugin
Cheers, Indrajit
On 29/01/10
Memory: 8M/15M
[INFO]
bash-3.2$
On Thu, Jan 28, 2010 at 9:04 PM, Indrajit Raychaudhuri
indraj...@gmail.com mailto:indraj...@gmail.com wrote:
The Lift 2.0 snapshot jars for Scala 2.8 are now available
]
bash-3.2$
On Thu, Jan 28, 2010 at 9:04 PM, Indrajit Raychaudhuri
indraj...@gmail.com mailto:indraj...@gmail.com wrote:
The Lift 2.0 snapshot jars for Scala 2.8 are now available on
scala-tools Maven repository. Feel
mailto:feeder.of.the.be...@gmail.com wrote:
On Thu, Jan 28, 2010 at 9:04 PM, Indrajit Raychaudhuri
indraj...@gmail.com mailto:indraj...@gmail.com wrote:
The Lift 2.0 snapshot jars for Scala 2.8 are now available
on scala-tools Maven repository. Feel free to try
The Lift team is pleased to announce the lift-1.0.3 release!
Lift is an expressive and elegant framework for writing web
applications.
Lift stresses the importance of security, maintainability, scalability
and performance while allowing for high levels of developer
productivity.
Lift is a scala
]
[INFO] Total time: 33 minutes 11 seconds
[INFO] Finished at: Thu Jan 28 19:38:33 EST 2010
[INFO] Final Memory: 105M/527M
[INFO]
2010/1/28 Indrajit Raychaudhuri indraj...@gmail.com
Dear Greg,
It would be, in next couple of hours or so.
Cheers, Indrajit
On 29/01/10 5:42 AM, Meredith Gregory wrote:
Dear David,
Did the jars get pushed up to the Scala-tools.org Maven repository?
Best wishes,
--greg
On Wed, Jan 27, 2010 at 1:01 PM, David Pollak
The Lift 2.0 snapshot jars for Scala 2.8 are now available on
scala-tools Maven repository. Feel free to try your Lift application
against 2.0-scala280-SNAPSHOT jars.
You can change Lift artifact dependencies version to
2.0-scala280-SNAPSHOT in you application pom and proceed to build as
Hmm, I think this jQuery update should be sent as a separate
announcement. As this change that can create create ripple in an
application and qualifies as a 'potentially' breaking change.
Cheers, Indrajit
On 27/01/10 6:16 PM, Marius wrote:
This broke my app ... with flying colors :D
But
Awesome! :-)
Heiko
On Sunday, January 24, 2010, Indrajit Raychaudhuri indraj...@gmail.com
wrote:
Folks,
A quick update on Lift 2.0 build on Scala 2.8.
Scala 2.8 port of Lift is available on the branch 280_port_refresh. This
is a 'refresh'ed version of 280_port which is fully
Can you please rename the folder read only to read_only and give it
another try?
Cheers, Indrajit
On 28/01/10 12:24 PM, Jonathan Ferguson wrote:
Hi all,
I get the following error when attempting to build the lift source code.
[ERROR] Exception in thread main java.lang.NoClassDefFoundError:
Jeppe,
How about:
-- Fork http://github.com/dpp/liftweb to
http://github.com/jeppenejsum/liftweb and maintaining on your own with
frequent git pull dpp master
-- Deploy your artifacts to an internal server (all that you need is an
http server where you can 'deploy' the artifact via
Folks,
A quick update on Lift 2.0 build on Scala 2.8.
Scala 2.8 port of Lift is available on the branch 280_port_refresh. This
is a 'refresh'ed version of 280_port which is fully aligned and sync'ed
with the master.
To ensure minimal delta between the master and 280_port_refresh, the
if asked for its status with the operator ?~!
each due to the exception of:
java.lang.NoSuchMethodError: java.lang.String.isEmpty()Z
This is under OS/X 10.5, trying both Java 5 and Java 6. I've had no
problems building the original 280_port branch.
Thanks,
Dave
On 25/01/10 7:47 AM, Indrajit
Never mind, seems to be solved now.
In fact, quite often Maven users fall over this on OSX. I used to keep
JAVA_HOME set in ~/.profile in 10.5 for this reason.
Cheers, Indrajit
On Jan 25, 10:20 am, Indrajit Raychaudhuri indraj...@gmail.com
wrote:
David,
I tested it on OSX 10.6. Can you try
Sorry for the delay in response. Have been swamped with work activities
in last couple of days.
On 22/01/10 2:22 AM, David Pollak wrote:
Folks,
It's looking like Scala 2.8 RC8 will become 2.8 Beta1 on Tuesday.
I'd like to get the Lift 2.8 branch up to date (and keep it up to date)
with the
Cool. Welcome on board Jeppe!
On 22/01/10 10:17 PM, Timothy Perrett wrote:
Massively overdue welcome Jeppe!
+1
What are you hoping to contribute to Lift?
Cheers, Tim
On 22 Jan 2010, at 16:25, David Pollak wrote:
Folks,
Please join me in welcoming Jeppe as a Lift Committer. He's
Welcome on board, Mads!
Looking forward to the outcome of what you are fancying.
And all the best for your exams.
Cheers, Indrajit
On 20/01/10 3:56 AM, Mads Hartmann wrote:
I'm fancying this on too: http://github.com/dpp/liftweb/issues#issue/281
And that's it I think, for now at-least :)
On 18/01/10 7:10 PM, Tim Maxwell wrote:
Hi Folks,
I am messing around with the 2.0-M1 build and I can't figure out a
couple of things.
a. What is the prefered method of installing the lift-examples?
Go to the corresponding directory and do mvn package.
Once done, you would have all shiny
I guess you meant lift-archetype-basic :) That is meant for you to
quickly get started with a with a working project from scratch. It
doesn't really serve as example.
For examples, go to the examples directory at the top level. They
haven't been removed, just relocated from lift-examples to
Jeppe,
Good find! This happens because the new top level pom.xml hasn't been
deployed in the scala-tools repo.
Have fixed in master, give it a try in half an hour or so.
Cheers, Indrajit
On 18/01/10 2:49 PM, Jeppe Nejsum Madsen wrote:
Hi,
Just tried an mvn -U clean test and got this:
1 - 100 of 259 matches
Mail list logo
