Re: [ide4edu-dev] Re: ide4edu-dev Digest, Vol 9, Issue 8

[cmatheso@xxxxxxxxxxx]

Sorry for all the questions, but I got 1 more..

Quoting "Wayne Beaton" <wayne@xxxxxxxxxxx>:
> The Team project set is basically a set of instructions for Eclipse  
> to load stuff from the CVS repository. You need to redownload the  
> file and reimport to get any changes. Alternatively, you can go to  
> the CVS perspective, and navigate to the "technology" project  
> repository, "HEAD" branch, org.eclipse.ide4edu to gain direct access  
> to the various artefacts.

Ok, I was able to successfully load the ide4edu stuff directly from  
the CVS repo. I synced directly to the head / ide4edu tag no problem.

However, I have 2 issues now:
1. It won't build individually. When the project set is in use, the  
build property knows how to find for ex. plugin.xml, but with the  
import from CVS, the same file is actually located here - following  
same ex. javalite/plugins/org.eclipse.ide4edu.javalite.ui/plugin.xml  
and thus can't find it and nothing builds.

2. Perhaps its just me, but whats up with the directory structure? Its  
really, *really* hard to follow. Is this a byproduct of using project  
sets primarily?

Heres the full path of one of our classes from the CVS Head directory:

...\org.eclipse.ide4edu\javalite\plugins\org.eclipse.ide4edu.javalite.ui\src\org\eclipse\ide4edu\javalite\ui\view\OpenNewLitePackageWizardAction.java

The file structure is repeated 3 times... Would it be worthwhile  
re-organizing the file structure (and making it consistent between  
scheme and javalite?). The solution to this would help fix #1 as well.  
What do you guys think? I personally like having a file structure that  
makes sense, so its easy to navigate, etc. etc.

Also, I will admit this is the 1st time I've used a team project set  
(I've always worked directly with the repo file structure instead). Is  
this (3 times repeated) file structure intended?


Thanks for your time and patience,
Cory.