Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (nike.apache.org: domain of zepfred@gmail.com designates
 209.85.213.172 as permitted sender)
Subject: Re: Debug Derby inside IDE
References: 
 <CACcJavD3Uc1DgwsAxa7LcDNEB90xmv_RKBcMPE5++Ju4A1xQ6A@mail.gmail.com>
 <4F008B4A.2010902@gmail.com>
From: Frederico <zepfred@gmail.com>
Content-Type: text/plain;
	charset=utf-8
In-Reply-To: <4F008B4A.2010902@gmail.com>
Message-Id: <9041FA1F-AFF6-4811-B3BE-92F70A84D5A1@gmail.com>
Date: Sun, 1 Jan 2012 15:19:36 -0200
To: "<derby-dev@db.apache.org>" <derby-dev@db.apache.org>
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)

Thanks.

Att,

Fred

Enviado via iPad

Em 01/01/2012, =C3=A0s 14:35, Bryan Pendleton <bpendleton.derby@gmail.com> e=
screveu:

>> Is there any way to start/debug the database system inside the ide?
>=20
> Absolutely! Derby developers do this routinely.
>=20
> Derby is 100% pure Java, and so any Java debugger can be used to run Derby=
.
>=20
> When I do this, I build Derby using Ant, with debugging enabled in the com=
pilation,
> and then I start Derby with my debugger.
>=20
> Tell your debugger to use the main class org.apache.derby.tools.ij, then
> you can issue ij commands and set breakpoints in the Derby engine using
> your debugger.
>=20
> thanks,
>=20
> bryan