Community
Participate
Working Groups
I think right now most people don't realize we have WAR product deployment tooling. We should modify the RAP tooling feature (org.eclipse.rap.tooling) so that it includes the WAR product feature (org.eclipse.libra.warproducts.feature), so that people get both.
As an experiment, can we have this for RAP 1.5 M5 ?
The main problem is the version (<=1.0) and the fact that it is still in incubation: org.eclipse.libra.warproducts.feature_0.1.1.201203140341.jar According to their release plan (http://www.eclipse.org/projects/project.php?id=webtools.libra) they will release a 0.2 version together with Juno. From a legal perspective it would be required to mark the RAP Tooling feature with 'includes incubating components' and I am not so sure that this is what everyone wants.
I understand the wish to make the war products easier to find for RAP developers. However, I don't think that including the libra.warproducts feature in the rap.tooling feature is the right solution. The RAP Tools do not depend on Libra warproducts, and technically, there is no reason to create this dependency. There may be better ways of making the warproducts available for RAP developers, such as including them in the EPP package for RAP and RCP developers once the libra project has graduated. This would be the subject of another bug against EPP.
After discussion with Holger and Markus, we agreed not to add this dependency to the RAP Tools feature. Please open a bug against EPP if you think that the warproducts should be included in the RCP/RAP package.