Hi Lawrence, On 8/1/06, Lawrence Mandel <[EMAIL PROTECTED]> wrote:
>An alternative to importing is to create a new java project and point >it to the directory you checked out woden to. The wizard for creating >the new project will create a .project for you and use the .classpath >already present. A more common usage pattern with Eclipse is to simply checkout an existing project into your workspace.
+1 to that. I was just trying to diagnose why Gilbert was having troubles using the process of importing the source. Using the SVN plugin is by far the easiest route.
I think we should revisit including the project information (.project, .classpath) in the repository. When working on multiple branches of Woden at the same time the project name can always be renamed using the technique you described.
Sure if we determine this is the root of the problem. Jeremy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
