Community
Participate
Working Groups
org.eclipse.jst.validation.sample Is there a reason this test "plugin" is not a standard OSGi bundle? As it is, it is an "old fashioned" plugin, which has to be converted to a bundle before runtime. This started to show up during the "layout tests" such as http://build.eclipse.org/webtools/committers/wtp-R3.2.0-S/20100524020321/S-3.2.0RC3-20100524020321/testResults/layoutErrors.html While we could certainly make it stop showing up there, by listing it as an exception, I think the best thing to do is to make it a proper bundle, unless there is a reason not to. It is likely to cause more concrete issues in the future (e.g. on Eclipse 4.0?) if it depends on that special plugin-to-bundle conversion that is, what 4 releases ago?
While this plugin may live under the umbrella of the Java EE Tools JUnits, this is actually part of Validation. I am routing it over to their component, however a jeetools committer will need to commit the final change (if any).
Created attachment 169894 [details] Create the MANIFEST.MF
Wini, First, with such a change, we must increase the plugin version id- at least 1.1.1. Second, it would be nice if we separated the strings- there should be a plugin.properties. Select the plugin and do PDE Tools->Externalize Strings...
I ran the org.eclipse.jst.validation.test.junit.AutomatedValidationBVT test with Wini's current changes, and it still passes.
Created attachment 170001 [details] New patch to add the plugin.properties and increase the version id.
Thanks Carl. I have modified the patch with the plugin.properties and updated version id.
I approve of this patch. I also reran the test case.
This ancient, but still used, test bundle was never converted to an OSGi bundle. As such, it is impossible to fix the layout errors that Eclipse wants fixed for the Helios release. There is no workaround. I ran the org.eclipse.jst.validation.test.junit.AutomatedValidationBVT locally. This is a simple conversion of the org.eclipse.jst.validation.sample plugin over to OSGi format. I have reviewed the changes. The only possible risk associated with this fix would be that the org.eclipse.jst.validation.test.junit.AutomatedValidationBVT would fail.
Committed to HEAD for WTP 3.2 RC3
I'm all for this change. Couldn't effect function, and could revert if something odd happened to tests. It also appears this bundle is "unpacked" as a directory. Could it be left jarred up? Fine if not (or, fine if done later) but if you think its feasible, please update the appropriate test feature. Thanks for attending to this little detail.
Closing.
