Re: [skalli-dev] How many launches to you want to have?
Just to add some comments on configuration of the storage folder: There is a mechanism to get that storage folder path from a property file that has to be in the class path root. Doing so we can customize the storage folder by adding a bundle fragment including that property file. For us it's much easier to implement a separate bundle (fragment) that is deployed together with the skalli bundles instead of touching particular files that came with skalli sources (this is something we call a 'build hack'). In general, as you mentioned your 'telekom customization', it is obvious that we have a 'sap customization' (e.g. the bundle fragment including the property file mentioned above). I think this could be the way to go for all customization that needs to be adapted by different organizations.
The only thing that is missing at the moment is a description how to write such a bundle fragment, I will adapt the contributor guide asap.
From: Jochen Hiller <jo.hiller@xxxxxxxxxxxxxx<mailto:jo.hiller@xxxxxxxxxxxxxx>>
Reply-To: Skalli project developer mailing list <skalli-dev@xxxxxxxxxxx<mailto:skalli-dev@xxxxxxxxxxx>>
Date: Thu, 12 May 2011 20:39:20 +0200
To: Skalli project developer mailing list <skalli-dev@xxxxxxxxxxx<mailto:skalli-dev@xxxxxxxxxxx>>
Subject: Re: [skalli-dev] How many launches to you want to have?
On Thu, May 12, 2011 at 5:29 PM, Varwig, Britta <britta.varwig@xxxxxxx<mailto:britta.varwig@xxxxxxx>> wrote:
on http://wiki.eclipse.org/Skalli/Contributor_Guide#Run_Skalli_from_IDE a patch with an skalli-jetty.launch is available (has not reached origin/master by now).
Additionally a skalli.lauch is available in project org.eclipse.skalli.target.
What was the reason to have both?
added my comment to https://bugs.eclipse.org/bugs/show_bug.cgi?id=343826
One launch config is fine, only property has to be fixed to OSGi standard. Reopened the bug.
Additionally I would like to provide a workdir with some testdata. (some example projects and users fitting to the jetty-users)
Benefit for Skalli beginners: they fast can get a feeling of a working and filled skalli.
Thats a good idea.
I would like to have a suitable launch file for that as well, or can I “reuse” the current available one and just add the testdata to the current workdir?
For a quick startup, it is an good idea to have a non-empty storage to play around with, especially for simple demoing purposes. I would reuse the o.e.s.target/workdir as default directory.
For other needs, developers can adapt or clone the launch config for their needs (like I am doing for my Telekom customization).