Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 353139 - [Intro] Replace use of samples framework with easier to maintain framework
Summary: [Intro] Replace use of samples framework with easier to maintain framework
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: User Assistance (show other bugs)
Version: 3.7   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: platform-ua-inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-26 13:03 EDT by Chris Goldthorpe CLA
Modified: 2019-11-27 07:08 EST (History)
6 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 Chris Goldthorpe CLA 2011-07-26 13:03:46 EDT 
3.7

The Samples page of Intro contains a small number of samples which are not well maintained, are unsigned and rely on the PDE Samples framework. If we could replace the samples mechanism with a page which used P2 it would be easier to keep the samples up to date.
Comment 1 Dani Megert CLA 2013-01-21 04:38:55 EST 

*** This bug has been marked as a duplicate of bug 279813 ***
Comment 2 Dani Megert CLA 2013-01-21 11:34:27 EST 
.
Comment 3 Curtis Windatt CLA 2013-01-21 11:49:54 EST 
Note that the PDE samples framework does use p2 to install.  However, the process is still convoluted and has much room for improvement.  I updated the title to reflect this.
Comment 4 Lars Vogel CLA 2019-11-27 07:08:35 EST 
This bug hasn't had any activity in quite some time. Maybe the problem got
resolved, was a duplicate of something else, or became less pressing for some
reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it.
The information can be, for example, that the problem still occurs, that you
still want the feature, that more information is needed, or that the bug is
(for whatever reason) no longer relevant.

If the bug is still relevant, please remove the stalebug whiteboard tag.