Community
Participate
Working Groups
Right now the navigator content priority for this contribution is "higher", which makes it hard for us (JPA) to place our content, which we feel should be lower than core module content (EJB, Web deployment descriptors, etc.) but higher than resources and (probably) also this content. If we set our content priority to be "higher", it keeps us lower than core module content, but also consistently lower than enhanced java content for the web. If we set our priority to be "highest", it puts us higher than core module content at times. Java content (jdt) by itself is at priority "high", which I think should be appropriate for this content, because it seems to replace that content. Are there reasons for setting this priority higher?
Dimitar, please take care of this. Paul, I hope this is not urgent and M7 is a good target for the fix?
No, that's absolutely soon enough. This is a minor change and will allow us to respond soon enough. Thanks.
Created attachment 96562 [details] severity is reduced to high. here is a fix, but unfortunately it brings some implications, the build folder is placed right after Deployment Descriptor and in this way the web project becomes the only one that looks in this way. See before and after screenshots. Here again I ran into the Common Navigator framework and I was not able to move the build folder to the bottom as it is in all other project. @Chuck: please see the screenshots. I am not really confident in this fix.
Created attachment 96564 [details] Before screenshot
Created attachment 96565 [details] After severity change.
I'm ok with this, but JDT UI contribution should not be "high". We really need to get them to reduce it to "normal" at least so we have more options.
bug in JDT created. https://bugs.eclipse.org/bugs/show_bug.cgi?id=228022
We want to hold on applying the patch until bug 228022 is clarified. Moving to RC1.
Paul/Dimitar/Chuck/Kaloyan: Why is this bug marked as minor, but at the same time you are pushing on Platform UI to fix bug 228022 for 3.4 after our API freeze?
(In reply to comment #9) > Paul/Dimitar/Chuck/Kaloyan: Why is this bug marked as minor, but at the same > time you are pushing on Platform UI to fix bug 228022 for 3.4 after our API > freeze? > See my comment in bug 228022: https://bugs.eclipse.org/bugs/show_bug.cgi?id=228022#c25
Bug 228022 has been re-targeted to Eclipse SDK 3.5. So, I guess we have to re-target this one for WTP 4.0.
Hi Paul, the fix in the platform should solve your problem and does not require a fix for us. If this works for you please close the bug entry.
I'm not sure how the fix in platform resolves this issue for us. Seems they implemented something for *action providers* but I don't see what they did for navigator content. Our JPA content still falls below the web "build" folder for some reason, even at priority "higher".
From the platform team there is a new option available, which should enable you to achieve the ordering you like. The new property is "appearsBefore" option in the content provider and it allows control over the ordering of the content providers. https://bugs.eclipse.org/bugs/show_bug.cgi?id=228022#c46 Can you confirm that this is enough for you?
Finally made it onto my plate to check this out. This does work to allow us to place ourselves in the tree properly. But now I ask - why is JAX-WS using "highest"? Shouldn't that also be using "higher" and "appearsBefore" to correctly place it?
Hi Paul, I will close this bug report. You can open a separate bug for the JAX-WS. Is this ok with you?
Sure.
228022 enables more refined positioning of the nodes.
We have a problem with this behavior. It appears that "appearsBefore" causes a problem if the referenced content provider is not in the workspace. (see bug 349108) We do not want to depend on the plugin declaring that content type. I would prefer that the reference to that content provider would not *require* that dependency. Should this be logged in a separate bug?
Sorry, meant to put this on the parent bug.
