Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Ganymede Policies on Package Visibility"
(New page: We currently do not have any Ganymede policy on how to handle the package visibility in bundles. Some projects, such as the Eclipse Top Level Project, have a [[Export-Package | strict "all...) |
|||
| Line 4: | Line 4: | ||
This page is to start the discussion and documentation on how to handle this in Ganymede. If everyone agrees, and it seems useful and constructive, we can "move" this information to the main [[Ganymede]] page | This page is to start the discussion and documentation on how to handle this in Ganymede. If everyone agrees, and it seems useful and constructive, we can "move" this information to the main [[Ganymede]] page | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | [[Category:Ganymede]] | ||
Revision as of 04:55, 8 September 2007
We currently do not have any Ganymede policy on how to handle the package visibility in bundles. Some projects, such as the Eclipse Top Level Project, have a strict "all visible" policy and others such as WTP, have followed that, but are considering changing their policy to allow some packages to be hidden.
At a minimum, for Ganymede, we should require all Ganymede participants at least document their policy. I am not sure we could or should have any completely consistent cross-project policy, since a projects committers and clients are all different and they have different requirements and motivations to do one or the other.
This page is to start the discussion and documentation on how to handle this in Ganymede. If everyone agrees, and it seems useful and constructive, we can "move" this information to the main Ganymede page