Community
Participate
Working Groups
All doc plugins for the JST components are currently contained in a 2 features called org.eclipse.jst.enterprise_userdoc.feature and org.eclipse.jst.server_userdoc.feature. This does not match the way the WST doc plugins are dealt with, and doesn't provide adoptors with the option of selecting which doc plugins they want to include in their products. I suggest the following features be created to allow adopters to select which docs they want to pull into their products (you can change the feature names to more closely match the development features if you want - I just wanted to give some suggestions of logical groupings): org.eclipse.jst.ejb_userdoc.feature id="org.eclipse.jst.ejb.doc.user" org.eclipse.jst.enterprise_userdoc.feature (feature present - contains too many plugins) id="org.eclipse.jst.j2ee.doc.user" org.eclipse.jst.server_userdoc.feature (already present) id="org.eclipse.jst.server.ui.doc.user" org.eclipse.jst.ws_userdoc.feature id="org.eclipse.jst.ws.axis.ui.doc.user" id="org.eclipse.jst.ws.consumption.ui.doc.user" id="org.eclipse.jst.ws.doc.user"
David, are you still working on JST features in 1.5?
yes, will get back to it in week or two.
*** Bug 111984 has been marked as a duplicate of this bug. ***
Hi David...any chance we can still get this into 1.5?
yep ... I started to say "in a week or two" but now see I've used that one already :) Ping me every couple of days and remind me how important this is to you. Thanks,
David, RC2 is rapidly approaching. Any update?
David, ping, RC2 has passed. Any update?
As David hasn't had a chance to update this defect I'm removing the 1.5 target. This fix does not look appropriate for 1.5 at this point.
*bump* David, can we take another look at this for WTP 2.0? I'd still like to see the feature breakdown for the doc plugins match the dev ones more closely.
Yes, Kate ... let's see if we can do this for 2.0.
Hmm, how about 3.0.
we'll try again next year!
Looks like we are going to put this off for yet another release ... so marking as "future" to be explicit about that.