Community
Participate
Working Groups
Refactor TPTP project sets for component reorganization. See http://wiki.eclipse.org/4.5_Component_Reorganization for more details. This should be done later in the release cycle. Also, the project sets should be reviewed for non-existent/empty plug-ins in CVS and reviewed by the project leads for correctness.
I don't agree that the project sets should/can be done later. These should be kept in sync with the builds and releases. The whole point is to enable quick productivity, and being out of sync simply makes them unreliable. The alternative is to stop providing them, since the committers on the project seem to not want to keep them current. Although that answers seems totally opposite to the idea of community support.
(In reply to comment #1) > I don't agree that the project sets should/can be done later. These should be > kept in sync with the builds and releases. The whole point is to enable quick > productivity, and being out of sync simply makes them unreliable. Agreed. The intent was wait until all of the component reorganization is complete and not necessarily until the end of the release cycle.
The project set files have been updated for i5. http://www.eclipse.org/tptp/home/documents/resources/projectSets/TPTPProjectSet450.psf http://www.eclipse.org/tptp/home/documents/resources/projectSets/TPTPProjectSet450-pserver.psf Re-targeting to i7 to update post API freeze.
*** Bug 224569 has been marked as a duplicate of this bug. ***
Project sets are now built during the build. Refer to the links for the psf to see the latest revisions.
Requires defect https://bugs.eclipse.org/bugs/show_bug.cgi?id=224569.
Verified at http://www.eclipse.org/tptp/home/documents/extenders.php. Closing.
