-
Notifications
You must be signed in to change notification settings - Fork 0
/
README.txt
108 lines (61 loc) · 2.79 KB
/
README.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
Local build
===========
1. Adjust maven properties, target configuration and Eclipse repository location
in
./pom.xml
pepper-target/pepper-target.target
2. Run test to build OSGI bundles
mvn -P osgi package
3. Install OSGI bundles into your local Maven repository
mvn -P osgi install
4. Run test to build Eclipse bundles
mvn -P eclipse package
5. Install Eclipse bundles into your local Maven repository and add bundles to
the target P2 repository
mvn -P eclipse install
Frequently asked questions
==========================
How can I adjust the version of the Pepper core modules?
--------------------------------------------------------
Change maven properties
pepper.core.version
pepper.core.version.osgi
in ./pom.xml. If you are building against a snapshot version use
pepper.core.version x.y.z-SNAPSHOT
pepper.core.version.osgi x.y.z.SNAPSHOT
As of Pepper version 1.1.6 timestamped versions are not possible because the
entry bundle-version in the manifest files of the Pepper bundles is not
timestamped.
How can I add a special Pepper import/export module?
----------------------------------------------------
1. Add the module as Maven dependency to the dependency management section of
./pom.xml
2. Add the module as Maven dependency to the dependency section of
pepper-feature-modules/pom.xml
pepper-repository/pom.xml
3. Add the module as plugin to the Eclipse feature definition file
pepper-feature-modules/feature.xml
How can I add the source of a special Pepper import/export module?
------------------------------------------------------------------
1. Make sure the module is contained in the Pepper Modules Feature (see above)
2. Define a new Maven property containing the version of the Pepper module in
./pom.xml
and a corresponding OSGI version property; cf. the Maven properties
pepper.module.paula.version
pepper.module.paula.version.osgi
3. Add a new Maven module which builds the source of the Pepper module as OSGI
bundle; cf.
pepper-plugin-module-paula-source/pom.xml
4. Include this Maven module in the <modules> section of the profile OSGI in
./pom.xml
5. Add the new Maven module as Maven dependency to the dependency section of
pepper-feature-modules-source/pom.xml
pepper-repository/pom.xml
Use the group id, the artifact id and the version of the new Maven module,
not those of the original pepper module.
6. Add the module as plugin to the Eclipse feature definition file
pepper-feature-modules-source/feature.xml
How can I add a bundle required from the target platform?
---------------------------------------------------------
Add this bundle to pepper-target/pepper-target.target either as feature or
individual bundle.