[Lift] Re: [ANN] Lift 1.1-M8

2009-12-31 Thread joseph hirn
Heiko, I just tried runtime scope and I get the same exception when recompiling a Scala file with jetty still running. Do you experience the same? org.h2.jdbc.JdbcSQLException: Database may be already in use: Locked by another process. Possible solutions: close all other connection(s); use the

[Lift] Re: [ANN] Lift 1.1-M8

2009-12-31 Thread joseph hirn
This response explains your intentions with the archetype, which is to have a warfile that you can drop into an unmodified container. I assumed it would be to get a development environment setup as quickly as possible and since jetty:run is the prescribed method of getting started, I thought it

[Lift] Re: [ANN] Lift 1.1-M8

2009-12-30 Thread joseph hirn
Hello David. It's true that if you only have the dependency marked as provided then yes, it won't run. I am not advocating the use of using scope provided. That is only if you are programming to the h2 interfaces directly which you aren't and shouldn't be doing. I am advocating that you do not

Re: [Lift] Re: [ANN] Lift 1.1-M8

2009-12-29 Thread David Pollak
On Mon, Dec 28, 2009 at 1:13 PM, joseph hirn joseph.h...@gmail.com wrote: Thanks for the response Indrajit. Yes this is the same issue I had opened 246 for and sorry for beating a dead horse. The thing is that in most cases, you do want to container to provide the db driver. If this is the

Re: [Lift] Re: [ANN] Lift 1.1-M8

2009-12-28 Thread Indrajit Raychaudhuri
Joseph, I assume your concern is same as the one that you had mentioned here: http://github.com/dpp/liftweb/issues/246/find. While this is a genuine case for the scenario you described, marking db driver as 'provided' has the side effect of not being included with the generated war (because

[Lift] Re: [ANN] Lift 1.1-M8

2009-12-28 Thread joseph hirn
Thanks for the response Indrajit. Yes this is the same issue I had opened 246 for and sorry for beating a dead horse. The thing is that in most cases, you do want to container to provide the db driver. It's bad practice to create a war file with dependence on a specific database, let alone a

[Lift] Re: [ANN] Lift 1.1-M8

2009-12-27 Thread joseph hirn
I had started another thread about this being a derby issue but it's more related to the archetype. Still in the M8 archetype, h2 db is dependency of the project rather than a dependency of Jetty. It is better to have jetty declare the h2 dep because it keeps the sample app database independent.