Ok, I probably haven't completely configured it since I was using ./
bin/plexus.sh which doesn't use those properties.
However, please note that the macosx run.sh doesn't work on intel
macs (we need to see if jsw has been updated...)
- Brett
On 01/10/2006, at 4:33 AM, Henri Yandell wrote:
The plexus runtime didn't work:
===========================================================
./bin/macosx/run.sh
Usage: ./bin/macosx/run.sh { console | start | stop | restart |
status | dump }
./bin/macosx/run.sh start
Starting @[EMAIL PROTECTED]
./bin/macosx/run.sh status
Removed stale pid file: ./@[EMAIL PROTECTED]
@app.long.name@ is not running.
ls logs/wrapper.log
logs/wrapper.log
more logs/wrapper.log
STATUS | wrapper | 2006/09/30 11:30:09 | --> Wrapper Started as
Daemon
===========================================================
On 9/30/06, Henri Yandell <[EMAIL PROTECTED]> wrote:
I'll give that a shot and document that as well in the getting
started.
Hen
On 9/30/06, Brett Porter <[EMAIL PROTECTED]> wrote:
> It creates a bin directory with scripts to start it as a standalone
> server. You can certainly use the WAR if you already have a servlet
> container.
>
> On 30/09/2006, at 4:05 PM, Henri Yandell wrote:
>
> > On 9/29/06, Brett Porter <[EMAIL PROTECTED]> wrote:
> >> Yes, it's meant to ship with derby. I think if you change the
user/
> >> pass to sa and no empty string respectively it'll be fine.
> >>
> >> If you use archiva-plexus-runtime, it sets derby up in that
fashion.
> >
> > How do I use archiva-plexus-runtime? Currently I've been
assuming that
> > all of the projects get wrapped up into the war and that
that's the
> > only deployable.
> >
> > Hen
>
