Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 366822 - Commit EGL Dojo Sample to Eclipse CVS
Summary: Commit EGL Dojo Sample to Eclipse CVS
Status: CLOSED DUPLICATE of bug 394302
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: EDT (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-15 10:31 EST by Brian Svihovec CLA
Modified: 2017-02-23 14:20 EST (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Brian Svihovec CLA 2011-12-15 10:31:55 EST 
This will require a CQ.

The project should be added to the samples folder in CVS.
Comment 1 Theresa Ramsey CLA 2012-04-18 16:16:39 EDT 
so the next question is do we make them part of the product (vs separate download) and 'installable' like the samples in RBD?
Comment 2 Brian Svihovec CLA 2012-04-18 16:26:36 EDT 
I do not think we should consider adding these samples to the product until we have a separate EDT Web Developer Tools build.

Since we are making the projects available as zip files on our website for now, even putting this code in EDT CVS is probably a low priority.
Comment 3 Theresa Ramsey CLA 2012-04-19 09:10:33 EDT 
the .7 sample were in the website cvs (since that's how they were made available for download).  We can put the .8 ones there, though the actual download is on the download site (so we can track download numbers). 

Anyway, just trying to make sure people know that they are made available to externals, not just internal for testing.
Comment 4 Matt Heitz CLA 2012-11-14 10:56:02 EST 
I opened bug 394302 to consolidate several issues including this one.

The topic of how users get their hands on the samples is covered by bug 357806.

*** This bug has been marked as a duplicate of bug 394302 ***