[KIEKER-630] Create separate Eclipse projects for kieker and its examples

[rju]

JIRA Issue: KIEKER-630 Create separate Eclipse projects for kieker and its examples Original Reporter: Christian Wulf

---

Reason: to reduce the contents in the package explorer of Eclipse. The examples are not used when fixing bugs and implementing new features for Kieker.

Checklist:

[rju]

author rju -- Mon, 17 Mar 2014 14:59:01 +0100

I second this idea. We should have a
- kieker base package and project for kieker-common and kieker-monitoring
- kieker-analysis package for the analysis framework
- trace-analysis package
- kdb package
- web-gui package
- package for Perl instrumentation
- package for C instrumantation

For people who want to evaluate Kieker we could also provide such package containing
- kieker-common, kieker-monitoring, kieker-analysis and trace-analysis

[rju]

author Jan Waller -- Mon, 17 Mar 2014 15:01:15 +0100

1. There are already separate Eclipse projects (at least for examples)...
2. They are all included in the one project, so that automatic refactoring changes everything (including currently closed projects)

3. Personally, I hat this trend to masses of projects in eclipse, that actually are a single one.

[rju]

author nils-christian -- Mon, 24 Mar 2014 16:45:23 +0100

We already had different archive files for common, monitoring, ... some years ago. We merged them into one archive to improve the usability.

Furthermore I agree with Jan. Splitting Kieker into multiple projects would simply complicate the development (with respect to maintenance and refactoring). I do not see any benefit in splitting Kieker or seperate the examples from Kieker.

[rju]

author rju -- Mon, 24 Mar 2014 17:12:14 +0100

From a demo user point of view it is helpful to have everything in one bundle. And of course to run the analysis the records must be present. The same applies to monitoring. However, for both it is only necessary to have the records in the same bundle (a.k.a jar file). This does not mean that we have to split the Eclipse project. Even though we could as API changes in the record structure which can be automatically propagated are very rare. But it is not necessary to split up the project.

In future we will have several smaller bundles for Kieker to support different programming languages.

However, the present dependencies for our tools are:
trace-anaylsis => kieker-analysis framework, kieker.common.records
kdb => kieker.monitoring, kieker.common.records

Therefore, to have separate bundles for different use cases, we would have to split up the tools section as well. As the present download is not that big at the moment we could keep all Java parts in one bundle. Even though it looks mixed up.

[rju]

author Björn Weißenfels -- Mon, 28 Apr 2014 13:28:59 +0200

Christian Wulf: Is this still topical?

Also: We now have KIEKER-1416 Open for the module idea.