Glenn, et al..
Thanks for the instructions!
I agree its possible to make Eclipse recognize where to get the source
from, but this method involves setting IDE-wide properties [*1], which
means it effects every project that would be loaded afterwards. Also,
there should be no need to create a separate project to set up the
correct directory structure [*2]. If it was already that way in CVS, you
could just pull, and point your IDE to the beginning 'net.sourceforge'
directory, and you'd be off and running.
Maybe I'm missing something, though.. is there a reason that the code is
not in CVS in package order (other than its always been done that way)?
Would it not be easier to have it that way already rather than
re-creating environments and so forth?
> -------- Original Message --------
> Subject: Re: CVS Hierarchy [Fwd: Re: help with eclipse?]
> Date: Tue, 03 Dec 2002 13:45:39 -0500
> From: gwg <gwghome@...>
> To: squirrel-sql-develop <squirrel-sql-develop@...>
> When I started using Eclipse on squirrel, I had the same trouble as you.
> Colin is also using Eclipse, and he sent me the following
> instructions. Once you get it set up, it is simple to do the cvs
> operations. When I checkout a clean cvs copy, it takes me less than 5
> minutes to re-create my Eclipse environment in the fresh directory.
> I'm posting this to the mail list in case other people have the same
> question and so that it is archived in a public place.
> Hope this helps.
> Colin Bell wrote:
> > Hi Glenn,
> > In Window/Preferences Java/New Project I tell Eclipse to use src
> > and bin for new projects. [*1]
> > I create a separate project for each component [*2] so my directory
> > structure is something like
> > squirrel-sql/app
> > squirrel-sql/fw
> > squirrel-sql/plugins/jedit
> > squirrel-sql/plugins/laf
> > etc.
> > For the framework project (all the code that ends up in fw.jar) I have
> > my source in a subfolder
> > squirrel-sql/fw/src
> > I create the project so that squirrel-sql/fw is the base directory
> > for it.
> > So the source is something like
> > squirrel-sql/fw/src/net/sourceforge/squirrel_sql/fw/sql
> > etc.
> > Then I create an app project and its folders
> > squirrel-sql/app/src/net/sourceforge/squirrel_sql/client/sql
> > In the app project I also add the fw project as one of the required
> > projects in the java Build path in the project properties.
> > And then I create another project for each plugin in a similar
> > fashion.
> > Grabbing the source from CVS should give you the correct directory
> > structure, I think the trick is setting the Eclipse preferences to
> > look for source in the src subdirectory.
> > Johan does it in a different way. He just has (I think) one project
> > with multiple source paths. The problem with doing it this way is its
> > easy to have incorrect references in the source. I.E. none of the
> > classes in the fw project should know about any of the classes in the
> > app project, no class in the app project should know about classes in
> > a particular plugin.
> > fw classes are supposed to be a generic set of classes that could be
> > used in any application.
> > This is my .classpath file for the fw project:
> > <?xml version="1.0" encoding="UTF-8"?>
> > <classpath>
> > <classpathentry kind="src" path="src"/>
> > <classpathentry kind="var" path="JRE_LIB" rootpath="JRE_SRCROOT"
> > sourcepath="JRE_SRC"/>
> > <classpathentry kind="lib" path="lib/log4j.jar"/>
> > <classpathentry kind="lib" path="lib/nanoxml-2.1.jar"/>
> > <classpathentry kind="output" path="bin"/>
> > </classpath>
> > Give me a yell if this doesn't help.
> > --
> > Colin Bell
> > http://squirrel-sql.sf.net
> > ----- Original Message -----
> > From: Glenn <gwghome@...>
> > Date: Friday, October 11, 2002 9:56 am
> > Subject: help with eclipse?
> >>From one of your messages I understood that you are using
> >>eclipse. If I
> >>misunderstood let me know, but if you are I'ld appreciate any tips
> >>can give me.
> >>My main problem at the moment is importing the source in a clean
> >>way. I
> >>have been able to get it to compile and start running, but it took
> >>a lot
> >>of tinkering and I can't see working that way on a permanent
> >>basis. I
> >>cannot see how to just suck in the code an run. The main problem
> >>to be that I cannot tell eclipse how to set up the package names
> >>import, so it includes the full path for the file in the package
> >>and then complains when that doesn't match the package name
> >>declared in
> >>the file. The other issue is how to tell it what to build and
> >>environment to use during that build.
> >>Any pointers you can suggest would be great! Thanks.