Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [stellation-res] CVS Directory Structure 
Jonathan,

I'm sorry that you're having problems.
I'll take a look at the "Setting Up Stellation..." document and revise it as needed. 

Meanwhile, there are at least two different approaches: importing selecting
projects and importing the works.  I'll describe both.

A. Importing selected projects

This is how I normally set up an Eclipse workspace for Stellation in Windows:
1) Make the toplevel ('root') folder for the workspace in some appropriate location. 

2) Create a deskop shortcut for launching Eclipse in that workspace.
Here are some typical deskop properties.
Target: F:\Dev\eclipse\eclipse.exe -data E:\Projects\Stellation\eclipse\workspace -vmargs -Xmx256M 
Start in: E:\Projects\Stellation\eclipse\workspace
where F:\Dev\eclipse is where I keep the current version of Eclipse (2.1 M5 at present) 
and E:\Projects\Stellation\eclipse\workspace
is the root folder of my main working Stellation workspace.
The -vmargs argument tells Eclipse to use 256M for virtual memory; I will expand this when I get more memory. 

3. Launch Eclipse using the shortcut just created.
3a. Go to Windows > Preferences > Workbench and turn off 'Perform Build Automatically on Resource Modification' 


4. Open the CVS perspective and add the Stellation CVS repository
host: dev.eclipse.org
path: /home/technology

5. Using the CVS browser (left pane), navigate to org.eclipse.stellation,
and open the plugins folder.

6. Highlight the desired projects
(e.g. org.eclipse.stellation.{cli, core, remote, scm.model, scm.ui, unittest}
and often org.eclipse.stellation.{scm, scm.feature, vsf, vsf.feature} as well.) 

7. Right-click and select 'Check Out as Project'
All selected projects should now be checked out and added to the Eclipse workspace 
as Eclipse Projects.

8. Open / return to the PDE perspective.
9. Import all the required plugins as binary projects. (I think this was described in "Setting Up Stellation...."). 
I typically
* turn off the option for importing source
* manually select org.eclipse.team.ui, org.junit, and the third-party libs (oro, log4j, jdom, often postgresql) needed by Stellation. 
* Click 'Add required plugins'
* Import everything selected.
10. in the Package View, click a plugin, right-click and select 'Update Classpath'''', click 'Select All' and then update all classpaths. 

11. Select Project > Rebuild All

Everything should build ok (unless I forgot a step).
I do this routinely, and the command-line builds (core/build-core.xml) work fine for me **as long as I am using the patched build-core.xml**. I am still waiting for someone to verify the patch, and the version currently in CVS is flaky (in my view, broken/unreliable). 
Please see Bugzilla #31589 for details and the patch.

B.  Importing the Works

Follow steps 1-4 above.

5.  Highlight 'org.eclipse.stellation' (the top node for the entire project)

6. Right click and 'check out as project'.

This imports **everything** and eats disk space (lots of javadoc).
It's useful primarily for website maintenance, since the resulting workspace
has a single project org.eclipse.stellation. You cannot use Eclipse build the individual Stellation projects within the 'org.eclipse.stellation' Eclipse project, because Eclipse does not support sub-projects. 

Hope this helps,

Jim

At 10:22 AM 3/2/2003, Jonathan Gossage wrote:

I am having problems with the current CVS directory structure. In
particular, I am having a problem with the "org.eclipse.stellation/plugins"
directory. Since I used the instructions in the document "Setting up
Stellation in Eclipse" I do not have any of the CVS stuff above the Java
project directories. These directories simply show up in the root of my
Eclipse workspace.

It turns out that the build scripts are sensitive to the structure of the
complete directory tree and I have been unable to find any way, using the
Eclipse CVS support to download the complete CVS structure.

Ideally, what I would like to retrieve is the following structure:

org.eclipse.stellation
   doc
      All files and directories underneath
   docs
      All files and directories underneath
   plugins
      All files and directories underneath

I have yet to find a convenient way to this and it is impacting my ability
to test building and installing Stellation under Windows.

Regards

Jonathan

_______________________________________________
stellation-res mailing list
stellation-res@xxxxxxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/stellation-res



--------------------------------------------------------------------
Jim Wright, IBM T.J. Watson Research Center
*** The Stellation project: Advanced SCM for Collaboration
*** http://www.eclipse.org/stellation
*** Work Email: jwright@xxxxxxxxxxxxxx ------- Personal Email: jim.wright@xxxxxxx

Back to the top