Community
Participate
Working Groups
In a JAXB faceted project if you attempt content assist in an XML file you will see the JPA proposals category. We need to do something similar to the fix in bug 345213 for the org.eclipse.wst.sse.ui.completionProposal extension point. Then the org.eclipse.jpt.jpa.ui.xml.jpaProposalCategory extension in the org.eclipse.jpt.jpa.ui.plugin.xml would add the enablement element.
This causes a side-effect of activating the jpa ui and core plugins when using content assist in an xml file in any type of project. This will result in the same issues as https://bugs.eclipse.org/bugs/show_bug.cgi?id=386171. For 3.2.1 we might want to turn off the force plugin activation on the java completion proposal computer if we can't get the underlying problem fixed in time.
Created attachment 225397 [details] proposed patch against 3.2 maintenance This patch against 3.2 mainteance simply changes the xml content assist extensions to not activate the org.eclipse.jpt.jpa.core plug-in. We are doing this to further fix bug 386171.
I entered bug 397786 to fully fix this problem in 3.3. For maintenance we just want to prevent the jpa plug-in from loading unecessarily.
Patch pushed to 3.2 maintenance.