[news.eclipse.tools] Re: IDE comparison

[andrew_sandstrom@xxxxxxx (Andrew Sandstrom)]

In my limited experience with Eclipse so far, the lesson I have learned
is: do not equate Eclipse streams with VisualAge Micro Edition team
streams.  Doing so gave me a huge headache.  As far as I can tell, you
can/should only treat a stream other than "HEAD" as a CVS branch, and not
as a mechanism for general purpose sharing. Maybe different repositories
will have a better story?

I agree wholeheartedly about need for Configuration Maps.  This is
especially important for embedded development when trying to manage
multiple targets for a wide array of devices.

-Andrew

David Whiteman wrote:

> Unforunately, team streams in that "previous OTI product" couldn't be
> versioned.  I have no idea if the Eclipse version of team streams have this
> capability.  But I definitely see the utility in being able to load a
> previous configuration into your workspace.

> David
> --
> ------------------------------------------
> David Whiteman
> david_whiteman@xxxxxxx
> ------------------------------------------
> "Randy Hudson" <someone@xxxxxxxxxx> wrote in message
> news:9lpnol$g2q$1@xxxxxxxxxxxxxxxx
> > I've seen the phrase "Team Streams" appear in Eclipse.  If this is what I
> > think it is, then it is a Server-side concept that might satisfy your
> needs.
> > The original Team Stream in a previous OTI product could contain several
> > projects.  Resources could be released into such streams for other
> > teammembers even without versioning the containing project or package.  In
> > my current work, there is a "stable" and "future" version of the same set
> of
> > projects/code.
> >
> > Having said this, if you cannot juggle and yo-yo at the same time, you
> > shouldn't work with projects that participate in more than one team
> stream.
> > The alternative is to create a workspace for each "level" of code, and
> > transport code between them by manually doing compares.