db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dyre.Tjeldv...@Sun.COM
Subject Re: GSOC Student
Date Tue, 25 Mar 2008 10:51:41 GMT
thinking outloud <thoughts.loudspeaker@gmail.com> writes:

> Finally I've got the "BUILD SUCCESSFUL" message.
> So yes i was trying to set up my build and test environment and now it's up
> and working.
> This great document <http://wiki.apache.org/db-derby/BuildingDerby> helped
> me a lot (thanks to JohnHEmbretsen) even if (there is a but :) ) munching
> that we need to add JUnit
> in this document will be more helpful (it's sad in the
> BUILDING.txt<http://svn.apache.org/repos/asf/db/derby/code/trunk/BUILDING.txt>anyway).
> And *the step 5*<http://wiki.apache.org/db-derby/BuildingDerby#head-681537d04a4de5433e397238dd9bf22eaf8611cb>didn't
> really work for me (i am using NB6 + windows) because when i add
> *ant.library.dir=<path>* (and after clicking OK ) the build fail (ant
> problems) and when i try to redo the step 5 the path I've already added
> looked strange (may be a Netbeans bug??) so i changed this property in
> build.xml file (change ${ant.library.dir} to your path in tow places).
>
> In another hand it will be great to have someone in the IRC channel to talk
> to.

As a FYI to everybody out there that may be struggeling with this: The
instructions in BUILDING.txt does not (yet) take IDEs into
consideration. They should let you build Derby using a command line
shell, but chances are that you need to do some tweaking to make it work
inside an IDE (at least this is true for NB). Even more tweaking may be
required to get all the tests running inside NB (especially the old
harness which likes to fork processes and get information from
environment variables). Yet more tweaking may be required to get the
debugger to work, etc.

I guess you have already found out that the heuristic used by the build
system for finding the various JDKs needed doesn't work on Windows,
even if you choose the deafult installation locations for the JDKs. 

In general I believe that the Derby community has some work to do here,
because the goal should be to make it close to hassle-free to build, run
tests, and debug failures on the most common developer platforms, which
I believe to be some combination of Windows, Sun JDKs,
Eclipse/Netbeans. 

So please, keep the suggestions (and patches if you have) coming (create
Jira issues). Note however that changes must be discussed and reviewed
in the community so that they work for all platforms... 

-- 
dt

Mime
View raw message