You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The nightly build of the TPD editor can meanwhile convert Maven
coordinates from TPD to .target. Therefore we can simplify our target
platform definition to use a single file again (instead of using nested
target files, with one for Eclipse plugins and one for Maven libraries).
There is no functional change, no version upgrades, really just
simplifying how to write the target file.
// If the following part has errors and no syntax highlighting, then please use Help>About>Installation>Installed Software>Target Platform DSL>Uninstall.
33
+
// After restarting please install the current version from the URL in line 1.
*[Target Platform DSL](https://github.com/eclipse-cbi/targetplatform-dsl), must be from the nightly update site
12
12
13
13
14
14
## How to use the target platform
@@ -29,55 +29,8 @@ which will lead to runtime errors for end users that are still on an old Eclipse
29
29
30
30
Target files are hard to maintain manually.
31
31
Therefore we use a custom DSL to maintain most of the target platform, and to derive the `.target` file.
32
-
However, that DSL based generation is not possible for the part of the target platform that shall include Maven coordinates.
33
-
That's why the target platform is split over multiple files.
34
-
The root target platform includes 2 child target platforms:
35
-
* one containing all the Maven artifacts
36
-
* one containing normal Eclipse plugins
37
-
38
-
The following is a PlantUML diagram of that structure:
39
-
40
-
```
41
-
@startuml
42
-
package "net.sf.eclipsecs.target.target" {
43
-
[net.sf.eclipsecs.partial.maven.target] as maven
44
-
[net.sf.eclipsecs.partial.eclipse.target] as eclipse
45
-
}
46
-
47
-
note bottom of maven
48
-
dependencies like in pom.xml
49
-
from Maven Central
50
-
end note
51
-
note bottom of eclipse
52
-
features/plugins from
53
-
from eclipse.org update sites
54
-
end note
55
-
@enduml
56
-
```
57
-
58
-
While that structure may look confusing at first glance, it simplifies the actual editing a lot,
59
-
because you either only edit Maven coordinates or entries in the `.tpd` file.
60
-
61
-
### Eclipse plugins
62
-
63
-
Edit the `net.sf.eclipsecs.partial.eclipse.tpd` file.
64
-
After saving use the context menu of the .tpd file to create a new version of the `net.sf.eclipsecs.partial.eclipse.target` file.
65
-
66
-
### Maven libraries
67
-
68
-
Meanwhile Eclipse PDE and Tycho can also use Maven libraries directly in the target platform
69
-
(by automatically wrapping them into a generated OSGi bundle).
70
-
Those libraries are contained in `net.sf.eclipsecs.partial.maven.target`.
71
-
You can open that with a text editor and edit the Maven coordinates like in a `pom.xml`.
72
-
73
-
### Eclipse license entry
74
-
75
-
Unfortunately there is a [bug in Eclipse PDE when resolving target files](https://github.com/eclipse-pde/eclipse.pde/issues/558) that contain only nested target files.
76
-
The issue leads to logging a (harmless) exception in the console when launching Eclipse-CS from the IDE.
77
-
This is only relevant for Eclipse-CS developers, not Eclipse-CS users.
78
-
The workaround is to simply add another (not nested) target location in the first position.
79
-
Therefore this target contains a reference to the Eclipse license feature in the target platform.
80
-
That license feature is not used anywhere.
32
+
Edit the `net.sf.eclipsecs.target.tpd` file.
33
+
After saving use the context menu of the .tpd file to create a new version of the `net.sf.eclipsecs.target.target` file.
0 commit comments