Fixes
Change-Id: I09165602161c6c9144726eca368f09f6b618743c
diff --git a/examples/simpleclassmodelingrefactoring/index.html b/examples/simpleclassmodelingrefactoring/index.html
index 8140fe9..e88013d 100644
--- a/examples/simpleclassmodelingrefactoring/index.html
+++ b/examples/simpleclassmodelingrefactoring/index.html
@@ -22,7 +22,7 @@
<h2>Metamodel</h2>
<p>
-<a href="simpleclassmodelingrefactoring/classModel.png"><image src="simpleclassmodelingrefactoring/classModel.png" align="center" width="639" /></a>
+<a href="examples/simpleclassmodelingrefactoring/classModel.png"><image src="examples/simpleclassmodelingrefactoring/classModel.png" align="center" width="639" /></a>
<br>
The metamodel is defined in the file <i>ClassModel.ecore</i>. We used
the Ecore Tools to draw a diagram (depicted above).
@@ -39,7 +39,7 @@
<h2>Refactoring Transformation Rules</h2>
<p>
-<a href="simpleclassmodelingrefactoring/refactoringRules.png"><image src="simpleclassmodelingrefactoring/refactoringRules.png" align="right" width="400" /></a>
+<a href="examples/simpleclassmodelingrefactoring/refactoringRules.png"><image src="examples/simpleclassmodelingrefactoring/refactoringRules.png" align="right" width="400" /></a>
Since refactoring is a specific kind of model transformation, refactorings for EMF-based
models can be specified in Henshin and then integrated into a model refactoring framework
such as <a href="http://www.eclipse.org/emf-refactor/">EMF Refactor</a>.
@@ -54,7 +54,7 @@
<h2>Scenario</h2>
<p>
-<a href="simpleclassmodelingrefactoring/scenario.png"><image src="simpleclassmodelingrefactoring/scenario.png" align="right" width="300" /></a>
+<a href="examples/simpleclassmodelingrefactoring/scenario.png"><image src="examples/simpleclassmodelingrefactoring/scenario.png" align="right" width="300" /></a>
Lets assume that a software developer wants to know which refactoring rules need to be
applied in order to restructure a class model. More specifically, we refer to the class
model shown in the following figure representing an early analysis model in the development
@@ -97,14 +97,14 @@
→ Calculate Critical Pairs).
</p>
-<a href="simpleclassmodelingrefactoring/callCPAWizard.png"><image src="simpleclassmodelingrefactoring/callCPAWizard.png" align="center" width="300" /></a>
+<a href="examples/simpleclassmodelingrefactoring/callCPAWizard.png"><image src="examples/simpleclassmodelingrefactoring/callCPAWizard.png" align="center" width="300" /></a>
<p>
This brings up a wizard to specify the rule set to be analyzed and the kind of critical
pairs that shall be analyzed.
</p>
-<a href="simpleclassmodelingrefactoring/CPAWizard.png"><image src="simpleclassmodelingrefactoring/CPAWizard.png" align="center" width="300" /></a>
+<a href="examples/simpleclassmodelingrefactoring/CPAWizard.png"><image src="examples/simpleclassmodelingrefactoring/CPAWizard.png" align="center" width="300" /></a>
<p>
After the CPA, a dedicated results view provides an overview on all conflicts and dependencies
@@ -112,7 +112,7 @@
as rule pairs. For each pair, a set of conflicts (dependencies) is listed named by their kinds.
</p>
-<a href="simpleclassmodelingrefactoring/CPAResultView.png"><image src="simpleclassmodelingrefactoring/CPAResultView.png" align="right" width="300" /></a>
+<a href="examples/simpleclassmodelingrefactoring/CPAResultView.png"><image src="examples/simpleclassmodelingrefactoring/CPAResultView.png" align="right" width="300" /></a>
<p>
Here, three conflics are found. The conflicts of the first and the third rule pair in the results
@@ -127,7 +127,7 @@
conflict (dependency). The following figure shows a minimal model in the tree-based Ecore instance editor.
</p>
-<a href="simpleclassmodelingrefactoring/CPAEditor.png"><image src="simpleclassmodelingrefactoring/CPAEditor.png" align="center" width="600" /></a>
+<a href="examples/simpleclassmodelingrefactoring/CPAEditor.png"><image src="examples/simpleclassmodelingrefactoring/CPAEditor.png" align="center" width="600" /></a>
<p>
The minimal model (see center of the figure above) is related to the first <i>produce-forbid-conflict</i>
@@ -147,7 +147,7 @@
corresponding API.
</p>
-<a href="simpleclassmodelingrefactoring/ICriticalPairAnalysis.png"><image src="simpleclassmodelingrefactoring/ICriticalPairAnalysis.png" align="center" width="471" /></a>
+<a href="examples/simpleclassmodelingrefactoring/ICriticalPairAnalysis.png"><image src="examples/simpleclassmodelingrefactoring/ICriticalPairAnalysis.png" align="center" width="471" /></a>
<p>
The initialization can be done with one or two rule sets containing Henshin
@@ -173,7 +173,7 @@
<p>The following figure shows the results API.</p>
-<a href="simpleclassmodelingrefactoring/CPAResultAPI.png"><image src="simpleclassmodelingrefactoring/CPAResultAPI.png" align="center" width="400" /></a>
+<a href="examples/simpleclassmodelingrefactoring/CPAResultAPI.png"><image src="examples/simpleclassmodelingrefactoring/CPAResultAPI.png" align="center" width="400" /></a>
<p>
All conflicts (dependencies) are within the container <i>CPAResult</i>. Conflict
@@ -192,4 +192,4 @@
strictly separated.
</p>
-<a href="simpleclassmodelingrefactoring/CPKinds.png"><image src="simpleclassmodelingrefactoring/CPKinds.png" align="center" width="429" /></a>
+<a href="examples/simpleclassmodelingrefactoring/CPKinds.png"><image src="examples/simpleclassmodelingrefactoring/CPKinds.png" align="center" width="429" /></a>
diff --git a/examples/universitycourses/index.html b/examples/universitycourses/index.html
index b34c532..e544e88 100644
--- a/examples/universitycourses/index.html
+++ b/examples/universitycourses/index.html
@@ -16,7 +16,7 @@
<h2>Metamodel</h2>
<p>
-<a href="examples/universitycourses/universityCourses-model.png"><img src="examples/universityCourses/universityCourses-model.png" align="right" width="250" /></a>
+<a href="examples/universitycourses/universityCourses-model.png"><img src="examples/universitycourses/universityCourses-model.png" align="right" width="250" /></a>
The metamodel describes a <i>University</i> which contains <i>Courses</i> and <i>Persons</i>..
A <i>Course</i> has a name, belongs to a university and can be of two types.
An <i>OfferedCourse</i> represents a course which can be staged in the next lecture period.
@@ -42,7 +42,7 @@
<h2>Henshin Rules and Units</h2>
-<a href="examples/universitycourses/universityCourses-planAllCoursesOrFail.png"><img src="examples/universityCourses/universityCourses-planAllCoursesOrFail.png" /></a>
+<a href="examples/universitycourses/universityCourses-planAllCoursesOrFail.png"><img src="examples/universitycourses/universityCourses-planAllCoursesOrFail.png" /></a>
<p>
The <i>SequentialUnit</i> <b>planAllCoursesOrFail</b> (<i>strict=true</i>, <i>rollback=false</i>) executes the rule <i>existsUnscheduledInterestingCourse</i> first.
@@ -61,7 +61,7 @@
</p>
<p>
-<a href="examples/universitycourses/universityCourses-incrementHour.png"><img src="examples/universityCourses/universityCourses-incrementHour.png" /></a>
+<a href="examples/universitycourses/universityCourses-incrementHour.png"><img src="examples/universitycourses/universityCourses-incrementHour.png" /></a>
</p>
<p>
@@ -73,7 +73,7 @@
</p>
<p>
-<a href="examples/universitycourses/universityCourses-planOneCourse.png"><img src="examples/universityCourses/universityCourses-planOneCourse.png" align="right" width="350" /></a>
+<a href="examples/universitycourses/universityCourses-planOneCourse.png"><img src="examples/universitycourses/universityCourses-planOneCourse.png" align="right" width="350" /></a>
<b>planOneCourse</b> is a <i>SequentialUnit</i> with the flags <i>strict=true</i> and <i>rollback=true</i>.
First, it schedules a course which prevents time conflicts for lecturers by fixing the time using the rule <i>scheduleOfferedCourse</i>.
@@ -101,7 +101,7 @@
</p>
<p>
-<a href="examples/universitycourses/universityCourses-manageCourses.png"><img src="examples/universityCourses/universityCourses-manageCourses.png" align="right" /></a>
+<a href="examples/universitycourses/universityCourses-manageCourses.png"><img src="examples/universitycourses/universityCourses-manageCourses.png" align="right" /></a>
The starting point for the application of this example is the <i>IteratedUnit</i> <b>manageCourses</b> with the flag <i>strict</i> set to false.
The <i>in</i>-parameter <i>startHour</i> in this and all other units sets the earliest hour to which courses can be scheduled.
This unit tries to apply its sub-unit <i>planOrCleanup</i> two times which shall ensure that each of the two sub-units of <i>planOrCleanup</i> is applied at least once.
