Community
Participate
Working Groups
In updating the map file for TPTP, I found only the sub-projects are listed. Can the top level tptp project be used instead of tptp.platform, tptp.monitoring, tptp.performance, and tptp.test? The reason for this would be to make it easier for end users to know which package to select, as well, we only maintain one map file for the whole project. Currently, I have been putting the map file only in the tptp.platform project listed on babel. I am not sure how our project will display in the downloads section as we are not currently listed due to http://bugs.eclipse.org/266250. The projects are seen as listed in the about this project webpages: http://www.eclipse.org/projects/project_summary.php?projectid=tptp http://www.eclipse.org/projects/project_summary.php?projectid=tptp.platform http://www.eclipse.org/projects/project_summary.php?projectid=tptp.performance http://www.eclipse.org/projects/project_summary.php?projectid=tptp.monitoring http://www.eclipse.org/projects/project_summary.php?projectid=tptp.test Thanks!
Denis, you may have some insight about this. Could you take a look?
Joel, I believe we are currently using tptp.platform. Babel uses the Bugzilla Products and cannot map to the category itself. I have marked the other tptp projects as inactive, leaving only tptp.platform (which has all your map files). Is this sufficient for closing this?
Hi Denis, Yes, we are currently using tptp.platform. I found a category TPTP in Bugzilla unless we're looking at different places. The main concern here being other projects map appropriately for the download zips, while TPTP's isn't as clear for a new user. For example, BabelLanguagePack-webtools-en_AA_3.4.0.v20090315043401.zip would be for all of webtools, BabelLanguagePack-modeling.gmf-en_AA_3.4.0.v20090315043401.zip would be the GMF subproject of Modeling. While BabelLanguagePack-tptp.platform-en_AA_3.4.0.v20090315043401.zip may be thought of as the Platform sub-project of TPTP (http://www.eclipse.org/tptp/home/downloads/) and users would be looking for our other three sub-projects.
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. -- The automated Eclipse Genie.
