Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 343826

Summary:

Run skalli locally from the IDE

Product:

z_Archived

Reporter:

Simon Kaufmann <simon>

Component:

Skalli

Assignee:

Project Inbox <skalli.core-inbox>

Status:

RESOLVED FIXED

QA Contact:

Severity:

normal

Priority:

CC:

jochen.hiller

Version:

unspecified

Target Milestone:

---

Hardware:

OS:

Windows 7

Whiteboard:

Attachments:

Description	Flags
Enhanced target platform definition	none
Changed Jetty launch config with modified OSGi service property	none

Description Simon Kaufmann

2011-04-26 07:48:00 EDT

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).

Comment 1 Simon Kaufmann

2011-04-26 08:01:34 EDT

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.

Comment 2 Jochen Hiller

2011-04-26 12:42:53 EDT

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?

Comment 3 Jochen Hiller

2011-04-26 12:44:00 EDT

Created attachment 194075 [details]
Enhanced target platform definition

Comment 4 Jochen Hiller

2011-04-26 12:44:37 EDT

Created attachment 194076 [details]
Changed Jetty launch config with modified OSGi service property

Comment 5 Jochen Hiller

2011-05-12 14:32:27 EDT

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.

Comment 6 Jochen Hiller

2011-05-13 02:00:30 EDT

Fixed the property to use OSGi standard property.

See http://git.eclipse.org/c/skalli/org.eclipse.skalli.git/commit/?id=d191f0b90b9381b4032d21f5b3675b8c32ecab66