Hi Markus, The rwt.jstest bundle contains the JavaScript tests for the web client. Dropdown (and I think clientscripting as well) hooks its JavaScript tests into the rwt.jstest suite as a shortcut, but in the long run, I think it should have a stand-alone JS test suite (or be merged with the core).
In its current form, rwt.jstest is not meant to be used by third party bundles. Therefore I'd prefer to keep it out of the SDK for the moment. In the future, we may provide a JavaScript rap fixture as part of the SDK. Since the JavaScript tests are not executed by maven anyway, the dependency to rwt.jstest is not relevant for the build. We can either make it optional or split the bundle into dropdown.test and dropdown.jstest. Regards, Ralf On Sun, May 12, 2013 at 11:31 AM, Markus Knauer <[email protected]>wrote: > Hi all, > > when I integrated the new RAP Incubator dropdown component into the build > I ran into the problem of a dependency from > org.eclipse.rap.addons.dropdown.test to org.eclipse.rap.rwt.jstest. > Unfortunately we've never integrated the jstest bundle in one of our builds > so far. > > In order to get a working build, I decided on Friday to ignore the > dropdown.test bundle and skip it for the time being. > > Today I integrated the missing jstest bundle into the Runtime build and > added the bundle to the SDK feature, but I am not entirely sure if this is > the right place. The next step will be to enable the tests in the dropdown > widget again. > > Are there any concerns to add the jstest bundle to the RAP Runtime SDK > feature? > > Thanks, > Markus > > _______________________________________________ > rap-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/rap-dev > >
_______________________________________________ rap-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/rap-dev
