RE: [stellation-res] CVS Directory Structure

["Jonathan Gossage" <jgossage@xxxxxxxx>]

> -----Original Message-----
> From: stellation-res-admin@xxxxxxxxxxxxxxx
> [mailto:stellation-res-admin@xxxxxxxxxxxxxxx]On Behalf Of Jim Wright -
> IBM Research
> Sent: Sunday, March 02, 2003 12:07 PM
> To: stellation-res@xxxxxxxxxxxxxxx
> Subject: 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.

I was doing this and it works fine so long as I stay within Eclipse. The
problem starts as soon as I try to do anything from the command line. Maybe
I am using the wrong build files. My understanding is that everything should
start with org.eclipse.stellation/current.xml. Is this correct?

Regards

Jonathan