Community
Participate
Working Groups
As a developer, I want to run Skalli directly from the IDE. Therefore the target platform and launch configuration need to be extended, so they include a servlet container (i.e. Jetty).
Last week I sat together with Jochen Hiller and we found out that newer Jetty versions luckily support RFC66. Based on what we found out, I pushed a change (793424). Feel free to comment.
I have used this patch to get Skalli running in my development environment. I'va also added documentation how to setup IDE, projects und run Skalli at Contributor Guide http://wiki.eclipse.org/Skalli/Contributor_Guide There are yet some minor issues: - 3rdparty libraries are missing. I have added an extended target definition which is adding the missing bundles. The wiki documents the download locations and target folder to use. - I have changed the launch config, to be named "skalli-jetty.launch" to reflect launch Skalli in Jetty web container. I have changed too the property to be OSGi compliant to "org.osgi.service.http.port=8080". Both files are attached to this bug. @Simon: if appropriate push it down to Git master branch. The Skalli portal is sucessfully starting, but icons are yet missing. Is there a default theme missing within VAADIN?
Created attachment 194075 [details] Enhanced target platform definition
Created attachment 194076 [details] Changed Jetty launch config with modified OSGi service property
As discussed on mailing list, the specific launch config is necessary anymore, when skalli.launch is based on Jetty now. I made the attachment obsolete now. Nevertheless, the OSGi standard property -Dorg.osgi.service.http.port=8080 should be used instead of the Jetty specific property.
Fixed the property to use OSGi standard property. See http://git.eclipse.org/c/skalli/org.eclipse.skalli.git/commit/?id=d191f0b90b9381b4032d21f5b3675b8c32ecab66
