Community
Participate
Working Groups
Hi, I just went through the steps for the war export. I would really like to see the org.eclipse.rap.demo.feature project to be part of the supplied team-project-sets in the help page. It is currently *not* and that adds some extra annoying steps to the procedure: - hmm, where do I get this org.eclipse.rap.demo.feature, ... rap CVS ... - ok, need to configure CVS access first, where was that wiki page again... - ok, now navigate the CVS tree to find the project... I think it would be a big improvement if this feature was already part of the .psfs given on the help page. The process is already quite complicated as is. Kind regards, Elias.
Now that the new WAR product tooling is part of Indigo, I think we should promote this as the standard way of creating WAR files. If no one objects I'd close this bug.
Hi Ralf, regardless of the tooling - I still think it makes sense to put the rap.demo.feature into the .psf (after all the demo plugin is in there). What do you think?
Do you think this feature is still useful? I think the sole purpose of org.eclipse.rap.demo.feature has always been the creation of WAR files. What the ConfigIniCreator and the PDE build config in this project did, can now be done much better by the WAR products. Therefore I wonder if we should keep (and maintain) this project at all.
I think that the org.eclipse.rap.demo.feature with it's ConfigIniCreator is just a hack and should not be part of our psf. I also think that the psf should only contain things that will be delivered with our build and the demo feature is not part of our build.
(In reply to comment #4) Completely agree with Holger.
Since 1.3.2 still contains the help that refers to this feature, I'd suggest that we keep it as it is for now and move it to obsolete later, say by the end of 2011.
Moved the org.eclipse.rap.demo.feature to the obsolete folder in CVS. The change affects all branches.