Community
Participate
Working Groups
This bundle also contains some documentation that would better fit into a bundle called org.eclipse.pde.doc.isv. I think we should make a clear separation of both documentations like JDT and Platform. extension points defined by PDE should go to doc.isv. This requires to create a new bundle.
Request PMC approval as this requires a new bundle. The current PDE doc contains documentation that should really be inside a pde doc isv bundle. This makes the PDE doc inconsistent with other documentations like JDT or Platform docs.
I'd like to hear Darin and Chris' input into this before splitting it. While PDE does have some API and extension points, I'm not positive that there is a need to have a separate help document.
I think the split will be beneficial in the long run. We want to add documentation for API tooling ant tasks (APIs). Moving forward there will only be more of this.
This fell off the radar for 3.5. Marking for 3.6.
If the doc is split up, we will no longer need the bootclasspath entry in the build.xml of the user doc plug-in. See bug 115401.
It is late in the cycle and there us no driving reason for us to make the split. Removing the target milestone.
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.
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.
