David H. DeWolf wrote: > Have you tried to install without any of the lightweight changes you > reference . . .just to see if that works for you? I have three > different boxes that I've tried clean installs on and it seems to work > for me. That said, maybe I'm forgetting to clean out some maven > artifact that's making it work. . .
After reading your other message, I guess its likely to be the lightweight installer. It sounds as if I should use the default. I was a bit put off that by mention of databases and the like. I haven't dug in here, but I assume the memory-based(?) configuration option doesn't require any additional database stuff. This may not be helpful to mention, but the current apparent direction for the Pluto portal driver is somewhat the opposite from my reasons for choosing it. Originally, I was lookling at a uPortal deployment, and decided that was too complex for creating a test environment, but I did notice that Pluto's portal driver was relatively lightweight, which was just what I wanted. > After a clean checkout, try running: > > mvn clean:clean install pluto:install -DinstallDir=/path/to/tomcat-dir > > BTW, are you installing this into Tomcat or into the test container that > you're attempting to get working. Hmmm. . .if you're trying that it > could be attempting to use the jetty installer since it doesn't detect > tomcat. That could be a bug. I'm installing into Tomcat, to give me a working (hopefully!) reference for getting the test-container working with the latest Pluto revision. #g -- Graham Klyne Research Technology Service Oxford University Computing Services
