Community
Participate
Working Groups
While trying to build stand alone, I notice xpath2 processor tests have dependency on org.eclipse.wst.xml.core;bundle-version="[1.1.0,2.0.0)", org.eclipse.wst.sse.core;bundle-version="[1.1.0,2.0.0)", Which in turn have lots of other dependencies: Bundle org.eclipse.wst.xml.core: Missing required plug-in org.eclipse.wst.common.uriresolver_[1.1.301,1.2.0). Optional plug-in org.eclipse.jem.util_[2.0.200,3.0.0) is not available. Optional plug-in org.eclipse.wst.validation_[1.2.100,1.3.0) is not available. Optional plug-in org.eclipse.wst.common.emf_[1.1.300,1.3.0) is not available. Optional plug-in org.eclipse.emf.ecore.xmi_[2.4.0,3.0.0) is not available. Optional plug-in org.eclipse.wst.common.emfworkbench.integration_[1.1.300,1.3.0) is not available. Missing required plug-in org.eclipse.wst.common.core_[1.1.201,1.3.0). Bundle org.eclipse.wst.sse.core: Missing required plug-in org.eclipse.wst.common.uriresolver_[1.1.301,1.2.0). Missing required plug-in org.eclipse.emf.common_[2.4.0,3.0.0). Optional plug-in org.eclipse.wst.validation_[1.2.100,2.0.0) is not available. All this for one test class: TestWTPDOMXPath2.java It seems to me, since xpath2 processor does not normally depend on these two wst plugins, it would be better if the test bundle did not either. While it could be made to work, perhaps that one test class could be moved to XSL tests? XSL in general, I think, does have naturally dependencies on xml.core and sse.core?
Yes, there a dependencies because there are WTP DOM specific tests included with in the test suite. We probably could refactor the test out into it's own plugin, but it is there to test interoperability of the WTP DOM and PsychoPath. (In reply to comment #0) > While trying to build stand alone, I notice xpath2 processor tests have > dependency on > > org.eclipse.wst.xml.core;bundle-version="[1.1.0,2.0.0)", > org.eclipse.wst.sse.core;bundle-version="[1.1.0,2.0.0)", > > Which in turn have lots of other dependencies: > > Bundle org.eclipse.wst.xml.core: > Missing required plug-in > org.eclipse.wst.common.uriresolver_[1.1.301,1.2.0). > Optional plug-in org.eclipse.jem.util_[2.0.200,3.0.0) is not available. > Optional plug-in org.eclipse.wst.validation_[1.2.100,1.3.0) is not > available. > Optional plug-in org.eclipse.wst.common.emf_[1.1.300,1.3.0) is not > available. > Optional plug-in org.eclipse.emf.ecore.xmi_[2.4.0,3.0.0) is not > available. > Optional plug-in > org.eclipse.wst.common.emfworkbench.integration_[1.1.300,1.3.0) is not > available. > Missing required plug-in org.eclipse.wst.common.core_[1.1.201,1.3.0). > Bundle org.eclipse.wst.sse.core: > Missing required plug-in > org.eclipse.wst.common.uriresolver_[1.1.301,1.2.0). > Missing required plug-in org.eclipse.emf.common_[2.4.0,3.0.0). > Optional plug-in org.eclipse.wst.validation_[1.2.100,2.0.0) is not > available. > > > All this for one test class: TestWTPDOMXPath2.java > > It seems to me, since xpath2 processor does not normally depend on these two > wst plugins, it would be better if the test bundle did not either. While it > could be made to work, perhaps that one test class could be moved to XSL tests? > XSL in general, I think, does have naturally dependencies on xml.core and > sse.core?
This was fixed as part of bug 340934. Separate test bundle was introduced for this purpose.
