I don't know what the deal is, but I don't get the webapp failing
because of it.
Is there a reason not to use SA/empty since I've said that works?
- Brett
On 30/09/2006, at 4:53 PM, Henri Yandell wrote:
Got to love coincidence :)
So the real issue is that the first time there are exceptions and the
new database gets created. The exceptions stops the webapp from
starting and you have to shutdown and restart. I've updated my getting
started guide.
Hen
On 9/29/06, Henri Yandell <[EMAIL PROTECTED]> wrote:
In fact it was much simpler - I had to change the 'archiva' in the
url
to 'ARCHIVA' for some reason. Curious.
Hen
On 9/29/06, Henri Yandell <[EMAIL PROTECTED]> wrote:
> Gotya. So it's not intended to ship with Derby usually?
>
> It seemed like a good idea when reading Daniel's email. Much
simpler
> to get setup and running for a new user than having the docs
have to
> try to cover other databases.
>
> I'll dig into the Derby docs for basic setup and try again.
>
> Thanks,
>
> Hen
>
> On 9/29/06, Brett Porter <[EMAIL PROTECTED]> wrote:
> > I'm not a huge Derby expert, however I usually set it up with
> > user=sa, empty password, and it creates the schema on first run.
> >
> > - Brett
> >
> > On 30/09/2006, at 9:45 AM, Henri Yandell wrote:
> >
> > > I'm attempting to install Archiva from svn and having
problems. The
> > > following wiki page records where I currently am:
> > >
> > > http://docs.codehaus.org/display/MAVENUSER/Archiva
> > >
> > > which is that I've happily built things and have deployed a
war to
> > > Tomcat (using Daniel Mohni's very useful email threads). The
current
> > > bug I hit is that the embedded Derby database is not
initialized in
> > > any way:
> > >
> > > 2006-09-29 16:39:13,439 [main] WARN
RDBMS -
> > > Error initialising derby schema : Schema 'ARCHIVA' does not
exist
> > > ERROR 42Y07: Schema 'ARCHIVA' does not exist
> > >
> > > Does anyone have any suggestion as to how to do that?
> > >
> > > Hen
> >
>
