Not a complete solution (as that would indeed require additional
parents): The parent pom already has a dependencyManagement section,
which can indicate which exact version of a dependency should be used
in a child. Currently it's only used for the scala-lib and for the
servlet api. See [1] for mo
Thoughts about that presentation[1] (german): The slides indicate that
the presentation was for the W-JAX 2008 conference (Nov 2008), so it's
a bit older. While most of the stuff is nothing special (except that
he left out JPA in the persistence slides - was probably too new for
the submission dea
4-24MB XML? Ah well...
On the IDE side: if you open a file as textfile (instead of marked up
whatever, XML in your case) things 'usually' work. Editor might still
be too slow, but it's something to try. Either convince the IDE
somehow (open as..), otherwise either create a symbolic link or rename
d.php?t=45673
[2] SetEnvIf User-Agent ".*MSIE.*" nokeepalive ssl-unclean-shutdown
downgrade-1.0 force-response-1.0
On Mar 26, 3:50 am, "Charles F. Munat" wrote:
> Daniel,
>
> Thanks so much! This is excellent. I don't know if it's the problem, but
> it won&#
I'm not sure that this is of any help or even applies to lift, but we
had once a very similar situation with a corporate application.
Difference was that the problem occurred when you were working slower.
Here's the description of the problem and what the reason was. When we
ran our application in
g config a
> bit.It also expands the POM via those dependencies. Bottom line: I'd like to
> avoid it if we can, but I don't have a problem if it ends up being the best
> way to do it.
>
> Derek
>
> On Mon, Dec 15, 2008 at 10:08 PM, Daniel Mueller
> wrote:
>
>
uld hate to make it
> an implicit requirement of using Record with JPA; it's just huge.
>
> Derek
>
> On Mon, Dec 15, 2008 at 12:46 PM, Daniel Mueller
> wrote:
>
>
>
> > I never did it with JPA, that's why I mentioned that there might be
> > some pro
thing transparent but easy to use.
>
> Derek
>
> On Mon, Dec 15, 2008 at 12:39 AM, Daniel Mueller
> wrote:
>
>
>
> > (Reactivating discussion. I guess it's been discussed more on the
> > committer list, but here you have my 2 cents anyway)
>
> > For th
(Reactivating discussion. I guess it's been discussed more on the
committer list, but here you have my 2 cents anyway)
For the sake of the Record-JPA discussion, people will fall into two
categories when they are using lift:
* The first group of people have an existing, working, tested JPA/OR
bas
