Community
Participate
Working Groups
Build ID: 3.4 M6 Steps To Reproduce: Due to refactoring of CommonFrameworksPlugin, the clients utilizing java source folder preferences are broken
Created attachment 96286 [details] Proposed patch
Created attachment 96648 [details] Updated patch
I approve
Needed to refactor these prefs.. Currently they are broken.
Comitted to HEAD with one modification- removed the addition of Eclipse-LazyStart: true since the MANIFEST.MF already has Bundle-ActivationPolicy: lazy (Eclipse-LazyStart is the deprecated way to do it, the Bundle-ActivationPolicy is its replacement, and they both do the same thing, so no sense having both)
somehow my approval got removed (Carl :) ... so, I'm re-adding now, just so the summary pages make sense.
Guys, I hate being a pain about this, but this change introduced new public API during RC1 which really isn't necessary and we certainly don't want to be on the hook to support it. On a related note, I see that the fact we don't have a "jst.common" bugzilla component created some confusion here (and explains why I am only seeing this bug now). We should probably do something about that. Either we should create a new "jst.common" component or better yet, rename "wst.common" to just "common".
Created attachment 100341 [details] Additional patch (for jst.common.project.facet.core)
Created attachment 100342 [details] Additional patch (for jst.j2ee)
Created attachment 100343 [details] Additional patch (for jst.common.project.facet.core) Forgot to remove the x-friends declaration.
Created attachment 100345 [details] Additional Patch Sorry for all the noise. Ignore previous attachments. Here is a consolidated patch.
Please review "Additional Patch". This patch moves the introduced FacetCorePlugin class into an internal package and updates the reference from jst.j2ee plugin. This is basically a minimum change that is necessary to hide the introduced api, but more thought will need to go into how these product flags are handled in a future release. It seems like we have at least three different ways of doing the same thing. Maybe it's time to think about retiring some of these.
Approved.
Fix released.
verified, closing