forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ross Gardler <>
Subject Re: Eclipse and forrest.
Date Tue, 17 Apr 2007 12:26:49 GMT
Gav.... wrote:
>> -----Original Message-----
>> From: Ross Gardler []
>> Sent: Tuesday, 17 April 2007 7:33 PM
>> To:
>> Subject: Re: Eclipse and forrest.
>> Gav.... wrote:
>>> I downloaded the latest Eclipse all-in-one package [1] that contains
>>> everything we need.
>> ...
>>> 1. Workspace, do you point to the forrest trunk as your workspace or
>>> somewhere standalone.
>> That's up to you. I'll tell you my setup - that works for me.
>> I have all public source code in:
>> ~/projects
>> Inside there I have loads of project folders, the forrest ones are:
>> ~/project/forrest-trunk
>> ~/project/forrest-ivy-branch
>> ~/project/apache-forrest-0.8
>> My eclipse workbench is set at
>> ~/project
>> I then use "working sets" to narrow down the projects I see at any one
>> time (see eclipse help docs for that, but if you only have a handful of
>> projects then you don't need to worry about it).
>> If you already have the sources checked out into your workbench folder
>> then simply  create a new project in your workbench and give the new
>> project the same name as the existing folder, i.e. "forrest-trunk".
>> Eclipse will spot there is already src here and work through an import
>> wizard with your.
> I did point to my working trunk which I use with SVN, I didn't like the fact
> that eclipse then created a few more folders of its own inside my forrest
> SVN tree, could get messy. I'd rather not have versioned/unversioned stuff
> mixed up like that. This was the main reason for this question, thought
> I'd messed it up big time.

Your working directory should not be your trunk checkout. If you set it 
up the way I suggested where (in my case) ~/project is the working 
directory and ~/project/forrest-trunk is the forrest project directory 
there is only one eclipse specific file to be created (.project) and 
you'll find this is already in svn:ignore

> The confusing thing for me then is, how do I work on trunk and debug it and
> update it etc whilst the workspace is pointing somewhere else, or is this a
> RTFM concidering I only installed it today? (I'm impatient, but that's
> hardly your problem). Or maybe, I do need this mixture of svn trunk and
> eclipse ?

The eclipse workspace does not map to each project. The workspace is a 
collection of all projects you want to work with in eclipse. This is 
getting off topic for this list, if you need to know more about the 
specifics of eclipse workspaces see the eclipse docs. If you want to 
know more about how I work with Eclipse and Forrest I'll expand further, 
but I already told you my set up and don't really know what else to tell 
you at this stage.

With respect to debugging, see Chris' reply for one option, or you can 
do what I do:

start forrest in debug mode (see our faq)
use the eclipse debugger by connecting to the running instance of 
forrest (I think there is a faq entry for that too, but I may be 
mistaken, more info if you need it)


View raw message