Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 358083

Summary:	Consider to remove team project set
Product:	[RT] RAP	Reporter:	Ralf Sternberg <rsternberg>
Component:	Website	Assignee:	Project Inbox <rap-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	elias, ruediger.herrmann
Version:	1.5
Target Milestone:	1.5 RC1
Hardware:	PC
OS:	Linux
Whiteboard:

Description Ralf Sternberg

2011-09-19 06:29:09 EDT

Since we now have public nightly builds, we should not encourage users to consume RAP from CVS anymore. Updating a target from to the latest nightly build is easier and safer than including source code into the IDE. If someone really needs the source from CVS they know what they're doing and will find the projects to checkout.

For a team project set, it's hard to decide which bundles it should contain. Someone who builds lightweight applications, does not need workbench, forms, etc. Moreover, team project sets induce an additional maintenance effort to keep them up-to-date.

I'd therefore suggest to get rid of the rap.psf file from http://eclipse.org/rap/source/
We can keep the demo project set to make it easy to check out the code of an example RAP application.

Comment 1 Rüdiger Herrmann

2011-09-30 04:52:40 EDT

Take a look at bug 351379 when this is resolved.

Comment 2 Ralf Sternberg

2011-09-30 10:18:41 EDT

PDE provides a feature to import source from SCM: Import As… > Project from a Repository
The RAP bundles support this feature already.

I think that's a better way of supporting source code import into the IDE and it comes at no maintenance cost. When we remove the psf from http://eclipse.org/rap/source/, we should describe this method there.

Comment 3 Elias Volanakis

2012-02-01 20:00:25 EST

In my correspondence with our users, I have to explain how to get the code frequently (usually for things that we don't ship with the 'default' RAP, i.e. test suites and incubator components). 

So having current, working instructions, is definitely important. The actual mechanism for provisioning (i.e. .psf, import from CVS, import from GIT) is less important.

Also: What is the timeline for putting RAP into git (since CVS is retiring) ? That could be a good trigger for updating the instructions.

Comment 4 Ralf Sternberg

2012-02-02 06:20:49 EST

Thanks for your input. I'd like to do the git migration before the release, but there's no schedule yet. See bug 331780.

Comment 5 Ralf Sternberg

2012-05-16 06:02:07 EDT

The existing team project set files had become obsolete by the migration to git and have been removed from the website.
Since we have nightly builds, source bundles, github mirrors coming soon, I consider team project sets not as important as they were years before.