summaryrefslogtreecommitdiffstats
path: root/features
diff options
context:
space:
mode:
Diffstat (limited to 'features')
-rw-r--r--features/org.yocto.bc.headless.build/.project11
-rw-r--r--features/org.yocto.bc.headless.build/build.properties262
-rw-r--r--features/org.yocto.bc.headless.build/customTargets.xml212
-rw-r--r--features/org.yocto.bc/.project17
-rw-r--r--features/org.yocto.bc/build.properties3
-rw-r--r--features/org.yocto.bc/feature.properties163
-rw-r--r--features/org.yocto.bc/feature.xml42
-rw-r--r--features/org.yocto.bc/license.html107
-rw-r--r--features/org.yocto.doc.headless.build/.project11
-rw-r--r--features/org.yocto.doc.headless.build/build.properties262
-rw-r--r--features/org.yocto.doc.headless.build/customTargets.xml212
-rw-r--r--features/org.yocto.doc/.project17
-rw-r--r--features/org.yocto.doc/build.properties3
-rw-r--r--features/org.yocto.doc/feature.properties163
-rw-r--r--features/org.yocto.doc/feature.xml35
-rw-r--r--features/org.yocto.doc/license.html107
-rw-r--r--features/org.yocto.sdk.headless.build/.project11
-rw-r--r--features/org.yocto.sdk.headless.build/build.properties262
-rw-r--r--features/org.yocto.sdk.headless.build/customTargets.xml212
-rw-r--r--features/org.yocto.sdk.site/.project17
-rw-r--r--features/org.yocto.sdk.site/category.xml18
-rw-r--r--features/org.yocto.sdk.site/index.html60
-rw-r--r--features/org.yocto.sdk.site/site.xml18
-rw-r--r--features/org.yocto.sdk.site/web/site.css12
-rw-r--r--features/org.yocto.sdk.site/web/site.xsl214
-rw-r--r--features/org.yocto.sdk/.project17
-rw-r--r--features/org.yocto.sdk/build.properties6
-rw-r--r--features/org.yocto.sdk/feature.properties163
-rw-r--r--features/org.yocto.sdk/feature.xml109
-rw-r--r--features/org.yocto.sdk/license.html107
-rw-r--r--features/org.yocto.sdk/sourceTemplateFeature/feature.properties163
-rw-r--r--features/org.yocto.sdk/sourceTemplateFeature/license.html107
-rw-r--r--features/org.yocto.sdk/sourceTemplatePlugin/license.html107
-rw-r--r--features/org.yocto.sdk/sourceTemplatePlugin/plugin.properties163
34 files changed, 3393 insertions, 0 deletions
diff --git a/features/org.yocto.bc.headless.build/.project b/features/org.yocto.bc.headless.build/.project
new file mode 100644
index 0000000..672fcda
--- /dev/null
+++ b/features/org.yocto.bc.headless.build/.project
@@ -0,0 +1,11 @@
1<?xml version="1.0" encoding="UTF-8"?>
2<projectDescription>
3 <name>org.yocto.bc.headless.build</name>
4 <comment></comment>
5 <projects>
6 </projects>
7 <buildSpec>
8 </buildSpec>
9 <natures>
10 </natures>
11</projectDescription>
diff --git a/features/org.yocto.bc.headless.build/build.properties b/features/org.yocto.bc.headless.build/build.properties
new file mode 100644
index 0000000..9d9a9cc
--- /dev/null
+++ b/features/org.yocto.bc.headless.build/build.properties
@@ -0,0 +1,262 @@
1###############################################################################
2# Copyright (c) 2003, 2009 IBM Corporation and others.
3# All rights reserved. This program and the accompanying materials
4# are made available under the terms of the Eclipse Public License v1.0
5# which accompanies this distribution, and is available at
6# http://www.eclipse.org/legal/epl-v10.html
7#
8# Contributors:
9# IBM Corporation - initial API and implementation
10###############################################################################
11#####################
12# Parameters describing how and where to execute the build.
13# Typical users need only update the following properties:
14# baseLocation - where things you are building against are installed
15# bootclasspath - The base jars to compile against (typicaly rt.jar)
16# configs - the list of {os, ws, arch} configurations to build.
17#
18# Of course any of the settings here can be overridden by spec'ing
19# them on the command line (e.g., -DbaseLocation=d:/eclipse
20
21#The type of the top level element we are building, generally "feature"
22topLevelElementType = feature
23#The id of the top level element we are building
24topLevelElementId = org.yocto.bc
25
26############# PRODUCT/PACKAGING CONTROL #############
27product=/plugin or feature id/path/to/.product
28runPackager=true
29
30#Set the name of the archive that will result from the product build.
31#archiveNamePrefix=
32
33# The prefix that will be used in the generated archive.
34archivePrefix=eclipse
35
36# The location underwhich all of the build output will be collected.
37collectingFolder=${archivePrefix}
38
39# The list of {os, ws, arch} configurations to build. This
40# value is a '&' separated list of ',' separate triples. For example,
41# configs=win32,win32,x86 & linux,motif,x86
42# By default the value is *,*,*
43configs = *, *, *
44#configs=win32, win32, x86 & \
45# win32,win32,x86_64 & \
46# win32,win32,wpf & \
47# linux, gtk, ppc & \
48# linux, gtk, x86 & \
49# linux, gtk, x86_64 & \
50# linux, motif, x86 & \
51# solaris, motif, sparc & \
52# solaris, gtk, sparc & \
53# aix, motif, ppc & \
54# hpux, motif, ia64_32 & \
55# macosx, carbon, ppc & \
56# macosx, carbon, x86 & \
57# macosx, cocoa, ppc & \
58# macosx, cocoa, x86 & \
59# macosx, cocoa, x86_64
60
61# By default PDE creates one archive (result) per entry listed in the configs property.
62# Setting this value to true will cause PDE to only create one output containing all
63# artifacts for all the platforms listed in the configs property.
64# To control the output format for the group, add a "group, group, group - <format>" entry to the
65# archivesFormat.
66#groupConfigurations=true
67
68#The format of the archive. By default a zip is created using antZip.
69#The list can only contain the configuration for which the desired format is different than zip.
70#archivesFormat=win32, win32, x86 - antZip& \
71# linux, gtk, ppc - antZip &\
72# linux, gtk, x86 - antZip& \
73# linux, gtk, x86_64 - antZip& \
74# linux, motif, x86 - antZip& \
75# solaris, motif, sparc - antZip& \
76# solaris, gtk, sparc - antZip& \
77# aix, motif, ppc - antZip& \
78# hpux, motif, PA_RISC - antZip& \
79# macosx, carbon, ppc - antZip
80
81#Allow cycles involving at most one bundle that needs to be compiled with the rest being binary bundles.
82allowBinaryCycles = true
83
84#Sort bundles depenedencies across all features instead of just within a given feature.
85#flattenDependencies = true
86
87#Parallel compilation, requires flattenedDependencies=true
88#parallelCompilation=true
89#parallelThreadCount=
90#parallelThreadsPerProcessor=
91
92#Set to true if you want the output to be ready for an update jar (no site.xml generated)
93outputUpdateJars = true
94
95#Set to true for Jnlp generation
96#codebase should be a URL that will be used as the root of all relative URLs in the output.
97#generateJnlp=false
98#jnlp.codebase=<codebase url>
99#jnlp.j2se=<j2se version>
100#jnlp.locale=<a locale>
101#jnlp.generateOfflineAllowed=true or false generate <offlineAllowed/> attribute in the generated features
102#jnlp.configs=${configs} #uncomment to filter the content of the generated jnlp files based on the configuration being built
103
104#Set to true if you want to sign jars
105#signJars=false
106#sign.alias=<alias>
107#sign.keystore=<keystore location>
108#sign.storepass=<keystore password>
109#sign.keypass=<key password>
110
111#Arguments to send to the zip executable
112zipargs=
113
114#Arguments to send to the tar executable
115tarargs=
116
117#Control the creation of a file containing the version included in each configuration - on by default
118#generateVersionsLists=false
119
120############## BUILD NAMING CONTROL ################
121# The directory into which the build elements are fetched and where
122# the build takes place.
123#buildDirectory=
124
125# Type of build. Used in naming the build output. Typically this value is
126# one of I, N, M, S, ...
127buildType=I
128
129# ID of the build. Used in naming the build output.
130buildId=TestBuild
131
132# Label for the build. Used in naming the build output
133buildLabel=${buildType}.${buildId}
134
135# Timestamp for the build. Used in naming the build output
136timestamp=007
137
138#The value to be used for the qualifier of a plugin or feature when you want to override the value computed by pde.
139#The value will only be applied to plugin or features indicating build.properties, qualifier = context
140#forceContextQualifier=<the value for the qualifier>
141
142#Enable / disable the generation of a suffix for the features that use .qualifier.
143#The generated suffix is computed according to the content of the feature
144#generateFeatureVersionSuffix=true
145
146############# BASE CONTROL #############
147# Settings for the base Eclipse components and Java class libraries
148# against which you are building.
149# Base location for anything the build needs to compile against. For example,
150# in most RCP app or a plug-in, the baseLocation should be the location of a previously
151# installed Eclipse against which the application or plug-in code will be compiled and the RCP delta pack.
152
153#base=<path/to/parent/of/eclipse>
154#baseLocation=${base}/eclipse
155
156#Folder containing repositories whose content is needed to compile against
157#repoBaseLocation=${base}/repos
158#Folder where the content of the repositories from ${repoBaseLocation} will be made available as a form suitable to be compiled against
159#transformedRepoLocation=${base}/transformedRepos
160
161#Os/Ws/Arch/nl of the eclipse specified by baseLocation
162#baseos=win32
163#basews=win32
164#basearch=x86
165
166#this property indicates whether you want the set of plug-ins and features to be considered during the build to be limited to the ones reachable from the features / plugins being built
167filteredDependencyCheck=false
168
169#this property indicates whether the resolution should be done in development mode (i.e. ignore multiple bundles with singletons)
170resolution.devMode=false
171
172#pluginPath is a list of locations in which to find plugins and features. This list is separated by the platform file separator (; or :)
173#a location is one of:
174#- the location of the jar or folder that is the plugin or feature : /path/to/foo.jar or /path/to/foo
175#- a directory that contains a /plugins or /features subdirectory
176#- the location of a feature.xml, or for 2.1 style plugins, the plugin.xml or fragment.xml
177#pluginPath=
178
179skipBase=true
180eclipseURL=<url for eclipse download site>
181eclipseBuildId=<Id of Eclipse build to get>
182eclipseBaseURL=${eclipseURL}/eclipse-platform-${eclipseBuildId}-win32.zip
183
184
185############# MAP FILE CONTROL ################
186# This section defines CVS tags to use when fetching the map files from the repository.
187# If you want to fetch the map file from repository / location, change the getMapFiles target in the customTargets.xml
188
189skipMaps=true
190mapsRepo=:pserver:anonymous@example.com/path/to/repo
191mapsRoot=path/to/maps
192mapsCheckoutTag=HEAD
193
194#tagMaps=true
195mapsTagTag=v${buildId}
196
197
198############ REPOSITORY CONTROL ###############
199# This section defines properties parameterizing the repositories where plugins, fragments
200# bundles and features are being obtained from.
201
202# The tags to use when fetching elements to build.
203# By default thebuilder will use whatever is in the maps.
204# This value takes the form of a comma separated list of repository identifier (like used in the map files) and the
205# overriding value
206# For example fetchTag=CVS=HEAD, SVN=v20050101
207# fetchTag=HEAD
208skipFetch=true
209
210
211############# JAVA COMPILER OPTIONS ##############
212# The location of the Java jars to compile against. Typically the rt.jar for your JDK/JRE
213#bootclasspath=${java.home}/lib/rt.jar
214
215# specific JRE locations to compile against. These values are used to compile bundles specifying a
216# Bundle-RequiredExecutionEnvironment. Uncomment and set values for environments that you support
217#CDC-1.0/Foundation-1.0= /path/to/rt.jar
218#CDC-1.1/Foundation-1.1=
219#OSGi/Minimum-1.0=
220#OSGi/Minimum-1.1=
221#JRE-1.1=
222#J2SE-1.2=
223#J2SE-1.3=
224#J2SE-1.4=
225#J2SE-1.5=
226#JavaSE-1.6=
227#PersonalJava-1.1=
228#PersonalJava-1.2=
229#CDC-1.0/PersonalBasis-1.0=
230#CDC-1.0/PersonalJava-1.0=
231#CDC-1.1/PersonalBasis-1.1=
232#CDC-1.1/PersonalJava-1.1=
233
234# Specify the output format of the compiler log when eclipse jdt is used
235logExtension=.log
236
237# Whether or not to include debug info in the output jars
238javacDebugInfo=false
239
240# Whether or not to fail the build if there are compiler errors
241javacFailOnError=true
242
243# Enable or disable verbose mode of the compiler
244javacVerbose=true
245
246# Extra arguments for the compiler. These are specific to the java compiler being used.
247#compilerArg=
248
249# Default value for the version of the source code. This value is used when compiling plug-ins that do not set the Bundle-RequiredExecutionEnvironment or set javacSource in build.properties
250javacSource=1.6
251
252# Default value for the version of the byte code targeted. This value is used when compiling plug-ins that do not set the Bundle-RequiredExecutionEnvironment or set javacTarget in build.properties.
253javacTarget=1.6
254
255#individualSourceBundles=true
256
257#p2.gathering=true
258p2.compress=true
259#p2.category.site=file:${buildDirectory}/site.xml
260p2.category.definition=file:${buildDirectory}/category.xml
261p2.metadata.repo.name=Yocto Project Update Site
262p2.artifact.repo.name=Yocto Project Update Site
diff --git a/features/org.yocto.bc.headless.build/customTargets.xml b/features/org.yocto.bc.headless.build/customTargets.xml
new file mode 100644
index 0000000..b6d7ed7
--- /dev/null
+++ b/features/org.yocto.bc.headless.build/customTargets.xml
@@ -0,0 +1,212 @@
1<project name="Build specific targets and properties" default="noDefault">
2
3 <!-- ===================================================================== -->
4 <!-- Run a given ${target} on all elements being built -->
5 <!-- Add on <ant> task for each top level element being built. -->
6 <!-- ===================================================================== -->
7 <available property="allElementsFile" file="${builder}/allElements.xml" value="${builder}/allElements.xml"/>
8 <property name="allElementsFile" location="${eclipse.pdebuild.templates}/headless-build/allElements.xml"/>
9
10 <import file="${allElementsFile}" />
11 <target name="allElements">
12 <antcall target="allElementsDelegator" />
13 </target>
14
15 <!-- ===================================================================== -->
16 <!-- ===================================================================== -->
17 <target name="getBaseComponents" depends="checkLocalBase" unless="skipBase">
18 <get src="${eclipseBaseURL}" dest="${buildDirectory}/../temp-base.zip" />
19 <unzip dest="${base}" overwrite="true" src="${buildDirectory}/../temp-base.zip" />
20 </target>
21
22 <target name="checkLocalBase">
23 <available file="${base}" property="skipBase" />
24 </target>
25
26 <!-- ===================================================================== -->
27 <!-- Check out map files from correct repository -->
28 <!-- Replace values for mapsCheckoutTag as desired. -->
29 <!-- ===================================================================== -->
30 <target name="getMapFiles" depends="checkLocalMaps" unless="skipMaps">
31 <property name="mapsCheckoutTag" value="HEAD" />
32 <cvs cvsRoot="${mapsRepo}" package="${mapsRoot}" dest="${buildDirectory}/maps" tag="${mapsCheckoutTag}" />
33 </target>
34
35 <target name="checkLocalMaps">
36 <available property="skipMaps" file="${buildDirectory}/maps" />
37 </target>
38
39 <target name="tagMapFiles" if="tagMaps">
40 <cvs dest="${buildDirectory}/maps/${mapsRoot}" command="tag ${mapsTagTag}" />
41 </target>
42
43 <!-- ===================================================================== -->
44
45 <target name="clean" unless="noclean">
46 <antcall target="allElements">
47 <param name="target" value="cleanElement" />
48 </antcall>
49 </target>
50
51 <target name="gatherLogs">
52 <mkdir dir="${buildDirectory}/${buildLabel}/compilelogs" />
53 <antcall target="allElements">
54 <param name="target" value="gatherLogs" />
55 </antcall>
56 <unzip dest="${buildDirectory}/${buildLabel}/compilelogs" overwrite="true">
57 <fileset dir="${buildDirectory}/features">
58 <include name="**/*.log.zip" />
59 </fileset>
60 </unzip>
61 </target>
62
63 <!-- ===================================================================== -->
64 <!-- Steps to do before setup -->
65 <!-- ===================================================================== -->
66 <target name="preSetup">
67 <delete dir="${buildDirectory}/plugins"/>
68 <mkdir dir="${buildDirectory}/plugins"/>
69 <copy todir="${buildDirectory}/plugins" failonerror="true">
70 <fileset dir="${otherSrcDirectory}/plugins"/>
71 </copy>
72 <delete dir="${buildDirectory}/features"/>
73 <copy todir="${buildDirectory}/features" failonerror="true" >
74 <fileset dir="${otherSrcDirectory}/features"/>
75 </copy>
76 <antcall target="prepareForP2" />
77 </target>
78
79 <target name="prepareForP2" if="p2.gathering">
80 <copy file="${otherSrcDirectory}/features/org.yocto.sdk.site/site.xml" todir="${buildDirectory}" />
81 <copy file="${otherSrcDirectory}/features/org.yocto.sdk.site/category.xml" todir="${buildDirectory}" />
82 <xmlproperty file="${otherSrcDirectory}/features/org.yocto.bc/feature.xml" />
83 <replace file="${buildDirectory}/category.xml">
84 <replacefilter token="@bcfeatureVersion@" value="${feature(version)}"/>
85 </replace>
86 </target>
87
88 <!-- ===================================================================== -->
89 <!-- Steps to do after setup but before starting the build proper -->
90 <!-- ===================================================================== -->
91 <target name="postSetup">
92 <antcall target="getBaseComponents" />
93 </target>
94
95 <!-- ===================================================================== -->
96 <!-- Steps to do before fetching the build elements -->
97 <!-- ===================================================================== -->
98 <target name="preFetch">
99 </target>
100
101 <!-- ===================================================================== -->
102 <!-- Steps to do after fetching the build elements -->
103 <!-- ===================================================================== -->
104 <target name="postFetch">
105 </target>
106
107 <!-- ===================================================================== -->
108 <!-- Steps to do before the repositories are being processed -->
109 <!-- ===================================================================== -->
110 <target name="preProcessRepos">
111 </target>
112
113 <!-- ===================================================================== -->
114 <!-- Steps to do after the repositories have been processed -->
115 <!-- ===================================================================== -->
116 <target name="postProcessRepos">
117 </target>
118
119 <!-- ===================================================================== -->
120 <!-- Steps to do before generating the build scripts. -->
121 <!-- ===================================================================== -->
122 <target name="preGenerate">
123 </target>
124
125 <!-- ===================================================================== -->
126 <!-- Steps to do after generating the build scripts. -->
127 <!-- ===================================================================== -->
128 <target name="postGenerate">
129 <antcall target="clean" />
130 </target>
131
132 <!-- ===================================================================== -->
133 <!-- Steps to do before running the build.xmls for the elements being built. -->
134 <!-- ===================================================================== -->
135 <target name="preProcess">
136 </target>
137
138 <!-- ===================================================================== -->
139 <!-- Steps to do after running the build.xmls for the elements being built. -->
140 <!-- ===================================================================== -->
141 <target name="postProcess">
142 </target>
143
144 <!-- ===================================================================== -->
145 <!-- Steps to do before running assemble. -->
146 <!-- ===================================================================== -->
147 <target name="preAssemble">
148 </target>
149
150 <!-- ===================================================================== -->
151 <!-- Steps to do after running assemble. -->
152 <!-- ===================================================================== -->
153 <target name="postAssemble">
154 </target>
155
156 <!-- ===================================================================== -->
157 <!-- Steps to do before running package. -->
158 <!-- ===================================================================== -->
159 <target name="prePackage">
160 </target>
161
162 <!-- ===================================================================== -->
163 <!-- Steps to do after running package. -->
164 <!-- ===================================================================== -->
165 <target name="postPackage">
166 </target>
167
168 <!-- ===================================================================== -->
169 <!-- Steps to do after the build is done. -->
170 <!-- ===================================================================== -->
171 <target name="postBuild">
172 <antcall target="gatherLogs" />
173 <antcall target="updateSiteContent" />
174 </target>
175
176 <target name="updateSiteContent" if="p2.gathering">
177 <property file="${buildDirectory}/finalFeaturesVersions.properties" />
178 <copy file="${otherSrcDirectory}/features/org.yocto.sdk.site/site.xml" todir="${buildDirectory}" />
179 <replace file="${buildDirectory}/site.xml">
180 <replacefilter token="@bcgenVersion@" value="${org.yocto.bc}"/>
181 </replace>
182 <zip destfile="${buildDirectory}/${buildLabel}/org.yocto.bc-${buildId}-group.group.group.zip" update="true">
183 <zipfileset dir="${buildDirectory}">
184 <include name="site.xml"/>
185 </zipfileset>
186 <zipfileset dir="${otherSrcDirectory}/features/org.yocto.sdk.site">
187 <include name="index.html"/>
188 </zipfileset>
189 <zipfileset dir="${otherSrcDirectory}/features/org.yocto.sdk.site/web" prefix="web"/>
190 </zip>
191 </target>
192
193 <!-- ===================================================================== -->
194 <!-- Steps to do to test the build results -->
195 <!-- ===================================================================== -->
196 <target name="test">
197 </target>
198
199 <!-- ===================================================================== -->
200 <!-- Steps to do to publish the build results -->
201 <!-- ===================================================================== -->
202 <target name="publish">
203 </target>
204
205 <!-- ===================================================================== -->
206 <!-- Default target -->
207 <!-- ===================================================================== -->
208 <target name="noDefault">
209 <echo message="You must specify a target when invoking this file" />
210 </target>
211
212</project>
diff --git a/features/org.yocto.bc/.project b/features/org.yocto.bc/.project
new file mode 100644
index 0000000..553c486
--- /dev/null
+++ b/features/org.yocto.bc/.project
@@ -0,0 +1,17 @@
1<?xml version="1.0" encoding="UTF-8"?>
2<projectDescription>
3 <name>org.yocto.bc</name>
4 <comment></comment>
5 <projects>
6 </projects>
7 <buildSpec>
8 <buildCommand>
9 <name>org.eclipse.pde.FeatureBuilder</name>
10 <arguments>
11 </arguments>
12 </buildCommand>
13 </buildSpec>
14 <natures>
15 <nature>org.eclipse.pde.FeatureNature</nature>
16 </natures>
17</projectDescription>
diff --git a/features/org.yocto.bc/build.properties b/features/org.yocto.bc/build.properties
new file mode 100644
index 0000000..52c3cfc
--- /dev/null
+++ b/features/org.yocto.bc/build.properties
@@ -0,0 +1,3 @@
1bin.includes = feature.xml,\
2 license.html,\
3 feature.properties
diff --git a/features/org.yocto.bc/feature.properties b/features/org.yocto.bc/feature.properties
new file mode 100644
index 0000000..71cd52d
--- /dev/null
+++ b/features/org.yocto.bc/feature.properties
@@ -0,0 +1,163 @@
1###############################################################################
2# Copyright (c) 2010 Intel, Inc. and others.
3# All rights reserved. This program and the accompanying materials
4# are made available under the terms of the Eclipse Public License v1.0
5# which accompanies this distribution, and is available at
6# http://www.eclipse.org/legal/epl-v10.html
7#
8# Contributors:
9# Intel - initial implementation
10###############################################################################
11
12# "featureName" property - name of the feature
13featureName=Yocto Project Bitbake Commander Plug-in
14
15# "providerName" property - name of the company that provides the feature
16providerName=yoctoproject.org
17
18# "updateSiteName" property - label for the update site
19updateSiteName=Yocto Project Update Site
20
21# "description" property - description of the feature
22description=\
23Eclipse plug-in for developing bitbake commander project using Yocto Project
24
25# copyright
26copyright=\
27Copyright (c) 2012 Intel, Inc. and others. \
28All rights reserved. This program and the accompanying materials \
29are made available under the terms of the Eclipse Public License v1.0 \
30which accompanies this distribution, and is available at \
31http://www.eclipse.org/legal/epl-v10.html
32################ end of copyright property ####################################
33
34# "licenseURL" property - URL of the "Feature License"
35# do not translate value - just change to point to a locale-specific HTML page
36licenseURL=license.html
37
38# "license" property - text of the "Feature Update License"
39# should be plain text version of license agreement pointed to be "licenseURL"
40license=\
41Eclipse Foundation Software User Agreement\n\
42April 14, 2010\n\
43\n\
44Usage Of Content\n\
45\n\
46THE ECLIPSE FOUNDATION MAKES AVAILABLE SOFTWARE, DOCUMENTATION, INFORMATION AND/OR\n\
47OTHER MATERIALS FOR OPEN SOURCE PROJECTS (COLLECTIVELY "CONTENT").\n\
48USE OF THE CONTENT IS GOVERNED BY THE TERMS AND CONDITIONS OF THIS\n\
49AGREEMENT AND/OR THE TERMS AND CONDITIONS OF LICENSE AGREEMENTS OR\n\
50NOTICES INDICATED OR REFERENCED BELOW. BY USING THE CONTENT, YOU\n\
51AGREE THAT YOUR USE OF THE CONTENT IS GOVERNED BY THIS AGREEMENT\n\
52AND/OR THE TERMS AND CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS\n\
53OR NOTICES INDICATED OR REFERENCED BELOW. IF YOU DO NOT AGREE TO THE\n\
54TERMS AND CONDITIONS OF THIS AGREEMENT AND THE TERMS AND CONDITIONS\n\
55OF ANY APPLICABLE LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED\n\
56BELOW, THEN YOU MAY NOT USE THE CONTENT.\n\
57\n\
58Applicable Licenses\n\
59\n\
60Unless otherwise indicated, all Content made available by the\n\
61Eclipse Foundation is provided to you under the terms and conditions of\n\
62the Eclipse Public License Version 1.0 ("EPL"). A copy of the EPL is\n\
63provided with this Content and is also available at http://www.eclipse.org/legal/epl-v10.html.\n\
64For purposes of the EPL, "Program" will mean the Content.\n\
65\n\
66Content includes, but is not limited to, source code, object code,\n\
67documentation and other files maintained in the Eclipse Foundation source code\n\
68repository ("Repository") in software modules ("Modules") and made available\n\
69as downloadable archives ("Downloads").\n\
70\n\
71 - Content may be structured and packaged into modules to facilitate delivering,\n\
72 extending, and upgrading the Content. Typical modules may include plug-ins ("Plug-ins"),\n\
73 plug-in fragments ("Fragments"), and features ("Features").\n\
74 - Each Plug-in or Fragment may be packaged as a sub-directory or JAR (Java(TM) ARchive)\n\
75 in a directory named "plugins".\n\
76 - A Feature is a bundle of one or more Plug-ins and/or Fragments and associated material.\n\
77 Each Feature may be packaged as a sub-directory in a directory named "features".\n\
78 Within a Feature, files named "feature.xml" may contain a list of the names and version\n\
79 numbers of the Plug-ins and/or Fragments associated with that Feature.\n\
80 - Features may also include other Features ("Included Features"). Within a Feature, files\n\
81 named "feature.xml" may contain a list of the names and version numbers of Included Features.\n\
82\n\
83The terms and conditions governing Plug-ins and Fragments should be\n\
84contained in files named "about.html" ("Abouts"). The terms and\n\
85conditions governing Features and Included Features should be contained\n\
86in files named "license.html" ("Feature Licenses"). Abouts and Feature\n\
87Licenses may be located in any directory of a Download or Module\n\
88including, but not limited to the following locations:\n\
89\n\
90 - The top-level (root) directory\n\
91 - Plug-in and Fragment directories\n\
92 - Inside Plug-ins and Fragments packaged as JARs\n\
93 - Sub-directories of the directory named "src" of certain Plug-ins\n\
94 - Feature directories\n\
95\n\
96Note: if a Feature made available by the Eclipse Foundation is installed using the\n\
97Provisioning Technology (as defined below), you must agree to a license ("Feature \n\
98Update License") during the installation process. If the Feature contains\n\
99Included Features, the Feature Update License should either provide you\n\
100with the terms and conditions governing the Included Features or inform\n\
101you where you can locate them. Feature Update Licenses may be found in\n\
102the "license" property of files named "feature.properties" found within a Feature.\n\
103Such Abouts, Feature Licenses, and Feature Update Licenses contain the\n\
104terms and conditions (or references to such terms and conditions) that\n\
105govern your use of the associated Content in that directory.\n\
106\n\
107THE ABOUTS, FEATURE LICENSES, AND FEATURE UPDATE LICENSES MAY REFER\n\
108TO THE EPL OR OTHER LICENSE AGREEMENTS, NOTICES OR TERMS AND CONDITIONS.\n\
109SOME OF THESE OTHER LICENSE AGREEMENTS MAY INCLUDE (BUT ARE NOT LIMITED TO):\n\
110\n\
111 - Common Public License Version 1.0 (available at http://www.eclipse.org/legal/cpl-v10.html)\n\
112 - Apache Software License 1.1 (available at http://www.apache.org/licenses/LICENSE)\n\
113 - Apache Software License 2.0 (available at http://www.apache.org/licenses/LICENSE-2.0)\n\
114 - Metro Link Public License 1.00 (available at http://www.opengroup.org/openmotif/supporters/metrolink/license.html)\n\
115 - Mozilla Public License Version 1.1 (available at http://www.mozilla.org/MPL/MPL-1.1.html)\n\
116\n\
117IT IS YOUR OBLIGATION TO READ AND ACCEPT ALL SUCH TERMS AND CONDITIONS PRIOR\n\
118TO USE OF THE CONTENT. If no About, Feature License, or Feature Update License\n\
119is provided, please contact the Eclipse Foundation to determine what terms and conditions\n\
120govern that particular Content.\n\
121\n\
122\n\Use of Provisioning Technology\n\
123\n\
124The Eclipse Foundation makes available provisioning software, examples of which include,\n\
125but are not limited to, p2 and the Eclipse Update Manager ("Provisioning Technology") for\n\
126the purpose of allowing users to install software, documentation, information and/or\n\
127other materials (collectively "Installable Software"). This capability is provided with\n\
128the intent of allowing such users to install, extend and update Eclipse-based products.\n\
129Information about packaging Installable Software is available at\n\
130http://eclipse.org/equinox/p2/repository_packaging.html ("Specification").\n\
131\n\
132You may use Provisioning Technology to allow other parties to install Installable Software.\n\
133You shall be responsible for enabling the applicable license agreements relating to the\n\
134Installable Software to be presented to, and accepted by, the users of the Provisioning Technology\n\
135in accordance with the Specification. By using Provisioning Technology in such a manner and\n\
136making it available in accordance with the Specification, you further acknowledge your\n\
137agreement to, and the acquisition of all necessary rights to permit the following:\n\
138\n\
139 1. A series of actions may occur ("Provisioning Process") in which a user may execute\n\
140 the Provisioning Technology on a machine ("Target Machine") with the intent of installing,\n\
141 extending or updating the functionality of an Eclipse-based product.\n\
142 2. During the Provisioning Process, the Provisioning Technology may cause third party\n\
143 Installable Software or a portion thereof to be accessed and copied to the Target Machine.\n\
144 3. Pursuant to the Specification, you will provide to the user the terms and conditions that\n\
145 govern the use of the Installable Software ("Installable Software Agreement") and such\n\
146 Installable Software Agreement shall be accessed from the Target Machine in accordance\n\
147 with the Specification. Such Installable Software Agreement must inform the user of the\n\
148 terms and conditions that govern the Installable Software and must solicit acceptance by\n\
149 the end user in the manner prescribed in such Installable Software Agreement. Upon such\n\
150 indication of agreement by the user, the provisioning Technology will complete installation\n\
151 of the Installable Software.\n\
152\n\
153Cryptography\n\
154\n\
155Content may contain encryption software. The country in which you are\n\
156currently may have restrictions on the import, possession, and use,\n\
157and/or re-export to another country, of encryption software. BEFORE\n\
158using any encryption software, please check the country's laws,\n\
159regulations and policies concerning the import, possession, or use, and\n\
160re-export of encryption software, to see if this is permitted.\n\
161\n\
162Java and all Java-based trademarks are trademarks of Oracle Corporation in the United States, other countries, or both.\n
163########### end of license property ##########################################
diff --git a/features/org.yocto.bc/feature.xml b/features/org.yocto.bc/feature.xml
new file mode 100644
index 0000000..9ce7353
--- /dev/null
+++ b/features/org.yocto.bc/feature.xml
@@ -0,0 +1,42 @@
1<?xml version="1.0" encoding="UTF-8"?>
2<feature
3 id="org.yocto.bc"
4 label="%featureName"
5 version="1.4.0.qualifier"
6 provider-name="%providerName">
7
8 <description>
9 %description
10 </description>
11
12 <copyright>
13 %copyright
14 </copyright>
15
16 <license url="%licenseURL">
17 %license
18 </license>
19
20 <url>
21 <update label="%updateSiteName" url="http://yoctoproject.org/downloads/eclipse-plugin/"/>
22 </url>
23
24 <requires>
25 <import plugin="org.eclipse.ui"/>
26 <import plugin="org.eclipse.core.runtime"/>
27 <import plugin="org.eclipse.core.resources"/>
28 <import plugin="org.eclipse.jface.text"/>
29 <import plugin="org.eclipse.ui.editors"/>
30 <import plugin="org.eclipse.ui.ide"/>
31 <import plugin="org.eclipse.ui.console"/>
32 <import plugin="org.eclipse.core.filesystem"/>
33 </requires>
34
35 <plugin
36 id="org.yocto.bc.ui"
37 download-size="0"
38 install-size="0"
39 version="0.0.0"
40 unpack="false"/>
41
42</feature>
diff --git a/features/org.yocto.bc/license.html b/features/org.yocto.bc/license.html
new file mode 100644
index 0000000..c184ca3
--- /dev/null
+++ b/features/org.yocto.bc/license.html
@@ -0,0 +1,107 @@
1<?xml version="1.0" encoding="ISO-8859-1" ?>
2<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
3<html xmlns="http://www.w3.org/1999/xhtml">
4<head>
5<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
6<title>Eclipse Foundation Software User Agreement</title>
7</head>
8
9<body lang="EN-US">
10<h2>Eclipse Foundation Software User Agreement</h2>
11<p>April 14, 2010</p>
12
13<h3>Usage Of Content</h3>
14
15<p>THE ECLIPSE FOUNDATION MAKES AVAILABLE SOFTWARE, DOCUMENTATION, INFORMATION AND/OR OTHER MATERIALS FOR OPEN SOURCE PROJECTS
16 (COLLECTIVELY &quot;CONTENT&quot;). USE OF THE CONTENT IS GOVERNED BY THE TERMS AND CONDITIONS OF THIS AGREEMENT AND/OR THE TERMS AND
17 CONDITIONS OF LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW. BY USING THE CONTENT, YOU AGREE THAT YOUR USE
18 OF THE CONTENT IS GOVERNED BY THIS AGREEMENT AND/OR THE TERMS AND CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS OR
19 NOTICES INDICATED OR REFERENCED BELOW. IF YOU DO NOT AGREE TO THE TERMS AND CONDITIONS OF THIS AGREEMENT AND THE TERMS AND
20 CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW, THEN YOU MAY NOT USE THE CONTENT.</p>
21
22<h3>Applicable Licenses</h3>
23
24<p>Unless otherwise indicated, all Content made available by the Eclipse Foundation is provided to you under the terms and conditions of the Eclipse Public License Version 1.0
25 (&quot;EPL&quot;). A copy of the EPL is provided with this Content and is also available at <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>.
26 For purposes of the EPL, &quot;Program&quot; will mean the Content.</p>
27
28<p>Content includes, but is not limited to, source code, object code, documentation and other files maintained in the Eclipse Foundation source code
29 repository (&quot;Repository&quot;) in software modules (&quot;Modules&quot;) and made available as downloadable archives (&quot;Downloads&quot;).</p>
30
31<ul>
32 <li>Content may be structured and packaged into modules to facilitate delivering, extending, and upgrading the Content. Typical modules may include plug-ins (&quot;Plug-ins&quot;), plug-in fragments (&quot;Fragments&quot;), and features (&quot;Features&quot;).</li>
33 <li>Each Plug-in or Fragment may be packaged as a sub-directory or JAR (Java&trade; ARchive) in a directory named &quot;plugins&quot;.</li>
34 <li>A Feature is a bundle of one or more Plug-ins and/or Fragments and associated material. Each Feature may be packaged as a sub-directory in a directory named &quot;features&quot;. Within a Feature, files named &quot;feature.xml&quot; may contain a list of the names and version numbers of the Plug-ins
35 and/or Fragments associated with that Feature.</li>
36 <li>Features may also include other Features (&quot;Included Features&quot;). Within a Feature, files named &quot;feature.xml&quot; may contain a list of the names and version numbers of Included Features.</li>
37</ul>
38
39<p>The terms and conditions governing Plug-ins and Fragments should be contained in files named &quot;about.html&quot; (&quot;Abouts&quot;). The terms and conditions governing Features and
40Included Features should be contained in files named &quot;license.html&quot; (&quot;Feature Licenses&quot;). Abouts and Feature Licenses may be located in any directory of a Download or Module
41including, but not limited to the following locations:</p>
42
43<ul>
44 <li>The top-level (root) directory</li>
45 <li>Plug-in and Fragment directories</li>
46 <li>Inside Plug-ins and Fragments packaged as JARs</li>
47 <li>Sub-directories of the directory named &quot;src&quot; of certain Plug-ins</li>
48 <li>Feature directories</li>
49</ul>
50
51<p>Note: if a Feature made available by the Eclipse Foundation is installed using the Provisioning Technology (as defined below), you must agree to a license (&quot;Feature Update License&quot;) during the
52installation process. If the Feature contains Included Features, the Feature Update License should either provide you with the terms and conditions governing the Included Features or
53inform you where you can locate them. Feature Update Licenses may be found in the &quot;license&quot; property of files named &quot;feature.properties&quot; found within a Feature.
54Such Abouts, Feature Licenses, and Feature Update Licenses contain the terms and conditions (or references to such terms and conditions) that govern your use of the associated Content in
55that directory.</p>
56
57<p>THE ABOUTS, FEATURE LICENSES, AND FEATURE UPDATE LICENSES MAY REFER TO THE EPL OR OTHER LICENSE AGREEMENTS, NOTICES OR TERMS AND CONDITIONS. SOME OF THESE
58OTHER LICENSE AGREEMENTS MAY INCLUDE (BUT ARE NOT LIMITED TO):</p>
59
60<ul>
61 <li>Common Public License Version 1.0 (available at <a href="http://www.eclipse.org/legal/cpl-v10.html">http://www.eclipse.org/legal/cpl-v10.html</a>)</li>
62 <li>Apache Software License 1.1 (available at <a href="http://www.apache.org/licenses/LICENSE">http://www.apache.org/licenses/LICENSE</a>)</li>
63 <li>Apache Software License 2.0 (available at <a href="http://www.apache.org/licenses/LICENSE-2.0">http://www.apache.org/licenses/LICENSE-2.0</a>)</li>
64 <li>Metro Link Public License 1.00 (available at <a href="http://www.opengroup.org/openmotif/supporters/metrolink/license.html">http://www.opengroup.org/openmotif/supporters/metrolink/license.html</a>)</li>
65 <li>Mozilla Public License Version 1.1 (available at <a href="http://www.mozilla.org/MPL/MPL-1.1.html">http://www.mozilla.org/MPL/MPL-1.1.html</a>)</li>
66</ul>
67
68<p>IT IS YOUR OBLIGATION TO READ AND ACCEPT ALL SUCH TERMS AND CONDITIONS PRIOR TO USE OF THE CONTENT. If no About, Feature License, or Feature Update License is provided, please
69contact the Eclipse Foundation to determine what terms and conditions govern that particular Content.</p>
70
71
72<h3>Use of Provisioning Technology</h3>
73
74<p>The Eclipse Foundation makes available provisioning software, examples of which include, but are not limited to, p2 and the Eclipse
75 Update Manager (&quot;Provisioning Technology&quot;) for the purpose of allowing users to install software, documentation, information and/or
76 other materials (collectively &quot;Installable Software&quot;). This capability is provided with the intent of allowing such users to
77 install, extend and update Eclipse-based products. Information about packaging Installable Software is available at <a
78 href="http://eclipse.org/equinox/p2/repository_packaging.html">http://eclipse.org/equinox/p2/repository_packaging.html</a>
79 (&quot;Specification&quot;).</p>
80
81<p>You may use Provisioning Technology to allow other parties to install Installable Software. You shall be responsible for enabling the
82 applicable license agreements relating to the Installable Software to be presented to, and accepted by, the users of the Provisioning Technology
83 in accordance with the Specification. By using Provisioning Technology in such a manner and making it available in accordance with the
84 Specification, you further acknowledge your agreement to, and the acquisition of all necessary rights to permit the following:</p>
85
86<ol>
87 <li>A series of actions may occur (&quot;Provisioning Process&quot;) in which a user may execute the Provisioning Technology
88 on a machine (&quot;Target Machine&quot;) with the intent of installing, extending or updating the functionality of an Eclipse-based
89 product.</li>
90 <li>During the Provisioning Process, the Provisioning Technology may cause third party Installable Software or a portion thereof to be
91 accessed and copied to the Target Machine.</li>
92 <li>Pursuant to the Specification, you will provide to the user the terms and conditions that govern the use of the Installable
93 Software (&quot;Installable Software Agreement&quot;) and such Installable Software Agreement shall be accessed from the Target
94 Machine in accordance with the Specification. Such Installable Software Agreement must inform the user of the terms and conditions that govern
95 the Installable Software and must solicit acceptance by the end user in the manner prescribed in such Installable Software Agreement. Upon such
96 indication of agreement by the user, the provisioning Technology will complete installation of the Installable Software.</li>
97</ol>
98
99<h3>Cryptography</h3>
100
101<p>Content may contain encryption software. The country in which you are currently may have restrictions on the import, possession, and use, and/or re-export to
102 another country, of encryption software. BEFORE using any encryption software, please check the country's laws, regulations and policies concerning the import,
103 possession, or use, and re-export of encryption software, to see if this is permitted.</p>
104
105<p><small>Java and all Java-based trademarks are trademarks of Oracle Corporation in the United States, other countries, or both.</small></p>
106</body>
107</html>
diff --git a/features/org.yocto.doc.headless.build/.project b/features/org.yocto.doc.headless.build/.project
new file mode 100644
index 0000000..106c772
--- /dev/null
+++ b/features/org.yocto.doc.headless.build/.project
@@ -0,0 +1,11 @@
1<?xml version="1.0" encoding="UTF-8"?>
2<projectDescription>
3 <name>org.yocto.doc.headless.build</name>
4 <comment></comment>
5 <projects>
6 </projects>
7 <buildSpec>
8 </buildSpec>
9 <natures>
10 </natures>
11</projectDescription>
diff --git a/features/org.yocto.doc.headless.build/build.properties b/features/org.yocto.doc.headless.build/build.properties
new file mode 100644
index 0000000..6a857f8
--- /dev/null
+++ b/features/org.yocto.doc.headless.build/build.properties
@@ -0,0 +1,262 @@
1###############################################################################
2# Copyright (c) 2003, 2009 IBM Corporation and others.
3# All rights reserved. This program and the accompanying materials
4# are made available under the terms of the Eclipse Public License v1.0
5# which accompanies this distribution, and is available at
6# http://www.eclipse.org/legal/epl-v10.html
7#
8# Contributors:
9# IBM Corporation - initial API and implementation
10###############################################################################
11#####################
12# Parameters describing how and where to execute the build.
13# Typical users need only update the following properties:
14# baseLocation - where things you are building against are installed
15# bootclasspath - The base jars to compile against (typicaly rt.jar)
16# configs - the list of {os, ws, arch} configurations to build.
17#
18# Of course any of the settings here can be overridden by spec'ing
19# them on the command line (e.g., -DbaseLocation=d:/eclipse
20
21#The type of the top level element we are building, generally "feature"
22topLevelElementType = feature
23#The id of the top level element we are building
24topLevelElementId = org.yocto.doc
25
26############# PRODUCT/PACKAGING CONTROL #############
27product=/plugin or feature id/path/to/.product
28runPackager=true
29
30#Set the name of the archive that will result from the product build.
31#archiveNamePrefix=
32
33# The prefix that will be used in the generated archive.
34archivePrefix=eclipse
35
36# The location underwhich all of the build output will be collected.
37collectingFolder=${archivePrefix}
38
39# The list of {os, ws, arch} configurations to build. This
40# value is a '&' separated list of ',' separate triples. For example,
41# configs=win32,win32,x86 & linux,motif,x86
42# By default the value is *,*,*
43configs = *, *, *
44#configs=win32, win32, x86 & \
45# win32,win32,x86_64 & \
46# win32,win32,wpf & \
47# linux, gtk, ppc & \
48# linux, gtk, x86 & \
49# linux, gtk, x86_64 & \
50# linux, motif, x86 & \
51# solaris, motif, sparc & \
52# solaris, gtk, sparc & \
53# aix, motif, ppc & \
54# hpux, motif, ia64_32 & \
55# macosx, carbon, ppc & \
56# macosx, carbon, x86 & \
57# macosx, cocoa, ppc & \
58# macosx, cocoa, x86 & \
59# macosx, cocoa, x86_64
60
61# By default PDE creates one archive (result) per entry listed in the configs property.
62# Setting this value to true will cause PDE to only create one output containing all
63# artifacts for all the platforms listed in the configs property.
64# To control the output format for the group, add a "group, group, group - <format>" entry to the
65# archivesFormat.
66#groupConfigurations=true
67
68#The format of the archive. By default a zip is created using antZip.
69#The list can only contain the configuration for which the desired format is different than zip.
70#archivesFormat=win32, win32, x86 - antZip& \
71# linux, gtk, ppc - antZip &\
72# linux, gtk, x86 - antZip& \
73# linux, gtk, x86_64 - antZip& \
74# linux, motif, x86 - antZip& \
75# solaris, motif, sparc - antZip& \
76# solaris, gtk, sparc - antZip& \
77# aix, motif, ppc - antZip& \
78# hpux, motif, PA_RISC - antZip& \
79# macosx, carbon, ppc - antZip
80
81#Allow cycles involving at most one bundle that needs to be compiled with the rest being binary bundles.
82allowBinaryCycles = true
83
84#Sort bundles depenedencies across all features instead of just within a given feature.
85#flattenDependencies = true
86
87#Parallel compilation, requires flattenedDependencies=true
88#parallelCompilation=true
89#parallelThreadCount=
90#parallelThreadsPerProcessor=
91
92#Set to true if you want the output to be ready for an update jar (no site.xml generated)
93outputUpdateJars = true
94
95#Set to true for Jnlp generation
96#codebase should be a URL that will be used as the root of all relative URLs in the output.
97#generateJnlp=false
98#jnlp.codebase=<codebase url>
99#jnlp.j2se=<j2se version>
100#jnlp.locale=<a locale>
101#jnlp.generateOfflineAllowed=true or false generate <offlineAllowed/> attribute in the generated features
102#jnlp.configs=${configs} #uncomment to filter the content of the generated jnlp files based on the configuration being built
103
104#Set to true if you want to sign jars
105#signJars=false
106#sign.alias=<alias>
107#sign.keystore=<keystore location>
108#sign.storepass=<keystore password>
109#sign.keypass=<key password>
110
111#Arguments to send to the zip executable
112zipargs=
113
114#Arguments to send to the tar executable
115tarargs=
116
117#Control the creation of a file containing the version included in each configuration - on by default
118#generateVersionsLists=false
119
120############## BUILD NAMING CONTROL ################
121# The directory into which the build elements are fetched and where
122# the build takes place.
123#buildDirectory=
124
125# Type of build. Used in naming the build output. Typically this value is
126# one of I, N, M, S, ...
127buildType=I
128
129# ID of the build. Used in naming the build output.
130buildId=TestBuild
131
132# Label for the build. Used in naming the build output
133buildLabel=${buildType}.${buildId}
134
135# Timestamp for the build. Used in naming the build output
136timestamp=007
137
138#The value to be used for the qualifier of a plugin or feature when you want to override the value computed by pde.
139#The value will only be applied to plugin or features indicating build.properties, qualifier = context
140#forceContextQualifier=<the value for the qualifier>
141
142#Enable / disable the generation of a suffix for the features that use .qualifier.
143#The generated suffix is computed according to the content of the feature
144#generateFeatureVersionSuffix=true
145
146############# BASE CONTROL #############
147# Settings for the base Eclipse components and Java class libraries
148# against which you are building.
149# Base location for anything the build needs to compile against. For example,
150# in most RCP app or a plug-in, the baseLocation should be the location of a previously
151# installed Eclipse against which the application or plug-in code will be compiled and the RCP delta pack.
152
153#base=<path/to/parent/of/eclipse>
154#baseLocation=${base}/eclipse
155
156#Folder containing repositories whose content is needed to compile against
157#repoBaseLocation=${base}/repos
158#Folder where the content of the repositories from ${repoBaseLocation} will be made available as a form suitable to be compiled against
159#transformedRepoLocation=${base}/transformedRepos
160
161#Os/Ws/Arch/nl of the eclipse specified by baseLocation
162#baseos=win32
163#basews=win32
164#basearch=x86
165
166#this property indicates whether you want the set of plug-ins and features to be considered during the build to be limited to the ones reachable from the features / plugins being built
167filteredDependencyCheck=false
168
169#this property indicates whether the resolution should be done in development mode (i.e. ignore multiple bundles with singletons)
170resolution.devMode=false
171
172#pluginPath is a list of locations in which to find plugins and features. This list is separated by the platform file separator (; or :)
173#a location is one of:
174#- the location of the jar or folder that is the plugin or feature : /path/to/foo.jar or /path/to/foo
175#- a directory that contains a /plugins or /features subdirectory
176#- the location of a feature.xml, or for 2.1 style plugins, the plugin.xml or fragment.xml
177#pluginPath=
178
179skipBase=true
180eclipseURL=<url for eclipse download site>
181eclipseBuildId=<Id of Eclipse build to get>
182eclipseBaseURL=${eclipseURL}/eclipse-platform-${eclipseBuildId}-win32.zip
183
184
185############# MAP FILE CONTROL ################
186# This section defines CVS tags to use when fetching the map files from the repository.
187# If you want to fetch the map file from repository / location, change the getMapFiles target in the customTargets.xml
188
189skipMaps=true
190mapsRepo=:pserver:anonymous@example.com/path/to/repo
191mapsRoot=path/to/maps
192mapsCheckoutTag=HEAD
193
194#tagMaps=true
195mapsTagTag=v${buildId}
196
197
198############ REPOSITORY CONTROL ###############
199# This section defines properties parameterizing the repositories where plugins, fragments
200# bundles and features are being obtained from.
201
202# The tags to use when fetching elements to build.
203# By default thebuilder will use whatever is in the maps.
204# This value takes the form of a comma separated list of repository identifier (like used in the map files) and the
205# overriding value
206# For example fetchTag=CVS=HEAD, SVN=v20050101
207# fetchTag=HEAD
208skipFetch=true
209
210
211############# JAVA COMPILER OPTIONS ##############
212# The location of the Java jars to compile against. Typically the rt.jar for your JDK/JRE
213#bootclasspath=${java.home}/lib/rt.jar
214
215# specific JRE locations to compile against. These values are used to compile bundles specifying a
216# Bundle-RequiredExecutionEnvironment. Uncomment and set values for environments that you support
217#CDC-1.0/Foundation-1.0= /path/to/rt.jar
218#CDC-1.1/Foundation-1.1=
219#OSGi/Minimum-1.0=
220#OSGi/Minimum-1.1=
221#JRE-1.1=
222#J2SE-1.2=
223#J2SE-1.3=
224#J2SE-1.4=
225#J2SE-1.5=
226#JavaSE-1.6=
227#PersonalJava-1.1=
228#PersonalJava-1.2=
229#CDC-1.0/PersonalBasis-1.0=
230#CDC-1.0/PersonalJava-1.0=
231#CDC-1.1/PersonalBasis-1.1=
232#CDC-1.1/PersonalJava-1.1=
233
234# Specify the output format of the compiler log when eclipse jdt is used
235logExtension=.log
236
237# Whether or not to include debug info in the output jars
238javacDebugInfo=false
239
240# Whether or not to fail the build if there are compiler errors
241javacFailOnError=true
242
243# Enable or disable verbose mode of the compiler
244javacVerbose=true
245
246# Extra arguments for the compiler. These are specific to the java compiler being used.
247#compilerArg=
248
249# Default value for the version of the source code. This value is used when compiling plug-ins that do not set the Bundle-RequiredExecutionEnvironment or set javacSource in build.properties
250javacSource=1.6
251
252# Default value for the version of the byte code targeted. This value is used when compiling plug-ins that do not set the Bundle-RequiredExecutionEnvironment or set javacTarget in build.properties.
253javacTarget=1.6
254
255#individualSourceBundles=true
256
257#p2.gathering=true
258p2.compress=true
259#p2.category.site=file:${buildDirectory}/site.xml
260p2.category.definition=file:${buildDirectory}/category.xml
261p2.metadata.repo.name=Yocto Project Update Site
262p2.artifact.repo.name=Yocto Project Update Site
diff --git a/features/org.yocto.doc.headless.build/customTargets.xml b/features/org.yocto.doc.headless.build/customTargets.xml
new file mode 100644
index 0000000..8cb505e
--- /dev/null
+++ b/features/org.yocto.doc.headless.build/customTargets.xml
@@ -0,0 +1,212 @@
1<project name="Build specific targets and properties" default="noDefault">
2
3 <!-- ===================================================================== -->
4 <!-- Run a given ${target} on all elements being built -->
5 <!-- Add on <ant> task for each top level element being built. -->
6 <!-- ===================================================================== -->
7 <available property="allElementsFile" file="${builder}/allElements.xml" value="${builder}/allElements.xml"/>
8 <property name="allElementsFile" location="${eclipse.pdebuild.templates}/headless-build/allElements.xml"/>
9
10 <import file="${allElementsFile}" />
11 <target name="allElements">
12 <antcall target="allElementsDelegator" />
13 </target>
14
15 <!-- ===================================================================== -->
16 <!-- ===================================================================== -->
17 <target name="getBaseComponents" depends="checkLocalBase" unless="skipBase">
18 <get src="${eclipseBaseURL}" dest="${buildDirectory}/../temp-base.zip" />
19 <unzip dest="${base}" overwrite="true" src="${buildDirectory}/../temp-base.zip" />
20 </target>
21
22 <target name="checkLocalBase">
23 <available file="${base}" property="skipBase" />
24 </target>
25
26 <!-- ===================================================================== -->
27 <!-- Check out map files from correct repository -->
28 <!-- Replace values for mapsCheckoutTag as desired. -->
29 <!-- ===================================================================== -->
30 <target name="getMapFiles" depends="checkLocalMaps" unless="skipMaps">
31 <property name="mapsCheckoutTag" value="HEAD" />
32 <cvs cvsRoot="${mapsRepo}" package="${mapsRoot}" dest="${buildDirectory}/maps" tag="${mapsCheckoutTag}" />
33 </target>
34
35 <target name="checkLocalMaps">
36 <available property="skipMaps" file="${buildDirectory}/maps" />
37 </target>
38
39 <target name="tagMapFiles" if="tagMaps">
40 <cvs dest="${buildDirectory}/maps/${mapsRoot}" command="tag ${mapsTagTag}" />
41 </target>
42
43 <!-- ===================================================================== -->
44
45 <target name="clean" unless="noclean">
46 <antcall target="allElements">
47 <param name="target" value="cleanElement" />
48 </antcall>
49 </target>
50
51 <target name="gatherLogs">
52 <mkdir dir="${buildDirectory}/${buildLabel}/compilelogs" />
53 <antcall target="allElements">
54 <param name="target" value="gatherLogs" />
55 </antcall>
56 <unzip dest="${buildDirectory}/${buildLabel}/compilelogs" overwrite="true">
57 <fileset dir="${buildDirectory}/features">
58 <include name="**/*.log.zip" />
59 </fileset>
60 </unzip>
61 </target>
62
63 <!-- ===================================================================== -->
64 <!-- Steps to do before setup -->
65 <!-- ===================================================================== -->
66 <target name="preSetup">
67 <delete dir="${buildDirectory}/plugins"/>
68 <mkdir dir="${buildDirectory}/plugins"/>
69 <copy todir="${buildDirectory}/plugins" failonerror="true">
70 <fileset dir="${otherSrcDirectory}/plugins"/>
71 </copy>
72 <delete dir="${buildDirectory}/features"/>
73 <copy todir="${buildDirectory}/features" failonerror="true" >
74 <fileset dir="${otherSrcDirectory}/features"/>
75 </copy>
76 <antcall target="prepareForP2" />
77 </target>
78
79 <target name="prepareForP2" if="p2.gathering">
80 <copy file="${otherSrcDirectory}/features/org.yocto.sdk.site/site.xml" todir="${buildDirectory}" />
81 <copy file="${otherSrcDirectory}/features/org.yocto.sdk.site/category.xml" todir="${buildDirectory}" />
82 <xmlproperty file="${otherSrcDirectory}/features/org.yocto.doc/feature.xml" />
83 <replace file="${buildDirectory}/category.xml">
84 <replacefilter token="@docFeatureVersion@" value="${feature(version)}"/>
85 </replace>
86 </target>
87
88 <!-- ===================================================================== -->
89 <!-- Steps to do after setup but before starting the build proper -->
90 <!-- ===================================================================== -->
91 <target name="postSetup">
92 <antcall target="getBaseComponents" />
93 </target>
94
95 <!-- ===================================================================== -->
96 <!-- Steps to do before fetching the build elements -->
97 <!-- ===================================================================== -->
98 <target name="preFetch">
99 </target>
100
101 <!-- ===================================================================== -->
102 <!-- Steps to do after fetching the build elements -->
103 <!-- ===================================================================== -->
104 <target name="postFetch">
105 </target>
106
107 <!-- ===================================================================== -->
108 <!-- Steps to do before the repositories are being processed -->
109 <!-- ===================================================================== -->
110 <target name="preProcessRepos">
111 </target>
112
113 <!-- ===================================================================== -->
114 <!-- Steps to do after the repositories have been processed -->
115 <!-- ===================================================================== -->
116 <target name="postProcessRepos">
117 </target>
118
119 <!-- ===================================================================== -->
120 <!-- Steps to do before generating the build scripts. -->
121 <!-- ===================================================================== -->
122 <target name="preGenerate">
123 </target>
124
125 <!-- ===================================================================== -->
126 <!-- Steps to do after generating the build scripts. -->
127 <!-- ===================================================================== -->
128 <target name="postGenerate">
129 <antcall target="clean" />
130 </target>
131
132 <!-- ===================================================================== -->
133 <!-- Steps to do before running the build.xmls for the elements being built. -->
134 <!-- ===================================================================== -->
135 <target name="preProcess">
136 </target>
137
138 <!-- ===================================================================== -->
139 <!-- Steps to do after running the build.xmls for the elements being built. -->
140 <!-- ===================================================================== -->
141 <target name="postProcess">
142 </target>
143
144 <!-- ===================================================================== -->
145 <!-- Steps to do before running assemble. -->
146 <!-- ===================================================================== -->
147 <target name="preAssemble">
148 </target>
149
150 <!-- ===================================================================== -->
151 <!-- Steps to do after running assemble. -->
152 <!-- ===================================================================== -->
153 <target name="postAssemble">
154 </target>
155
156 <!-- ===================================================================== -->
157 <!-- Steps to do before running package. -->
158 <!-- ===================================================================== -->
159 <target name="prePackage">
160 </target>
161
162 <!-- ===================================================================== -->
163 <!-- Steps to do after running package. -->
164 <!-- ===================================================================== -->
165 <target name="postPackage">
166 </target>
167
168 <!-- ===================================================================== -->
169 <!-- Steps to do after the build is done. -->
170 <!-- ===================================================================== -->
171 <target name="postBuild">
172 <antcall target="gatherLogs" />
173 <antcall target="updateSiteContent" />
174 </target>
175
176 <target name="updateSiteContent" if="p2.gathering">
177 <property file="${buildDirectory}/finalFeaturesVersions.properties" />
178 <copy file="${otherSrcDirectory}/features/org.yocto.sdk.site/site.xml" todir="${buildDirectory}" />
179 <replace file="${buildDirectory}/site.xml">
180 <replacefilter token="@docGenVersion@" value="${org.yocto.doc}"/>
181 </replace>
182 <zip destfile="${buildDirectory}/${buildLabel}/org.yocto.doc-${buildId}-group.group.group.zip" update="true">
183 <zipfileset dir="${buildDirectory}">
184 <include name="site.xml"/>
185 </zipfileset>
186 <zipfileset dir="${otherSrcDirectory}/features/org.yocto.sdk.site">
187 <include name="index.html"/>
188 </zipfileset>
189 <zipfileset dir="${otherSrcDirectory}/features/org.yocto.sdk.site/web" prefix="web"/>
190 </zip>
191 </target>
192
193 <!-- ===================================================================== -->
194 <!-- Steps to do to test the build results -->
195 <!-- ===================================================================== -->
196 <target name="test">
197 </target>
198
199 <!-- ===================================================================== -->
200 <!-- Steps to do to publish the build results -->
201 <!-- ===================================================================== -->
202 <target name="publish">
203 </target>
204
205 <!-- ===================================================================== -->
206 <!-- Default target -->
207 <!-- ===================================================================== -->
208 <target name="noDefault">
209 <echo message="You must specify a target when invoking this file" />
210 </target>
211
212</project>
diff --git a/features/org.yocto.doc/.project b/features/org.yocto.doc/.project
new file mode 100644
index 0000000..2ad46a8
--- /dev/null
+++ b/features/org.yocto.doc/.project
@@ -0,0 +1,17 @@
1<?xml version="1.0" encoding="UTF-8"?>
2<projectDescription>
3 <name>org.yocto.doc</name>
4 <comment></comment>
5 <projects>
6 </projects>
7 <buildSpec>
8 <buildCommand>
9 <name>org.eclipse.pde.FeatureBuilder</name>
10 <arguments>
11 </arguments>
12 </buildCommand>
13 </buildSpec>
14 <natures>
15 <nature>org.eclipse.pde.FeatureNature</nature>
16 </natures>
17</projectDescription>
diff --git a/features/org.yocto.doc/build.properties b/features/org.yocto.doc/build.properties
new file mode 100644
index 0000000..52c3cfc
--- /dev/null
+++ b/features/org.yocto.doc/build.properties
@@ -0,0 +1,3 @@
1bin.includes = feature.xml,\
2 license.html,\
3 feature.properties
diff --git a/features/org.yocto.doc/feature.properties b/features/org.yocto.doc/feature.properties
new file mode 100644
index 0000000..46883e8
--- /dev/null
+++ b/features/org.yocto.doc/feature.properties
@@ -0,0 +1,163 @@
1###############################################################################
2# Copyright (c) 2010 Intel, Inc. and others.
3# All rights reserved. This program and the accompanying materials
4# are made available under the terms of the Eclipse Public License v1.0
5# which accompanies this distribution, and is available at
6# http://www.eclipse.org/legal/epl-v10.html
7#
8# Contributors:
9# Intel - initial implementation
10###############################################################################
11
12# "featureName" property - name of the feature
13featureName=Yocto Project Documentation Plug-in
14
15# "providerName" property - name of the company that provides the feature
16providerName=yoctoproject.org
17
18# "updateSiteName" property - label for the update site
19updateSiteName=Yocto Project Update Site
20
21# "description" property - description of the feature
22description=\
23Eclipse plug-in containing the documentation of the Yocto Project
24
25# copyright
26copyright=\
27Copyright (c) 2013 Intel, Inc. and others. \
28All rights reserved. This program and the accompanying materials \
29are made available under the terms of the Eclipse Public License v1.0 \
30which accompanies this distribution, and is available at \
31http://www.eclipse.org/legal/epl-v10.html
32################ end of copyright property ####################################
33
34# "licenseURL" property - URL of the "Feature License"
35# do not translate value - just change to point to a locale-specific HTML page
36licenseURL=license.html
37
38# "license" property - text of the "Feature Update License"
39# should be plain text version of license agreement pointed to be "licenseURL"
40license=\
41Eclipse Foundation Software User Agreement\n\
42April 14, 2010\n\
43\n\
44Usage Of Content\n\
45\n\
46THE ECLIPSE FOUNDATION MAKES AVAILABLE SOFTWARE, DOCUMENTATION, INFORMATION AND/OR\n\
47OTHER MATERIALS FOR OPEN SOURCE PROJECTS (COLLECTIVELY "CONTENT").\n\
48USE OF THE CONTENT IS GOVERNED BY THE TERMS AND CONDITIONS OF THIS\n\
49AGREEMENT AND/OR THE TERMS AND CONDITIONS OF LICENSE AGREEMENTS OR\n\
50NOTICES INDICATED OR REFERENCED BELOW. BY USING THE CONTENT, YOU\n\
51AGREE THAT YOUR USE OF THE CONTENT IS GOVERNED BY THIS AGREEMENT\n\
52AND/OR THE TERMS AND CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS\n\
53OR NOTICES INDICATED OR REFERENCED BELOW. IF YOU DO NOT AGREE TO THE\n\
54TERMS AND CONDITIONS OF THIS AGREEMENT AND THE TERMS AND CONDITIONS\n\
55OF ANY APPLICABLE LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED\n\
56BELOW, THEN YOU MAY NOT USE THE CONTENT.\n\
57\n\
58Applicable Licenses\n\
59\n\
60Unless otherwise indicated, all Content made available by the\n\
61Eclipse Foundation is provided to you under the terms and conditions of\n\
62the Eclipse Public License Version 1.0 ("EPL"). A copy of the EPL is\n\
63provided with this Content and is also available at http://www.eclipse.org/legal/epl-v10.html.\n\
64For purposes of the EPL, "Program" will mean the Content.\n\
65\n\
66Content includes, but is not limited to, source code, object code,\n\
67documentation and other files maintained in the Eclipse Foundation source code\n\
68repository ("Repository") in software modules ("Modules") and made available\n\
69as downloadable archives ("Downloads").\n\
70\n\
71 - Content may be structured and packaged into modules to facilitate delivering,\n\
72 extending, and upgrading the Content. Typical modules may include plug-ins ("Plug-ins"),\n\
73 plug-in fragments ("Fragments"), and features ("Features").\n\
74 - Each Plug-in or Fragment may be packaged as a sub-directory or JAR (Java(TM) ARchive)\n\
75 in a directory named "plugins".\n\
76 - A Feature is a bundle of one or more Plug-ins and/or Fragments and associated material.\n\
77 Each Feature may be packaged as a sub-directory in a directory named "features".\n\
78 Within a Feature, files named "feature.xml" may contain a list of the names and version\n\
79 numbers of the Plug-ins and/or Fragments associated with that Feature.\n\
80 - Features may also include other Features ("Included Features"). Within a Feature, files\n\
81 named "feature.xml" may contain a list of the names and version numbers of Included Features.\n\
82\n\
83The terms and conditions governing Plug-ins and Fragments should be\n\
84contained in files named "about.html" ("Abouts"). The terms and\n\
85conditions governing Features and Included Features should be contained\n\
86in files named "license.html" ("Feature Licenses"). Abouts and Feature\n\
87Licenses may be located in any directory of a Download or Module\n\
88including, but not limited to the following locations:\n\
89\n\
90 - The top-level (root) directory\n\
91 - Plug-in and Fragment directories\n\
92 - Inside Plug-ins and Fragments packaged as JARs\n\
93 - Sub-directories of the directory named "src" of certain Plug-ins\n\
94 - Feature directories\n\
95\n\
96Note: if a Feature made available by the Eclipse Foundation is installed using the\n\
97Provisioning Technology (as defined below), you must agree to a license ("Feature \n\
98Update License") during the installation process. If the Feature contains\n\
99Included Features, the Feature Update License should either provide you\n\
100with the terms and conditions governing the Included Features or inform\n\
101you where you can locate them. Feature Update Licenses may be found in\n\
102the "license" property of files named "feature.properties" found within a Feature.\n\
103Such Abouts, Feature Licenses, and Feature Update Licenses contain the\n\
104terms and conditions (or references to such terms and conditions) that\n\
105govern your use of the associated Content in that directory.\n\
106\n\
107THE ABOUTS, FEATURE LICENSES, AND FEATURE UPDATE LICENSES MAY REFER\n\
108TO THE EPL OR OTHER LICENSE AGREEMENTS, NOTICES OR TERMS AND CONDITIONS.\n\
109SOME OF THESE OTHER LICENSE AGREEMENTS MAY INCLUDE (BUT ARE NOT LIMITED TO):\n\
110\n\
111 - Common Public License Version 1.0 (available at http://www.eclipse.org/legal/cpl-v10.html)\n\
112 - Apache Software License 1.1 (available at http://www.apache.org/licenses/LICENSE)\n\
113 - Apache Software License 2.0 (available at http://www.apache.org/licenses/LICENSE-2.0)\n\
114 - Metro Link Public License 1.00 (available at http://www.opengroup.org/openmotif/supporters/metrolink/license.html)\n\
115 - Mozilla Public License Version 1.1 (available at http://www.mozilla.org/MPL/MPL-1.1.html)\n\
116\n\
117IT IS YOUR OBLIGATION TO READ AND ACCEPT ALL SUCH TERMS AND CONDITIONS PRIOR\n\
118TO USE OF THE CONTENT. If no About, Feature License, or Feature Update License\n\
119is provided, please contact the Eclipse Foundation to determine what terms and conditions\n\
120govern that particular Content.\n\
121\n\
122\n\Use of Provisioning Technology\n\
123\n\
124The Eclipse Foundation makes available provisioning software, examples of which include,\n\
125but are not limited to, p2 and the Eclipse Update Manager ("Provisioning Technology") for\n\
126the purpose of allowing users to install software, documentation, information and/or\n\
127other materials (collectively "Installable Software"). This capability is provided with\n\
128the intent of allowing such users to install, extend and update Eclipse-based products.\n\
129Information about packaging Installable Software is available at\n\
130http://eclipse.org/equinox/p2/repository_packaging.html ("Specification").\n\
131\n\
132You may use Provisioning Technology to allow other parties to install Installable Software.\n\
133You shall be responsible for enabling the applicable license agreements relating to the\n\
134Installable Software to be presented to, and accepted by, the users of the Provisioning Technology\n\
135in accordance with the Specification. By using Provisioning Technology in such a manner and\n\
136making it available in accordance with the Specification, you further acknowledge your\n\
137agreement to, and the acquisition of all necessary rights to permit the following:\n\
138\n\
139 1. A series of actions may occur ("Provisioning Process") in which a user may execute\n\
140 the Provisioning Technology on a machine ("Target Machine") with the intent of installing,\n\
141 extending or updating the functionality of an Eclipse-based product.\n\
142 2. During the Provisioning Process, the Provisioning Technology may cause third party\n\
143 Installable Software or a portion thereof to be accessed and copied to the Target Machine.\n\
144 3. Pursuant to the Specification, you will provide to the user the terms and conditions that\n\
145 govern the use of the Installable Software ("Installable Software Agreement") and such\n\
146 Installable Software Agreement shall be accessed from the Target Machine in accordance\n\
147 with the Specification. Such Installable Software Agreement must inform the user of the\n\
148 terms and conditions that govern the Installable Software and must solicit acceptance by\n\
149 the end user in the manner prescribed in such Installable Software Agreement. Upon such\n\
150 indication of agreement by the user, the provisioning Technology will complete installation\n\
151 of the Installable Software.\n\
152\n\
153Cryptography\n\
154\n\
155Content may contain encryption software. The country in which you are\n\
156currently may have restrictions on the import, possession, and use,\n\
157and/or re-export to another country, of encryption software. BEFORE\n\
158using any encryption software, please check the country's laws,\n\
159regulations and policies concerning the import, possession, or use, and\n\
160re-export of encryption software, to see if this is permitted.\n\
161\n\
162Java and all Java-based trademarks are trademarks of Oracle Corporation in the United States, other countries, or both.\n
163########### end of license property ##########################################
diff --git a/features/org.yocto.doc/feature.xml b/features/org.yocto.doc/feature.xml
new file mode 100644
index 0000000..ed8687e
--- /dev/null
+++ b/features/org.yocto.doc/feature.xml
@@ -0,0 +1,35 @@
1<?xml version="1.0" encoding="UTF-8"?>
2<feature
3 id="org.yocto.doc"
4 label="%featureName"
5 version="1.4.0.qualifier"
6 provider-name="%providerName">
7
8 <description>
9 %description
10 </description>
11
12 <copyright>
13 %copyright
14 </copyright>
15
16 <license url="%licenseURL">
17 %license
18 </license>
19
20 <url>
21 <update label="%updateSiteName" url="http://yoctoproject.org/downloads/eclipse-plugin/"/>
22 </url>
23
24 <requires>
25 <import plugin="org.eclipse.help"/>
26 </requires>
27
28 <plugin
29 id="org.yocto.doc.user"
30 download-size="0"
31 install-size="0"
32 version="0.0.0"
33 unpack="false"/>
34
35</feature>
diff --git a/features/org.yocto.doc/license.html b/features/org.yocto.doc/license.html
new file mode 100644
index 0000000..c184ca3
--- /dev/null
+++ b/features/org.yocto.doc/license.html
@@ -0,0 +1,107 @@
1<?xml version="1.0" encoding="ISO-8859-1" ?>
2<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
3<html xmlns="http://www.w3.org/1999/xhtml">
4<head>
5<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
6<title>Eclipse Foundation Software User Agreement</title>
7</head>
8
9<body lang="EN-US">
10<h2>Eclipse Foundation Software User Agreement</h2>
11<p>April 14, 2010</p>
12
13<h3>Usage Of Content</h3>
14
15<p>THE ECLIPSE FOUNDATION MAKES AVAILABLE SOFTWARE, DOCUMENTATION, INFORMATION AND/OR OTHER MATERIALS FOR OPEN SOURCE PROJECTS
16 (COLLECTIVELY &quot;CONTENT&quot;). USE OF THE CONTENT IS GOVERNED BY THE TERMS AND CONDITIONS OF THIS AGREEMENT AND/OR THE TERMS AND
17 CONDITIONS OF LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW. BY USING THE CONTENT, YOU AGREE THAT YOUR USE
18 OF THE CONTENT IS GOVERNED BY THIS AGREEMENT AND/OR THE TERMS AND CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS OR
19 NOTICES INDICATED OR REFERENCED BELOW. IF YOU DO NOT AGREE TO THE TERMS AND CONDITIONS OF THIS AGREEMENT AND THE TERMS AND
20 CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW, THEN YOU MAY NOT USE THE CONTENT.</p>
21
22<h3>Applicable Licenses</h3>
23
24<p>Unless otherwise indicated, all Content made available by the Eclipse Foundation is provided to you under the terms and conditions of the Eclipse Public License Version 1.0
25 (&quot;EPL&quot;). A copy of the EPL is provided with this Content and is also available at <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>.
26 For purposes of the EPL, &quot;Program&quot; will mean the Content.</p>
27
28<p>Content includes, but is not limited to, source code, object code, documentation and other files maintained in the Eclipse Foundation source code
29 repository (&quot;Repository&quot;) in software modules (&quot;Modules&quot;) and made available as downloadable archives (&quot;Downloads&quot;).</p>
30
31<ul>
32 <li>Content may be structured and packaged into modules to facilitate delivering, extending, and upgrading the Content. Typical modules may include plug-ins (&quot;Plug-ins&quot;), plug-in fragments (&quot;Fragments&quot;), and features (&quot;Features&quot;).</li>
33 <li>Each Plug-in or Fragment may be packaged as a sub-directory or JAR (Java&trade; ARchive) in a directory named &quot;plugins&quot;.</li>
34 <li>A Feature is a bundle of one or more Plug-ins and/or Fragments and associated material. Each Feature may be packaged as a sub-directory in a directory named &quot;features&quot;. Within a Feature, files named &quot;feature.xml&quot; may contain a list of the names and version numbers of the Plug-ins
35 and/or Fragments associated with that Feature.</li>
36 <li>Features may also include other Features (&quot;Included Features&quot;). Within a Feature, files named &quot;feature.xml&quot; may contain a list of the names and version numbers of Included Features.</li>
37</ul>
38
39<p>The terms and conditions governing Plug-ins and Fragments should be contained in files named &quot;about.html&quot; (&quot;Abouts&quot;). The terms and conditions governing Features and
40Included Features should be contained in files named &quot;license.html&quot; (&quot;Feature Licenses&quot;). Abouts and Feature Licenses may be located in any directory of a Download or Module
41including, but not limited to the following locations:</p>
42
43<ul>
44 <li>The top-level (root) directory</li>
45 <li>Plug-in and Fragment directories</li>
46 <li>Inside Plug-ins and Fragments packaged as JARs</li>
47 <li>Sub-directories of the directory named &quot;src&quot; of certain Plug-ins</li>
48 <li>Feature directories</li>
49</ul>
50
51<p>Note: if a Feature made available by the Eclipse Foundation is installed using the Provisioning Technology (as defined below), you must agree to a license (&quot;Feature Update License&quot;) during the
52installation process. If the Feature contains Included Features, the Feature Update License should either provide you with the terms and conditions governing the Included Features or
53inform you where you can locate them. Feature Update Licenses may be found in the &quot;license&quot; property of files named &quot;feature.properties&quot; found within a Feature.
54Such Abouts, Feature Licenses, and Feature Update Licenses contain the terms and conditions (or references to such terms and conditions) that govern your use of the associated Content in
55that directory.</p>
56
57<p>THE ABOUTS, FEATURE LICENSES, AND FEATURE UPDATE LICENSES MAY REFER TO THE EPL OR OTHER LICENSE AGREEMENTS, NOTICES OR TERMS AND CONDITIONS. SOME OF THESE
58OTHER LICENSE AGREEMENTS MAY INCLUDE (BUT ARE NOT LIMITED TO):</p>
59
60<ul>
61 <li>Common Public License Version 1.0 (available at <a href="http://www.eclipse.org/legal/cpl-v10.html">http://www.eclipse.org/legal/cpl-v10.html</a>)</li>
62 <li>Apache Software License 1.1 (available at <a href="http://www.apache.org/licenses/LICENSE">http://www.apache.org/licenses/LICENSE</a>)</li>
63 <li>Apache Software License 2.0 (available at <a href="http://www.apache.org/licenses/LICENSE-2.0">http://www.apache.org/licenses/LICENSE-2.0</a>)</li>
64 <li>Metro Link Public License 1.00 (available at <a href="http://www.opengroup.org/openmotif/supporters/metrolink/license.html">http://www.opengroup.org/openmotif/supporters/metrolink/license.html</a>)</li>
65 <li>Mozilla Public License Version 1.1 (available at <a href="http://www.mozilla.org/MPL/MPL-1.1.html">http://www.mozilla.org/MPL/MPL-1.1.html</a>)</li>
66</ul>
67
68<p>IT IS YOUR OBLIGATION TO READ AND ACCEPT ALL SUCH TERMS AND CONDITIONS PRIOR TO USE OF THE CONTENT. If no About, Feature License, or Feature Update License is provided, please
69contact the Eclipse Foundation to determine what terms and conditions govern that particular Content.</p>
70
71
72<h3>Use of Provisioning Technology</h3>
73
74<p>The Eclipse Foundation makes available provisioning software, examples of which include, but are not limited to, p2 and the Eclipse
75 Update Manager (&quot;Provisioning Technology&quot;) for the purpose of allowing users to install software, documentation, information and/or
76 other materials (collectively &quot;Installable Software&quot;). This capability is provided with the intent of allowing such users to
77 install, extend and update Eclipse-based products. Information about packaging Installable Software is available at <a
78 href="http://eclipse.org/equinox/p2/repository_packaging.html">http://eclipse.org/equinox/p2/repository_packaging.html</a>
79 (&quot;Specification&quot;).</p>
80
81<p>You may use Provisioning Technology to allow other parties to install Installable Software. You shall be responsible for enabling the
82 applicable license agreements relating to the Installable Software to be presented to, and accepted by, the users of the Provisioning Technology
83 in accordance with the Specification. By using Provisioning Technology in such a manner and making it available in accordance with the
84 Specification, you further acknowledge your agreement to, and the acquisition of all necessary rights to permit the following:</p>
85
86<ol>
87 <li>A series of actions may occur (&quot;Provisioning Process&quot;) in which a user may execute the Provisioning Technology
88 on a machine (&quot;Target Machine&quot;) with the intent of installing, extending or updating the functionality of an Eclipse-based
89 product.</li>
90 <li>During the Provisioning Process, the Provisioning Technology may cause third party Installable Software or a portion thereof to be
91 accessed and copied to the Target Machine.</li>
92 <li>Pursuant to the Specification, you will provide to the user the terms and conditions that govern the use of the Installable
93 Software (&quot;Installable Software Agreement&quot;) and such Installable Software Agreement shall be accessed from the Target
94 Machine in accordance with the Specification. Such Installable Software Agreement must inform the user of the terms and conditions that govern
95 the Installable Software and must solicit acceptance by the end user in the manner prescribed in such Installable Software Agreement. Upon such
96 indication of agreement by the user, the provisioning Technology will complete installation of the Installable Software.</li>
97</ol>
98
99<h3>Cryptography</h3>
100
101<p>Content may contain encryption software. The country in which you are currently may have restrictions on the import, possession, and use, and/or re-export to
102 another country, of encryption software. BEFORE using any encryption software, please check the country's laws, regulations and policies concerning the import,
103 possession, or use, and re-export of encryption software, to see if this is permitted.</p>
104
105<p><small>Java and all Java-based trademarks are trademarks of Oracle Corporation in the United States, other countries, or both.</small></p>
106</body>
107</html>
diff --git a/features/org.yocto.sdk.headless.build/.project b/features/org.yocto.sdk.headless.build/.project
new file mode 100644
index 0000000..f796e80
--- /dev/null
+++ b/features/org.yocto.sdk.headless.build/.project
@@ -0,0 +1,11 @@
1<?xml version="1.0" encoding="UTF-8"?>
2<projectDescription>
3 <name>org.yocto.sdk.headless.build</name>
4 <comment></comment>
5 <projects>
6 </projects>
7 <buildSpec>
8 </buildSpec>
9 <natures>
10 </natures>
11</projectDescription>
diff --git a/features/org.yocto.sdk.headless.build/build.properties b/features/org.yocto.sdk.headless.build/build.properties
new file mode 100644
index 0000000..5a9b637
--- /dev/null
+++ b/features/org.yocto.sdk.headless.build/build.properties
@@ -0,0 +1,262 @@
1###############################################################################
2# Copyright (c) 2003, 2009 IBM Corporation and others.
3# All rights reserved. This program and the accompanying materials
4# are made available under the terms of the Eclipse Public License v1.0
5# which accompanies this distribution, and is available at
6# http://www.eclipse.org/legal/epl-v10.html
7#
8# Contributors:
9# IBM Corporation - initial API and implementation
10###############################################################################
11#####################
12# Parameters describing how and where to execute the build.
13# Typical users need only update the following properties:
14# baseLocation - where things you are building against are installed
15# bootclasspath - The base jars to compile against (typicaly rt.jar)
16# configs - the list of {os, ws, arch} configurations to build.
17#
18# Of course any of the settings here can be overridden by spec'ing
19# them on the command line (e.g., -DbaseLocation=d:/eclipse
20
21#The type of the top level element we are building, generally "feature"
22topLevelElementType = feature
23#The id of the top level element we are building
24topLevelElementId = org.yocto.sdk
25
26############# PRODUCT/PACKAGING CONTROL #############
27product=/plugin or feature id/path/to/.product
28runPackager=true
29
30#Set the name of the archive that will result from the product build.
31#archiveNamePrefix=
32
33# The prefix that will be used in the generated archive.
34archivePrefix=eclipse
35
36# The location underwhich all of the build output will be collected.
37collectingFolder=${archivePrefix}
38
39# The list of {os, ws, arch} configurations to build. This
40# value is a '&' separated list of ',' separate triples. For example,
41# configs=win32,win32,x86 & linux,motif,x86
42# By default the value is *,*,*
43configs = *, *, *
44#configs=win32, win32, x86 & \
45# win32,win32,x86_64 & \
46# win32,win32,wpf & \
47# linux, gtk, ppc & \
48# linux, gtk, x86 & \
49# linux, gtk, x86_64 & \
50# linux, motif, x86 & \
51# solaris, motif, sparc & \
52# solaris, gtk, sparc & \
53# aix, motif, ppc & \
54# hpux, motif, ia64_32 & \
55# macosx, carbon, ppc & \
56# macosx, carbon, x86 & \
57# macosx, cocoa, ppc & \
58# macosx, cocoa, x86 & \
59# macosx, cocoa, x86_64
60
61# By default PDE creates one archive (result) per entry listed in the configs property.
62# Setting this value to true will cause PDE to only create one output containing all
63# artifacts for all the platforms listed in the configs property.
64# To control the output format for the group, add a "group, group, group - <format>" entry to the
65# archivesFormat.
66#groupConfigurations=true
67
68#The format of the archive. By default a zip is created using antZip.
69#The list can only contain the configuration for which the desired format is different than zip.
70#archivesFormat=win32, win32, x86 - antZip& \
71# linux, gtk, ppc - antZip &\
72# linux, gtk, x86 - antZip& \
73# linux, gtk, x86_64 - antZip& \
74# linux, motif, x86 - antZip& \
75# solaris, motif, sparc - antZip& \
76# solaris, gtk, sparc - antZip& \
77# aix, motif, ppc - antZip& \
78# hpux, motif, PA_RISC - antZip& \
79# macosx, carbon, ppc - antZip
80
81#Allow cycles involving at most one bundle that needs to be compiled with the rest being binary bundles.
82allowBinaryCycles = true
83
84#Sort bundles depenedencies across all features instead of just within a given feature.
85#flattenDependencies = true
86
87#Parallel compilation, requires flattenedDependencies=true
88#parallelCompilation=true
89#parallelThreadCount=
90#parallelThreadsPerProcessor=
91
92#Set to true if you want the output to be ready for an update jar (no site.xml generated)
93outputUpdateJars = true
94
95#Set to true for Jnlp generation
96#codebase should be a URL that will be used as the root of all relative URLs in the output.
97#generateJnlp=false
98#jnlp.codebase=<codebase url>
99#jnlp.j2se=<j2se version>
100#jnlp.locale=<a locale>
101#jnlp.generateOfflineAllowed=true or false generate <offlineAllowed/> attribute in the generated features
102#jnlp.configs=${configs} #uncomment to filter the content of the generated jnlp files based on the configuration being built
103
104#Set to true if you want to sign jars
105#signJars=false
106#sign.alias=<alias>
107#sign.keystore=<keystore location>
108#sign.storepass=<keystore password>
109#sign.keypass=<key password>
110
111#Arguments to send to the zip executable
112zipargs=
113
114#Arguments to send to the tar executable
115tarargs=
116
117#Control the creation of a file containing the version included in each configuration - on by default
118#generateVersionsLists=false
119
120############## BUILD NAMING CONTROL ################
121# The directory into which the build elements are fetched and where
122# the build takes place.
123#buildDirectory=
124
125# Type of build. Used in naming the build output. Typically this value is
126# one of I, N, M, S, ...
127buildType=I
128
129# ID of the build. Used in naming the build output.
130buildId=TestBuild
131
132# Label for the build. Used in naming the build output
133buildLabel=${buildType}.${buildId}
134
135# Timestamp for the build. Used in naming the build output
136timestamp=007
137
138#The value to be used for the qualifier of a plugin or feature when you want to override the value computed by pde.
139#The value will only be applied to plugin or features indicating build.properties, qualifier = context
140#forceContextQualifier=<the value for the qualifier>
141
142#Enable / disable the generation of a suffix for the features that use .qualifier.
143#The generated suffix is computed according to the content of the feature
144#generateFeatureVersionSuffix=true
145
146############# BASE CONTROL #############
147# Settings for the base Eclipse components and Java class libraries
148# against which you are building.
149# Base location for anything the build needs to compile against. For example,
150# in most RCP app or a plug-in, the baseLocation should be the location of a previously
151# installed Eclipse against which the application or plug-in code will be compiled and the RCP delta pack.
152
153#base=<path/to/parent/of/eclipse>
154#baseLocation=${base}/eclipse
155
156#Folder containing repositories whose content is needed to compile against
157#repoBaseLocation=${base}/repos
158#Folder where the content of the repositories from ${repoBaseLocation} will be made available as a form suitable to be compiled against
159#transformedRepoLocation=${base}/transformedRepos
160
161#Os/Ws/Arch/nl of the eclipse specified by baseLocation
162#baseos=win32
163#basews=win32
164#basearch=x86
165
166#this property indicates whether you want the set of plug-ins and features to be considered during the build to be limited to the ones reachable from the features / plugins being built
167filteredDependencyCheck=false
168
169#this property indicates whether the resolution should be done in development mode (i.e. ignore multiple bundles with singletons)
170resolution.devMode=false
171
172#pluginPath is a list of locations in which to find plugins and features. This list is separated by the platform file separator (; or :)
173#a location is one of:
174#- the location of the jar or folder that is the plugin or feature : /path/to/foo.jar or /path/to/foo
175#- a directory that contains a /plugins or /features subdirectory
176#- the location of a feature.xml, or for 2.1 style plugins, the plugin.xml or fragment.xml
177#pluginPath=
178
179skipBase=true
180eclipseURL=<url for eclipse download site>
181eclipseBuildId=<Id of Eclipse build to get>
182eclipseBaseURL=${eclipseURL}/eclipse-platform-${eclipseBuildId}-win32.zip
183
184
185############# MAP FILE CONTROL ################
186# This section defines CVS tags to use when fetching the map files from the repository.
187# If you want to fetch the map file from repository / location, change the getMapFiles target in the customTargets.xml
188
189skipMaps=true
190mapsRepo=:pserver:anonymous@example.com/path/to/repo
191mapsRoot=path/to/maps
192mapsCheckoutTag=HEAD
193
194#tagMaps=true
195mapsTagTag=v${buildId}
196
197
198############ REPOSITORY CONTROL ###############
199# This section defines properties parameterizing the repositories where plugins, fragments
200# bundles and features are being obtained from.
201
202# The tags to use when fetching elements to build.
203# By default thebuilder will use whatever is in the maps.
204# This value takes the form of a comma separated list of repository identifier (like used in the map files) and the
205# overriding value
206# For example fetchTag=CVS=HEAD, SVN=v20050101
207# fetchTag=HEAD
208skipFetch=true
209
210
211############# JAVA COMPILER OPTIONS ##############
212# The location of the Java jars to compile against. Typically the rt.jar for your JDK/JRE
213#bootclasspath=${java.home}/lib/rt.jar
214
215# specific JRE locations to compile against. These values are used to compile bundles specifying a
216# Bundle-RequiredExecutionEnvironment. Uncomment and set values for environments that you support
217#CDC-1.0/Foundation-1.0= /path/to/rt.jar
218#CDC-1.1/Foundation-1.1=
219#OSGi/Minimum-1.0=
220#OSGi/Minimum-1.1=
221#JRE-1.1=
222#J2SE-1.2=
223#J2SE-1.3=
224#J2SE-1.4=
225#J2SE-1.5=
226#JavaSE-1.6=
227#PersonalJava-1.1=
228#PersonalJava-1.2=
229#CDC-1.0/PersonalBasis-1.0=
230#CDC-1.0/PersonalJava-1.0=
231#CDC-1.1/PersonalBasis-1.1=
232#CDC-1.1/PersonalJava-1.1=
233
234# Specify the output format of the compiler log when eclipse jdt is used
235logExtension=.log
236
237# Whether or not to include debug info in the output jars
238javacDebugInfo=false
239
240# Whether or not to fail the build if there are compiler errors
241javacFailOnError=true
242
243# Enable or disable verbose mode of the compiler
244javacVerbose=true
245
246# Extra arguments for the compiler. These are specific to the java compiler being used.
247#compilerArg=
248
249# Default value for the version of the source code. This value is used when compiling plug-ins that do not set the Bundle-RequiredExecutionEnvironment or set javacSource in build.properties
250javacSource=1.6
251
252# Default value for the version of the byte code targeted. This value is used when compiling plug-ins that do not set the Bundle-RequiredExecutionEnvironment or set javacTarget in build.properties.
253javacTarget=1.6
254
255#individualSourceBundles=true
256
257#p2.gathering=true
258p2.compress=true
259#p2.category.site=file:${buildDirectory}/site.xml
260p2.category.definition=file:${buildDirectory}/category.xml
261p2.metadata.repo.name=Yocto Project Update Site
262p2.artifact.repo.name=Yocto Project Update Site
diff --git a/features/org.yocto.sdk.headless.build/customTargets.xml b/features/org.yocto.sdk.headless.build/customTargets.xml
new file mode 100644
index 0000000..cb08f91
--- /dev/null
+++ b/features/org.yocto.sdk.headless.build/customTargets.xml
@@ -0,0 +1,212 @@
1<project name="Build specific targets and properties" default="noDefault">
2
3 <!-- ===================================================================== -->
4 <!-- Run a given ${target} on all elements being built -->
5 <!-- Add on <ant> task for each top level element being built. -->
6 <!-- ===================================================================== -->
7 <available property="allElementsFile" file="${builder}/allElements.xml" value="${builder}/allElements.xml"/>
8 <property name="allElementsFile" location="${eclipse.pdebuild.templates}/headless-build/allElements.xml"/>
9
10 <import file="${allElementsFile}" />
11 <target name="allElements">
12 <antcall target="allElementsDelegator" />
13 </target>
14
15 <!-- ===================================================================== -->
16 <!-- ===================================================================== -->
17 <target name="getBaseComponents" depends="checkLocalBase" unless="skipBase">
18 <get src="${eclipseBaseURL}" dest="${buildDirectory}/../temp-base.zip" />
19 <unzip dest="${base}" overwrite="true" src="${buildDirectory}/../temp-base.zip" />
20 </target>
21
22 <target name="checkLocalBase">
23 <available file="${base}" property="skipBase" />
24 </target>
25
26 <!-- ===================================================================== -->
27 <!-- Check out map files from correct repository -->
28 <!-- Replace values for mapsCheckoutTag as desired. -->
29 <!-- ===================================================================== -->
30 <target name="getMapFiles" depends="checkLocalMaps" unless="skipMaps">
31 <property name="mapsCheckoutTag" value="HEAD" />
32 <cvs cvsRoot="${mapsRepo}" package="${mapsRoot}" dest="${buildDirectory}/maps" tag="${mapsCheckoutTag}" />
33 </target>
34
35 <target name="checkLocalMaps">
36 <available property="skipMaps" file="${buildDirectory}/maps" />
37 </target>
38
39 <target name="tagMapFiles" if="tagMaps">
40 <cvs dest="${buildDirectory}/maps/${mapsRoot}" command="tag ${mapsTagTag}" />
41 </target>
42
43 <!-- ===================================================================== -->
44
45 <target name="clean" unless="noclean">
46 <antcall target="allElements">
47 <param name="target" value="cleanElement" />
48 </antcall>
49 </target>
50
51 <target name="gatherLogs">
52 <mkdir dir="${buildDirectory}/${buildLabel}/compilelogs" />
53 <antcall target="allElements">
54 <param name="target" value="gatherLogs" />
55 </antcall>
56 <unzip dest="${buildDirectory}/${buildLabel}/compilelogs" overwrite="true">
57 <fileset dir="${buildDirectory}/features">
58 <include name="**/*.log.zip" />
59 </fileset>
60 </unzip>
61 </target>
62
63 <!-- ===================================================================== -->
64 <!-- Steps to do before setup -->
65 <!-- ===================================================================== -->
66 <target name="preSetup">
67 <delete dir="${buildDirectory}/plugins"/>
68 <mkdir dir="${buildDirectory}/plugins"/>
69 <copy todir="${buildDirectory}/plugins" failonerror="true">
70 <fileset dir="${otherSrcDirectory}/plugins"/>
71 </copy>
72 <delete dir="${buildDirectory}/features"/>
73 <copy todir="${buildDirectory}/features" failonerror="true" >
74 <fileset dir="${otherSrcDirectory}/features"/>
75 </copy>
76 <antcall target="prepareForP2" />
77 </target>
78
79 <target name="prepareForP2" if="p2.gathering">
80 <copy file="${otherSrcDirectory}/features/org.yocto.sdk.site/site.xml" todir="${buildDirectory}" />
81 <copy file="${otherSrcDirectory}/features/org.yocto.sdk.site/category.xml" todir="${buildDirectory}" />
82 <xmlproperty file="${otherSrcDirectory}/features/org.yocto.sdk/feature.xml" />
83 <replace file="${buildDirectory}/category.xml">
84 <replacefilter token="@featureVersion@" value="${feature(version)}"/>
85 </replace>
86 </target>
87
88 <!-- ===================================================================== -->
89 <!-- Steps to do after setup but before starting the build proper -->
90 <!-- ===================================================================== -->
91 <target name="postSetup">
92 <antcall target="getBaseComponents" />
93 </target>
94
95 <!-- ===================================================================== -->
96 <!-- Steps to do before fetching the build elements -->
97 <!-- ===================================================================== -->
98 <target name="preFetch">
99 </target>
100
101 <!-- ===================================================================== -->
102 <!-- Steps to do after fetching the build elements -->
103 <!-- ===================================================================== -->
104 <target name="postFetch">
105 </target>
106
107 <!-- ===================================================================== -->
108 <!-- Steps to do before the repositories are being processed -->
109 <!-- ===================================================================== -->
110 <target name="preProcessRepos">
111 </target>
112
113 <!-- ===================================================================== -->
114 <!-- Steps to do after the repositories have been processed -->
115 <!-- ===================================================================== -->
116 <target name="postProcessRepos">
117 </target>
118
119 <!-- ===================================================================== -->
120 <!-- Steps to do before generating the build scripts. -->
121 <!-- ===================================================================== -->
122 <target name="preGenerate">
123 </target>
124
125 <!-- ===================================================================== -->
126 <!-- Steps to do after generating the build scripts. -->
127 <!-- ===================================================================== -->
128 <target name="postGenerate">
129 <antcall target="clean" />
130 </target>
131
132 <!-- ===================================================================== -->
133 <!-- Steps to do before running the build.xmls for the elements being built. -->
134 <!-- ===================================================================== -->
135 <target name="preProcess">
136 </target>
137
138 <!-- ===================================================================== -->
139 <!-- Steps to do after running the build.xmls for the elements being built. -->
140 <!-- ===================================================================== -->
141 <target name="postProcess">
142 </target>
143
144 <!-- ===================================================================== -->
145 <!-- Steps to do before running assemble. -->
146 <!-- ===================================================================== -->
147 <target name="preAssemble">
148 </target>
149
150 <!-- ===================================================================== -->
151 <!-- Steps to do after running assemble. -->
152 <!-- ===================================================================== -->
153 <target name="postAssemble">
154 </target>
155
156 <!-- ===================================================================== -->
157 <!-- Steps to do before running package. -->
158 <!-- ===================================================================== -->
159 <target name="prePackage">
160 </target>
161
162 <!-- ===================================================================== -->
163 <!-- Steps to do after running package. -->
164 <!-- ===================================================================== -->
165 <target name="postPackage">
166 </target>
167
168 <!-- ===================================================================== -->
169 <!-- Steps to do after the build is done. -->
170 <!-- ===================================================================== -->
171 <target name="postBuild">
172 <antcall target="gatherLogs" />
173 <antcall target="updateSiteContent" />
174 </target>
175
176 <target name="updateSiteContent" if="p2.gathering">
177 <property file="${buildDirectory}/finalFeaturesVersions.properties" />
178 <copy file="${otherSrcDirectory}/features/org.yocto.sdk.site/site.xml" todir="${buildDirectory}" />
179 <replace file="${buildDirectory}/site.xml">
180 <replacefilter token="@genVersion@" value="${org.yocto.sdk}"/>
181 </replace>
182 <zip destfile="${buildDirectory}/${buildLabel}/org.yocto.sdk-${buildId}-group.group.group.zip" update="true">
183 <zipfileset dir="${buildDirectory}">
184 <include name="site.xml"/>
185 </zipfileset>
186 <zipfileset dir="${otherSrcDirectory}/features/org.yocto.sdk.site">
187 <include name="index.html"/>
188 </zipfileset>
189 <zipfileset dir="${otherSrcDirectory}/features/org.yocto.sdk.site/web" prefix="web"/>
190 </zip>
191 </target>
192
193 <!-- ===================================================================== -->
194 <!-- Steps to do to test the build results -->
195 <!-- ===================================================================== -->
196 <target name="test">
197 </target>
198
199 <!-- ===================================================================== -->
200 <!-- Steps to do to publish the build results -->
201 <!-- ===================================================================== -->
202 <target name="publish">
203 </target>
204
205 <!-- ===================================================================== -->
206 <!-- Default target -->
207 <!-- ===================================================================== -->
208 <target name="noDefault">
209 <echo message="You must specify a target when invoking this file" />
210 </target>
211
212</project>
diff --git a/features/org.yocto.sdk.site/.project b/features/org.yocto.sdk.site/.project
new file mode 100644
index 0000000..9f1d10f
--- /dev/null
+++ b/features/org.yocto.sdk.site/.project
@@ -0,0 +1,17 @@
1<?xml version="1.0" encoding="UTF-8"?>
2<projectDescription>
3 <name>org.yocto.sdk.site</name>
4 <comment></comment>
5 <projects>
6 </projects>
7 <buildSpec>
8 <buildCommand>
9 <name>org.eclipse.pde.UpdateSiteBuilder</name>
10 <arguments>
11 </arguments>
12 </buildCommand>
13 </buildSpec>
14 <natures>
15 <nature>org.eclipse.pde.UpdateSiteNature</nature>
16 </natures>
17</projectDescription>
diff --git a/features/org.yocto.sdk.site/category.xml b/features/org.yocto.sdk.site/category.xml
new file mode 100644
index 0000000..4dd0178
--- /dev/null
+++ b/features/org.yocto.sdk.site/category.xml
@@ -0,0 +1,18 @@
1<?xml version="1.0" encoding="UTF-8"?>
2<site>
3 <feature url="features/org.yocto.sdk_@featureVersion@.jar" id="org.yocto.sdk" version="@featureVersion@">
4 <category name="Yocto Project ADT"/>
5 </feature>
6 <feature url="features/org.yocto.sdk.source_@featureVersion@.jar" id="org.yocto.sdk.source" version="@featureVersion@">
7 <category name="Yocto Project ADT"/>
8 </feature>
9 <feature url="features/org.yocto.bc_@bcfeatureVersion@.jar" id="org.yocto.bc" version="@bcfeatureVersion@">
10 <category name="Yocto Project Bitbake Commander"/>
11 </feature>
12 <feature url="features/org.yocto.doc_@docFeatureVersion@.jar" id="org.yocto.doc" version="@docFeatureVersion@">
13 <category name="Yocto Project Documentation"/>
14 </feature>
15 <category-def name="Yocto Project ADT" label="Yocto Project ADT Plug-in"/>
16 <category-def name="Yocto Project Bitbake Commander" label="Yocto Project Bitbake Commander Plug-in"/>
17 <category-def name="Yocto Project Documentation" label="Yocto Project Documentation plug-in"/>
18</site>
diff --git a/features/org.yocto.sdk.site/index.html b/features/org.yocto.sdk.site/index.html
new file mode 100644
index 0000000..ce46f0e
--- /dev/null
+++ b/features/org.yocto.sdk.site/index.html
@@ -0,0 +1,60 @@
1<html>
2<head>
3<title>org.yocto.sdk.site</title>
4<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
5<style>@import url("web/site.css");</style>
6<script type="text/javascript">
7 var returnval = 0;
8 var stylesheet, xmlFile, cache, doc;
9 function init(){
10 // NSCP 7.1+ / Mozilla 1.4.1+ / Safari
11 // Use the standard DOM Level 2 technique, if it is supported
12 if (document.implementation && document.implementation.createDocument) {
13 xmlFile = document.implementation.createDocument("", "", null);
14 stylesheet = document.implementation.createDocument("", "", null);
15 if (xmlFile.load){
16 xmlFile.load("site.xml");
17 stylesheet.load("web/site.xsl");
18 } else {
19 alert("Document could not be loaded by browser.");
20 }
21 xmlFile.addEventListener("load", transform, false);
22 stylesheet.addEventListener("load", transform, false);
23 }
24 //IE 6.0+ solution
25 else if (window.ActiveXObject) {
26 xmlFile = new ActiveXObject("msxml2.DOMDocument.3.0");
27 xmlFile.async = false;
28 xmlFile.load("site.xml");
29 stylesheet = new ActiveXObject("msxml2.FreeThreadedDOMDocument.3.0");
30 stylesheet.async = false;
31 stylesheet.load("web/site.xsl");
32 cache = new ActiveXObject("msxml2.XSLTemplate.3.0");
33 cache.stylesheet = stylesheet;
34 transformData();
35 }
36 }
37 // separate transformation function for IE 6.0+
38 function transformData(){
39 var processor = cache.createProcessor();
40 processor.input = xmlFile;
41 processor.transform();
42 data.innerHTML = processor.output;
43 }
44 // separate transformation function for NSCP 7.1+ and Mozilla 1.4.1+
45 function transform(){
46 returnval+=1;
47 if (returnval==2){
48 var processor = new XSLTProcessor();
49 processor.importStylesheet(stylesheet);
50 doc = processor.transformToDocument(xmlFile);
51 document.getElementById("data").innerHTML = doc.documentElement.innerHTML;
52 }
53 }
54</script>
55</head>
56<body onload="init();">
57<!--[insert static HTML here]-->
58<div id="data"><!-- this is where the transformed data goes --></div>
59</body>
60</html>
diff --git a/features/org.yocto.sdk.site/site.xml b/features/org.yocto.sdk.site/site.xml
new file mode 100644
index 0000000..33f36cd
--- /dev/null
+++ b/features/org.yocto.sdk.site/site.xml
@@ -0,0 +1,18 @@
1<?xml version="1.0" encoding="UTF-8"?>
2<site>
3 <description name="Yocto Project update site" url="http://yoctoproject.org/downloads/eclipse-plugin/">
4 Yocto Project update site
5 </description>
6 <feature url="features/org.yocto.sdk_@genVersion@.jar" id="org.yocto.sdk" version="@genVersion@">
7 <category name="Yocto Project ADT"/>
8 </feature>
9 <category-def name="Yocto Project ADT" label="Yocto Project ADT plug-in"/>
10 <feature url="features/org.yocto.bc_@bcgenVersion@.jar" id="org.yocto.bc" version="@bcgenVersion@">
11 <category name="Yocto Project Bitbake Commander"/>
12 </feature>
13 <category-def name="Yocto Project Bitbake Commander" label="Yocto Project Bitbake Commander plug-in"/>
14 <feature url="features/org.yocto.doc_@docGenVersion@.jar" id="org.yocto.doc" version="@docGenVersion@">
15 <category name="Yocto Project Documentation"/>
16 </feature>
17 <category-def name="Yocto Project Documentation" label="Yocto Project Documentation plug-in"/>
18</site>
diff --git a/features/org.yocto.sdk.site/web/site.css b/features/org.yocto.sdk.site/web/site.css
new file mode 100644
index 0000000..62c6f9f
--- /dev/null
+++ b/features/org.yocto.sdk.site/web/site.css
@@ -0,0 +1,12 @@
1<STYLE type="text/css">
2td.spacer {padding-bottom: 10px; padding-top: 10px;}
3.title { font-family: sans-serif; color: #99AACC;}
4.bodyText { font-family: sans-serif; font-size: 9pt; color:#000000; }
5.sub-header { font-family: sans-serif; font-style: normal; font-weight: bold; font-size: 9pt; color: white;}
6.log-text {font-family: sans-serif; font-style: normal; font-weight: lighter; font-size: 8pt; color:black;}
7.big-header { font-family: sans-serif; font-style: normal; font-weight: bold; font-size: 9pt; color: white; border-top:10px solid white;}
8.light-row {background:#FFFFFF}
9.dark-row {background:#EEEEFF}
10.header {background:#99AADD}
11#indent {word-wrap : break-word;width :300px;text-indent:10px;}
12</STYLE>
diff --git a/features/org.yocto.sdk.site/web/site.xsl b/features/org.yocto.sdk.site/web/site.xsl
new file mode 100644
index 0000000..478de48
--- /dev/null
+++ b/features/org.yocto.sdk.site/web/site.xsl
@@ -0,0 +1,214 @@
1<xsl:stylesheet version = '1.0' xmlns:xsl='http://www.w3.org/1999/XSL/Transform' xmlns:msxsl="urn:schemas-microsoft-com:xslt">
2<xsl:output method="html" encoding="UTF-8"/>
3<xsl:key name="cat" match="category" use="@name"/>
4<xsl:template match="/">
5<xsl:for-each select="site">
6 <html>
7 <head>
8 <title>org.yocto.sdk.site</title>
9 <style>@import url("web/site.css");</style>
10 </head>
11 <body>
12 <h1 class="title">org.yocto.sdk.site</h1>
13 <p class="bodyText"><xsl:value-of select="description"/></p>
14 <table width="100%" border="0" cellspacing="1" cellpadding="2">
15 <xsl:for-each select="category-def">
16 <xsl:sort select="@label" order="ascending" case-order="upper-first"/>
17 <xsl:sort select="@name" order="ascending" case-order="upper-first"/>
18 <xsl:if test="count(key('cat',@name)) != 0">
19 <tr class="header">
20 <td class="sub-header" width="30%">
21 <xsl:value-of select="@name"/>
22 </td>
23 <td class="sub-header" width="70%">
24 <xsl:value-of select="@label"/>
25 </td>
26 </tr>
27 <xsl:for-each select="key('cat',@name)">
28 <xsl:sort select="ancestor::feature//@version" order="ascending"/>
29 <xsl:sort select="ancestor::feature//@id" order="ascending" case-order="upper-first"/>
30 <tr>
31 <xsl:choose>
32 <xsl:when test="(position() mod 2 = 1)">
33 <xsl:attribute name="class">dark-row</xsl:attribute>
34 </xsl:when>
35 <xsl:otherwise>
36 <xsl:attribute name="class">light-row</xsl:attribute>
37 </xsl:otherwise>
38 </xsl:choose>
39 <td class="log-text" id="indent">
40 <xsl:choose>
41 <xsl:when test="ancestor::feature//@label">
42 <a href="{ancestor::feature//@url}"><xsl:value-of select="ancestor::feature//@label"/></a>
43 <br/>
44 <div id="indent">
45 (<xsl:value-of select="ancestor::feature//@id"/> - <xsl:value-of select="ancestor::feature//@version"/>)
46 </div>
47 </xsl:when>
48 <xsl:otherwise>
49 <a href="{ancestor::feature//@url}"><xsl:value-of select="ancestor::feature//@id"/> - <xsl:value-of select="ancestor::feature//@version"/></a>
50 </xsl:otherwise>
51 </xsl:choose>
52 <br />
53 </td>
54 <td>
55 <table>
56 <xsl:if test="ancestor::feature//@os">
57 <tr><td class="log-text" id="indent">Operating Systems:</td>
58 <td class="log-text" id="indent"><xsl:value-of select="ancestor::feature//@os"/></td>
59 </tr>
60 </xsl:if>
61 <xsl:if test="ancestor::feature//@ws">
62 <tr><td class="log-text" id="indent">Windows Systems:</td>
63 <td class="log-text" id="indent"><xsl:value-of select="ancestor::feature//@ws"/></td>
64 </tr>
65 </xsl:if>
66 <xsl:if test="ancestor::feature//@nl">
67 <tr><td class="log-text" id="indent">Languages:</td>
68 <td class="log-text" id="indent"><xsl:value-of select="ancestor::feature//@nl"/></td>
69 </tr>
70 </xsl:if>
71 <xsl:if test="ancestor::feature//@arch">
72 <tr><td class="log-text" id="indent">Architecture:</td>
73 <td class="log-text" id="indent"><xsl:value-of select="ancestor::feature//@arch"/></td>
74 </tr>
75 </xsl:if>
76 </table>
77 </td>
78 </tr>
79 </xsl:for-each>
80 <tr><td class="spacer"><br/></td><td class="spacer"><br/></td></tr>
81 </xsl:if>
82 </xsl:for-each>
83 <xsl:if test="count(feature) &gt; count(feature/category)">
84 <tr class="header">
85 <td class="sub-header" colspan="2">
86 Uncategorized
87 </td>
88 </tr>
89 </xsl:if>
90 <xsl:choose>
91 <xsl:when test="function-available('msxsl:node-set')">
92 <xsl:variable name="rtf-nodes">
93 <xsl:for-each select="feature[not(category)]">
94 <xsl:sort select="@id" order="ascending" case-order="upper-first"/>
95 <xsl:sort select="@version" order="ascending" />
96 <xsl:value-of select="."/>
97 <xsl:copy-of select="." />
98 </xsl:for-each>
99 </xsl:variable>
100 <xsl:variable name="myNodeSet" select="msxsl:node-set($rtf-nodes)/*"/>
101 <xsl:for-each select="$myNodeSet">
102 <tr>
103 <xsl:choose>
104 <xsl:when test="position() mod 2 = 1">
105 <xsl:attribute name="class">dark-row</xsl:attribute>
106 </xsl:when>
107 <xsl:otherwise>
108 <xsl:attribute name="class">light-row</xsl:attribute>
109 </xsl:otherwise>
110 </xsl:choose>
111 <td class="log-text" id="indent">
112 <xsl:choose>
113 <xsl:when test="@label">
114 <a href="{@url}"><xsl:value-of select="@label"/></a>
115 <br />
116 <div id="indent">
117 (<xsl:value-of select="@id"/> - <xsl:value-of select="@version"/>)
118 </div>
119 </xsl:when>
120 <xsl:otherwise>
121 <a href="{@url}"><xsl:value-of select="@id"/> - <xsl:value-of select="@version"/></a>
122 </xsl:otherwise>
123 </xsl:choose>
124 <br /><br />
125 </td>
126 <td>
127 <table>
128 <xsl:if test="@os">
129 <tr><td class="log-text" id="indent">Operating Systems:</td>
130 <td class="log-text" id="indent"><xsl:value-of select="@os"/></td>
131 </tr>
132 </xsl:if>
133 <xsl:if test="@ws">
134 <tr><td class="log-text" id="indent">Windows Systems:</td>
135 <td class="log-text" id="indent"><xsl:value-of select="@ws"/></td>
136 </tr>
137 </xsl:if>
138 <xsl:if test="@nl">
139 <tr><td class="log-text" id="indent">Languages:</td>
140 <td class="log-text" id="indent"><xsl:value-of select="@nl"/></td>
141 </tr>
142 </xsl:if>
143 <xsl:if test="@arch">
144 <tr><td class="log-text" id="indent">Architecture:</td>
145 <td class="log-text" id="indent"><xsl:value-of select="@arch"/></td>
146 </tr>
147 </xsl:if>
148 </table>
149 </td>
150 </tr>
151 </xsl:for-each>
152 </xsl:when>
153 <xsl:otherwise>
154 <xsl:for-each select="feature[not(category)]">
155 <xsl:sort select="@id" order="ascending" case-order="upper-first"/>
156 <xsl:sort select="@version" order="ascending" />
157 <tr>
158 <xsl:choose>
159 <xsl:when test="count(preceding-sibling::feature[not(category)]) mod 2 = 1">
160 <xsl:attribute name="class">dark-row</xsl:attribute>
161 </xsl:when>
162 <xsl:otherwise>
163 <xsl:attribute name="class">light-row</xsl:attribute>
164 </xsl:otherwise>
165 </xsl:choose>
166 <td class="log-text" id="indent">
167 <xsl:choose>
168 <xsl:when test="@label">
169 <a href="{@url}"><xsl:value-of select="@label"/></a>
170 <br />
171 <div id="indent">
172 (<xsl:value-of select="@id"/> - <xsl:value-of select="@version"/>)
173 </div>
174 </xsl:when>
175 <xsl:otherwise>
176 <a href="{@url}"><xsl:value-of select="@id"/> - <xsl:value-of select="@version"/></a>
177 </xsl:otherwise>
178 </xsl:choose>
179 <br /><br />
180 </td>
181 <td>
182 <table>
183 <xsl:if test="@os">
184 <tr><td class="log-text" id="indent">Operating Systems:</td>
185 <td class="log-text" id="indent"><xsl:value-of select="@os"/></td>
186 </tr>
187 </xsl:if>
188 <xsl:if test="@ws">
189 <tr><td class="log-text" id="indent">Windows Systems:</td>
190 <td class="log-text" id="indent"><xsl:value-of select="@ws"/></td>
191 </tr>
192 </xsl:if>
193 <xsl:if test="@nl">
194 <tr><td class="log-text" id="indent">Languages:</td>
195 <td class="log-text" id="indent"><xsl:value-of select="@nl"/></td>
196 </tr>
197 </xsl:if>
198 <xsl:if test="@arch">
199 <tr><td class="log-text" id="indent">Architecture:</td>
200 <td class="log-text" id="indent"><xsl:value-of select="@arch"/></td>
201 </tr>
202 </xsl:if>
203 </table>
204 </td>
205 </tr>
206 </xsl:for-each>
207 </xsl:otherwise>
208 </xsl:choose>
209 </table>
210 </body>
211 </html>
212</xsl:for-each>
213</xsl:template>
214</xsl:stylesheet>
diff --git a/features/org.yocto.sdk/.project b/features/org.yocto.sdk/.project
new file mode 100644
index 0000000..d4d7e2f
--- /dev/null
+++ b/features/org.yocto.sdk/.project
@@ -0,0 +1,17 @@
1<?xml version="1.0" encoding="UTF-8"?>
2<projectDescription>
3 <name>org.yocto.sdk</name>
4 <comment></comment>
5 <projects>
6 </projects>
7 <buildSpec>
8 <buildCommand>
9 <name>org.eclipse.pde.FeatureBuilder</name>
10 <arguments>
11 </arguments>
12 </buildCommand>
13 </buildSpec>
14 <natures>
15 <nature>org.eclipse.pde.FeatureNature</nature>
16 </natures>
17</projectDescription>
diff --git a/features/org.yocto.sdk/build.properties b/features/org.yocto.sdk/build.properties
new file mode 100644
index 0000000..efef74e
--- /dev/null
+++ b/features/org.yocto.sdk/build.properties
@@ -0,0 +1,6 @@
1bin.includes = feature.xml,\
2 license.html,\
3 feature.properties
4
5generate.feature@org.yocto.sdk.source=org.yocto.sdk
6
diff --git a/features/org.yocto.sdk/feature.properties b/features/org.yocto.sdk/feature.properties
new file mode 100644
index 0000000..1a2175d
--- /dev/null
+++ b/features/org.yocto.sdk/feature.properties
@@ -0,0 +1,163 @@
1###############################################################################
2# Copyright (c) 2010 Intel, Inc. and others.
3# All rights reserved. This program and the accompanying materials
4# are made available under the terms of the Eclipse Public License v1.0
5# which accompanies this distribution, and is available at
6# http://www.eclipse.org/legal/epl-v10.html
7#
8# Contributors:
9# Intel - initial implementation
10###############################################################################
11
12# "featureName" property - name of the feature
13featureName=Yocto Project ADT Plug-in
14
15# "providerName" property - name of the company that provides the feature
16providerName=yoctoproject.org
17
18# "updateSiteName" property - label for the update site
19updateSiteName=Yocto Project Update Site
20
21# "description" property - description of the feature
22description=\
23Eclipse plug-ins for developing embedded applications using Yocto Project
24
25# copyright
26copyright=\
27Copyright (c) 2010 Intel, Inc. and others. \
28All rights reserved. This program and the accompanying materials \
29are made available under the terms of the Eclipse Public License v1.0 \
30which accompanies this distribution, and is available at \
31http://www.eclipse.org/legal/epl-v10.html
32################ end of copyright property ####################################
33
34# "licenseURL" property - URL of the "Feature License"
35# do not translate value - just change to point to a locale-specific HTML page
36licenseURL=license.html
37
38# "license" property - text of the "Feature Update License"
39# should be plain text version of license agreement pointed to be "licenseURL"
40license=\
41Eclipse Foundation Software User Agreement\n\
42April 14, 2010\n\
43\n\
44Usage Of Content\n\
45\n\
46THE ECLIPSE FOUNDATION MAKES AVAILABLE SOFTWARE, DOCUMENTATION, INFORMATION AND/OR\n\
47OTHER MATERIALS FOR OPEN SOURCE PROJECTS (COLLECTIVELY "CONTENT").\n\
48USE OF THE CONTENT IS GOVERNED BY THE TERMS AND CONDITIONS OF THIS\n\
49AGREEMENT AND/OR THE TERMS AND CONDITIONS OF LICENSE AGREEMENTS OR\n\
50NOTICES INDICATED OR REFERENCED BELOW. BY USING THE CONTENT, YOU\n\
51AGREE THAT YOUR USE OF THE CONTENT IS GOVERNED BY THIS AGREEMENT\n\
52AND/OR THE TERMS AND CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS\n\
53OR NOTICES INDICATED OR REFERENCED BELOW. IF YOU DO NOT AGREE TO THE\n\
54TERMS AND CONDITIONS OF THIS AGREEMENT AND THE TERMS AND CONDITIONS\n\
55OF ANY APPLICABLE LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED\n\
56BELOW, THEN YOU MAY NOT USE THE CONTENT.\n\
57\n\
58Applicable Licenses\n\
59\n\
60Unless otherwise indicated, all Content made available by the\n\
61Eclipse Foundation is provided to you under the terms and conditions of\n\
62the Eclipse Public License Version 1.0 ("EPL"). A copy of the EPL is\n\
63provided with this Content and is also available at http://www.eclipse.org/legal/epl-v10.html.\n\
64For purposes of the EPL, "Program" will mean the Content.\n\
65\n\
66Content includes, but is not limited to, source code, object code,\n\
67documentation and other files maintained in the Eclipse Foundation source code\n\
68repository ("Repository") in software modules ("Modules") and made available\n\
69as downloadable archives ("Downloads").\n\
70\n\
71 - Content may be structured and packaged into modules to facilitate delivering,\n\
72 extending, and upgrading the Content. Typical modules may include plug-ins ("Plug-ins"),\n\
73 plug-in fragments ("Fragments"), and features ("Features").\n\
74 - Each Plug-in or Fragment may be packaged as a sub-directory or JAR (Java(TM) ARchive)\n\
75 in a directory named "plugins".\n\
76 - A Feature is a bundle of one or more Plug-ins and/or Fragments and associated material.\n\
77 Each Feature may be packaged as a sub-directory in a directory named "features".\n\
78 Within a Feature, files named "feature.xml" may contain a list of the names and version\n\
79 numbers of the Plug-ins and/or Fragments associated with that Feature.\n\
80 - Features may also include other Features ("Included Features"). Within a Feature, files\n\
81 named "feature.xml" may contain a list of the names and version numbers of Included Features.\n\
82\n\
83The terms and conditions governing Plug-ins and Fragments should be\n\
84contained in files named "about.html" ("Abouts"). The terms and\n\
85conditions governing Features and Included Features should be contained\n\
86in files named "license.html" ("Feature Licenses"). Abouts and Feature\n\
87Licenses may be located in any directory of a Download or Module\n\
88including, but not limited to the following locations:\n\
89\n\
90 - The top-level (root) directory\n\
91 - Plug-in and Fragment directories\n\
92 - Inside Plug-ins and Fragments packaged as JARs\n\
93 - Sub-directories of the directory named "src" of certain Plug-ins\n\
94 - Feature directories\n\
95\n\
96Note: if a Feature made available by the Eclipse Foundation is installed using the\n\
97Provisioning Technology (as defined below), you must agree to a license ("Feature \n\
98Update License") during the installation process. If the Feature contains\n\
99Included Features, the Feature Update License should either provide you\n\
100with the terms and conditions governing the Included Features or inform\n\
101you where you can locate them. Feature Update Licenses may be found in\n\
102the "license" property of files named "feature.properties" found within a Feature.\n\
103Such Abouts, Feature Licenses, and Feature Update Licenses contain the\n\
104terms and conditions (or references to such terms and conditions) that\n\
105govern your use of the associated Content in that directory.\n\
106\n\
107THE ABOUTS, FEATURE LICENSES, AND FEATURE UPDATE LICENSES MAY REFER\n\
108TO THE EPL OR OTHER LICENSE AGREEMENTS, NOTICES OR TERMS AND CONDITIONS.\n\
109SOME OF THESE OTHER LICENSE AGREEMENTS MAY INCLUDE (BUT ARE NOT LIMITED TO):\n\
110\n\
111 - Common Public License Version 1.0 (available at http://www.eclipse.org/legal/cpl-v10.html)\n\
112 - Apache Software License 1.1 (available at http://www.apache.org/licenses/LICENSE)\n\
113 - Apache Software License 2.0 (available at http://www.apache.org/licenses/LICENSE-2.0)\n\
114 - Metro Link Public License 1.00 (available at http://www.opengroup.org/openmotif/supporters/metrolink/license.html)\n\
115 - Mozilla Public License Version 1.1 (available at http://www.mozilla.org/MPL/MPL-1.1.html)\n\
116\n\
117IT IS YOUR OBLIGATION TO READ AND ACCEPT ALL SUCH TERMS AND CONDITIONS PRIOR\n\
118TO USE OF THE CONTENT. If no About, Feature License, or Feature Update License\n\
119is provided, please contact the Eclipse Foundation to determine what terms and conditions\n\
120govern that particular Content.\n\
121\n\
122\n\Use of Provisioning Technology\n\
123\n\
124The Eclipse Foundation makes available provisioning software, examples of which include,\n\
125but are not limited to, p2 and the Eclipse Update Manager ("Provisioning Technology") for\n\
126the purpose of allowing users to install software, documentation, information and/or\n\
127other materials (collectively "Installable Software"). This capability is provided with\n\
128the intent of allowing such users to install, extend and update Eclipse-based products.\n\
129Information about packaging Installable Software is available at\n\
130http://eclipse.org/equinox/p2/repository_packaging.html ("Specification").\n\
131\n\
132You may use Provisioning Technology to allow other parties to install Installable Software.\n\
133You shall be responsible for enabling the applicable license agreements relating to the\n\
134Installable Software to be presented to, and accepted by, the users of the Provisioning Technology\n\
135in accordance with the Specification. By using Provisioning Technology in such a manner and\n\
136making it available in accordance with the Specification, you further acknowledge your\n\
137agreement to, and the acquisition of all necessary rights to permit the following:\n\
138\n\
139 1. A series of actions may occur ("Provisioning Process") in which a user may execute\n\
140 the Provisioning Technology on a machine ("Target Machine") with the intent of installing,\n\
141 extending or updating the functionality of an Eclipse-based product.\n\
142 2. During the Provisioning Process, the Provisioning Technology may cause third party\n\
143 Installable Software or a portion thereof to be accessed and copied to the Target Machine.\n\
144 3. Pursuant to the Specification, you will provide to the user the terms and conditions that\n\
145 govern the use of the Installable Software ("Installable Software Agreement") and such\n\
146 Installable Software Agreement shall be accessed from the Target Machine in accordance\n\
147 with the Specification. Such Installable Software Agreement must inform the user of the\n\
148 terms and conditions that govern the Installable Software and must solicit acceptance by\n\
149 the end user in the manner prescribed in such Installable Software Agreement. Upon such\n\
150 indication of agreement by the user, the provisioning Technology will complete installation\n\
151 of the Installable Software.\n\
152\n\
153Cryptography\n\
154\n\
155Content may contain encryption software. The country in which you are\n\
156currently may have restrictions on the import, possession, and use,\n\
157and/or re-export to another country, of encryption software. BEFORE\n\
158using any encryption software, please check the country's laws,\n\
159regulations and policies concerning the import, possession, or use, and\n\
160re-export of encryption software, to see if this is permitted.\n\
161\n\
162Java and all Java-based trademarks are trademarks of Oracle Corporation in the United States, other countries, or both.\n
163########### end of license property ##########################################
diff --git a/features/org.yocto.sdk/feature.xml b/features/org.yocto.sdk/feature.xml
new file mode 100644
index 0000000..fe61c42
--- /dev/null
+++ b/features/org.yocto.sdk/feature.xml
@@ -0,0 +1,109 @@
1<?xml version="1.0" encoding="UTF-8"?>
2<!--
3 Copyright (c) 2011 Intel, Inc. and others.
4 All rights reserved. This program and the accompanying materials
5 are made available under the terms of the Eclipse Public License v1.0
6 which accompanies this distribution, and is available at
7 http://www.eclipse.org/legal/epl-v10.html
8
9 Contributors:
10 Intel - initial API and implementation
11 BMW Car IT - added user documentation plugin to the feature
12 -->
13<feature
14 id="org.yocto.sdk"
15 label="%featureName"
16 version="1.4.0.qualifier"
17 provider-name="%providerName">
18
19 <description>
20 %description
21 </description>
22
23 <copyright>
24 %copyright
25 </copyright>
26
27 <license url="%licenseURL">
28 %license
29 </license>
30
31 <url>
32 <update label="%updateSiteName" url="http://yoctoproject.org/downloads/eclipse-plugin/"/>
33 </url>
34
35 <includes
36 id="org.yocto.sdk.source"/>
37
38 <requires>
39 <import plugin="org.eclipse.core.runtime"/>
40 <import plugin="org.eclipse.osgi"/>
41 <import plugin="org.eclipse.ui"/>
42 <import plugin="org.eclipse.rse.core"/>
43 <import plugin="org.eclipse.rse.ui"/>
44 <import plugin="org.eclipse.rse.services"/>
45 <import plugin="org.eclipse.ui.views"/>
46 <import plugin="org.eclipse.rse.subsystems.files.core"/>
47 <import plugin="org.eclipse.rse.subsystems.processes.core"/>
48 <import plugin="org.eclipse.rse.processes.ui"/>
49 <import plugin="org.eclipse.rse.subsystems.terminals.core"/>
50 <import plugin="org.eclipse.tcf" version="1.0.0" match="greaterOrEqual"/>
51 <import plugin="org.eclipse.cdt.ui" version="5.1.2" match="greaterOrEqual"/>
52 <import plugin="org.eclipse.cdt.core" version="5.1.2" match="greaterOrEqual"/>
53 <import plugin="org.eclipse.core.resources" version="3.5.1" match="greaterOrEqual"/>
54 <import plugin="org.eclipse.debug.core" version="3.5.1" match="greaterOrEqual"/>
55 <import plugin="org.eclipse.cdt.managedbuilder.core"/>
56 <import plugin="org.eclipse.cdt.autotools.core" version="1.1.0" match="greaterOrEqual"/>
57 <import plugin="org.eclipse.cdt.autotools.ui" version="1.0.1" match="greaterOrEqual"/>
58 <import plugin="org.eclipse.cdt.managedbuilder.ui" version="5.1.0" match="greaterOrEqual"/>
59 <import plugin="org.eclipse.core.expressions" version="3.4.100" match="greaterOrEqual"/>
60 <import plugin="org.eclipse.rse.files.ui" version="3.1.1" match="greaterOrEqual"/>
61 <import plugin="org.eclipse.rse.subsystems.shells.core" version="3.1.0" match="greaterOrEqual"/>
62 <import plugin="org.eclipse.tcf.core" version="1.0.0" match="greaterOrEqual"/>
63 <import plugin="org.eclipse.cdt.launch.remote" version="2.2.0" match="greaterOrEqual"/>
64 <import plugin="org.eclipse.tm.terminal" version="3.0.1" match="greaterOrEqual"/>
65 <import plugin="org.eclipse.rse.terminals.ui" version="1.0.100" match="greaterOrEqual"/>
66 <import plugin="org.eclipse.debug.ui"/>
67 <import plugin="org.eclipse.ui.forms"/>
68 <import plugin="org.eclipse.jface.text"/>
69 <import plugin="org.eclipse.ui.editors"/>
70 <import plugin="org.eclipse.ui.ide"/>
71 <import plugin="org.eclipse.ui.console"/>
72 <import plugin="org.eclipse.core.filesystem"/>
73 </requires>
74
75 <plugin
76 id="org.yocto.sdk.ide"
77 download-size="0"
78 install-size="0"
79 version="0.0.0"
80 unpack="false"/>
81
82 <plugin
83 id="org.yocto.remote.utils"
84 download-size="0"
85 install-size="0"
86 version="0.0.0"
87 unpack="false"/>
88
89 <plugin
90 id="org.yocto.sdk.remotetools"
91 download-size="0"
92 install-size="0"
93 version="0.0.0"
94 unpack="false"/>
95
96 <plugin
97 id="org.yocto.sdk.ide.doc.user"
98 download-size="0"
99 install-size="0"
100 version="0.0.0"
101 unpack="false"/>
102
103 <plugin
104 id="org.yocto.cmake.managedbuilder"
105 download-size="0"
106 install-size="0"
107 version="0.0.0"
108 unpack="false"/>
109</feature>
diff --git a/features/org.yocto.sdk/license.html b/features/org.yocto.sdk/license.html
new file mode 100644
index 0000000..c184ca3
--- /dev/null
+++ b/features/org.yocto.sdk/license.html
@@ -0,0 +1,107 @@
1<?xml version="1.0" encoding="ISO-8859-1" ?>
2<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
3<html xmlns="http://www.w3.org/1999/xhtml">
4<head>
5<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
6<title>Eclipse Foundation Software User Agreement</title>
7</head>
8
9<body lang="EN-US">
10<h2>Eclipse Foundation Software User Agreement</h2>
11<p>April 14, 2010</p>
12
13<h3>Usage Of Content</h3>
14
15<p>THE ECLIPSE FOUNDATION MAKES AVAILABLE SOFTWARE, DOCUMENTATION, INFORMATION AND/OR OTHER MATERIALS FOR OPEN SOURCE PROJECTS
16 (COLLECTIVELY &quot;CONTENT&quot;). USE OF THE CONTENT IS GOVERNED BY THE TERMS AND CONDITIONS OF THIS AGREEMENT AND/OR THE TERMS AND
17 CONDITIONS OF LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW. BY USING THE CONTENT, YOU AGREE THAT YOUR USE
18 OF THE CONTENT IS GOVERNED BY THIS AGREEMENT AND/OR THE TERMS AND CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS OR
19 NOTICES INDICATED OR REFERENCED BELOW. IF YOU DO NOT AGREE TO THE TERMS AND CONDITIONS OF THIS AGREEMENT AND THE TERMS AND
20 CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW, THEN YOU MAY NOT USE THE CONTENT.</p>
21
22<h3>Applicable Licenses</h3>
23
24<p>Unless otherwise indicated, all Content made available by the Eclipse Foundation is provided to you under the terms and conditions of the Eclipse Public License Version 1.0
25 (&quot;EPL&quot;). A copy of the EPL is provided with this Content and is also available at <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>.
26 For purposes of the EPL, &quot;Program&quot; will mean the Content.</p>
27
28<p>Content includes, but is not limited to, source code, object code, documentation and other files maintained in the Eclipse Foundation source code
29 repository (&quot;Repository&quot;) in software modules (&quot;Modules&quot;) and made available as downloadable archives (&quot;Downloads&quot;).</p>
30
31<ul>
32 <li>Content may be structured and packaged into modules to facilitate delivering, extending, and upgrading the Content. Typical modules may include plug-ins (&quot;Plug-ins&quot;), plug-in fragments (&quot;Fragments&quot;), and features (&quot;Features&quot;).</li>
33 <li>Each Plug-in or Fragment may be packaged as a sub-directory or JAR (Java&trade; ARchive) in a directory named &quot;plugins&quot;.</li>
34 <li>A Feature is a bundle of one or more Plug-ins and/or Fragments and associated material. Each Feature may be packaged as a sub-directory in a directory named &quot;features&quot;. Within a Feature, files named &quot;feature.xml&quot; may contain a list of the names and version numbers of the Plug-ins
35 and/or Fragments associated with that Feature.</li>
36 <li>Features may also include other Features (&quot;Included Features&quot;). Within a Feature, files named &quot;feature.xml&quot; may contain a list of the names and version numbers of Included Features.</li>
37</ul>
38
39<p>The terms and conditions governing Plug-ins and Fragments should be contained in files named &quot;about.html&quot; (&quot;Abouts&quot;). The terms and conditions governing Features and
40Included Features should be contained in files named &quot;license.html&quot; (&quot;Feature Licenses&quot;). Abouts and Feature Licenses may be located in any directory of a Download or Module
41including, but not limited to the following locations:</p>
42
43<ul>
44 <li>The top-level (root) directory</li>
45 <li>Plug-in and Fragment directories</li>
46 <li>Inside Plug-ins and Fragments packaged as JARs</li>
47 <li>Sub-directories of the directory named &quot;src&quot; of certain Plug-ins</li>
48 <li>Feature directories</li>
49</ul>
50
51<p>Note: if a Feature made available by the Eclipse Foundation is installed using the Provisioning Technology (as defined below), you must agree to a license (&quot;Feature Update License&quot;) during the
52installation process. If the Feature contains Included Features, the Feature Update License should either provide you with the terms and conditions governing the Included Features or
53inform you where you can locate them. Feature Update Licenses may be found in the &quot;license&quot; property of files named &quot;feature.properties&quot; found within a Feature.
54Such Abouts, Feature Licenses, and Feature Update Licenses contain the terms and conditions (or references to such terms and conditions) that govern your use of the associated Content in
55that directory.</p>
56
57<p>THE ABOUTS, FEATURE LICENSES, AND FEATURE UPDATE LICENSES MAY REFER TO THE EPL OR OTHER LICENSE AGREEMENTS, NOTICES OR TERMS AND CONDITIONS. SOME OF THESE
58OTHER LICENSE AGREEMENTS MAY INCLUDE (BUT ARE NOT LIMITED TO):</p>
59
60<ul>
61 <li>Common Public License Version 1.0 (available at <a href="http://www.eclipse.org/legal/cpl-v10.html">http://www.eclipse.org/legal/cpl-v10.html</a>)</li>
62 <li>Apache Software License 1.1 (available at <a href="http://www.apache.org/licenses/LICENSE">http://www.apache.org/licenses/LICENSE</a>)</li>
63 <li>Apache Software License 2.0 (available at <a href="http://www.apache.org/licenses/LICENSE-2.0">http://www.apache.org/licenses/LICENSE-2.0</a>)</li>
64 <li>Metro Link Public License 1.00 (available at <a href="http://www.opengroup.org/openmotif/supporters/metrolink/license.html">http://www.opengroup.org/openmotif/supporters/metrolink/license.html</a>)</li>
65 <li>Mozilla Public License Version 1.1 (available at <a href="http://www.mozilla.org/MPL/MPL-1.1.html">http://www.mozilla.org/MPL/MPL-1.1.html</a>)</li>
66</ul>
67
68<p>IT IS YOUR OBLIGATION TO READ AND ACCEPT ALL SUCH TERMS AND CONDITIONS PRIOR TO USE OF THE CONTENT. If no About, Feature License, or Feature Update License is provided, please
69contact the Eclipse Foundation to determine what terms and conditions govern that particular Content.</p>
70
71
72<h3>Use of Provisioning Technology</h3>
73
74<p>The Eclipse Foundation makes available provisioning software, examples of which include, but are not limited to, p2 and the Eclipse
75 Update Manager (&quot;Provisioning Technology&quot;) for the purpose of allowing users to install software, documentation, information and/or
76 other materials (collectively &quot;Installable Software&quot;). This capability is provided with the intent of allowing such users to
77 install, extend and update Eclipse-based products. Information about packaging Installable Software is available at <a
78 href="http://eclipse.org/equinox/p2/repository_packaging.html">http://eclipse.org/equinox/p2/repository_packaging.html</a>
79 (&quot;Specification&quot;).</p>
80
81<p>You may use Provisioning Technology to allow other parties to install Installable Software. You shall be responsible for enabling the
82 applicable license agreements relating to the Installable Software to be presented to, and accepted by, the users of the Provisioning Technology
83 in accordance with the Specification. By using Provisioning Technology in such a manner and making it available in accordance with the
84 Specification, you further acknowledge your agreement to, and the acquisition of all necessary rights to permit the following:</p>
85
86<ol>
87 <li>A series of actions may occur (&quot;Provisioning Process&quot;) in which a user may execute the Provisioning Technology
88 on a machine (&quot;Target Machine&quot;) with the intent of installing, extending or updating the functionality of an Eclipse-based
89 product.</li>
90 <li>During the Provisioning Process, the Provisioning Technology may cause third party Installable Software or a portion thereof to be
91 accessed and copied to the Target Machine.</li>
92 <li>Pursuant to the Specification, you will provide to the user the terms and conditions that govern the use of the Installable
93 Software (&quot;Installable Software Agreement&quot;) and such Installable Software Agreement shall be accessed from the Target
94 Machine in accordance with the Specification. Such Installable Software Agreement must inform the user of the terms and conditions that govern
95 the Installable Software and must solicit acceptance by the end user in the manner prescribed in such Installable Software Agreement. Upon such
96 indication of agreement by the user, the provisioning Technology will complete installation of the Installable Software.</li>
97</ol>
98
99<h3>Cryptography</h3>
100
101<p>Content may contain encryption software. The country in which you are currently may have restrictions on the import, possession, and use, and/or re-export to
102 another country, of encryption software. BEFORE using any encryption software, please check the country's laws, regulations and policies concerning the import,
103 possession, or use, and re-export of encryption software, to see if this is permitted.</p>
104
105<p><small>Java and all Java-based trademarks are trademarks of Oracle Corporation in the United States, other countries, or both.</small></p>
106</body>
107</html>
diff --git a/features/org.yocto.sdk/sourceTemplateFeature/feature.properties b/features/org.yocto.sdk/sourceTemplateFeature/feature.properties
new file mode 100644
index 0000000..f0519b3
--- /dev/null
+++ b/features/org.yocto.sdk/sourceTemplateFeature/feature.properties
@@ -0,0 +1,163 @@
1###############################################################################
2# Copyright (c) 2011 Intel, Inc. and others.
3# All rights reserved. This program and the accompanying materials
4# are made available under the terms of the Eclipse Public License v1.0
5# which accompanies this distribution, and is available at
6# http://www.eclipse.org/legal/epl-v10.html
7#
8# Contributors:
9# Intel - initial implementation
10###############################################################################
11
12# "featureName" property - name of the feature
13featureName=Yocto Project ADT Plug-in - Source
14
15# "providerName" property - name of the company that provides the feature
16providerName=yoctoproject.org
17
18# "updateSiteName" property - label for the update site
19updateSiteName=Yocto Project Update Site
20
21# "description" property - description of the feature
22description=\
23Eclipse plug-ins for developing embedded applications using Yocto Project
24
25# copyright
26copyright=\
27Copyright (c) 2011 Intel, Inc. and others. \
28All rights reserved. This program and the accompanying materials \
29are made available under the terms of the Eclipse Public License v1.0 \
30which accompanies this distribution, and is available at \
31http://www.eclipse.org/legal/epl-v10.html
32################ end of copyright property ####################################
33
34# "licenseURL" property - URL of the "Feature License"
35# do not translate value - just change to point to a locale-specific HTML page
36licenseURL=license.html
37
38# "license" property - text of the "Feature Update License"
39# should be plain text version of license agreement pointed to be "licenseURL"
40license=\
41Eclipse Foundation Software User Agreement\n\
42April 14, 2010\n\
43\n\
44Usage Of Content\n\
45\n\
46THE ECLIPSE FOUNDATION MAKES AVAILABLE SOFTWARE, DOCUMENTATION, INFORMATION AND/OR\n\
47OTHER MATERIALS FOR OPEN SOURCE PROJECTS (COLLECTIVELY "CONTENT").\n\
48USE OF THE CONTENT IS GOVERNED BY THE TERMS AND CONDITIONS OF THIS\n\
49AGREEMENT AND/OR THE TERMS AND CONDITIONS OF LICENSE AGREEMENTS OR\n\
50NOTICES INDICATED OR REFERENCED BELOW. BY USING THE CONTENT, YOU\n\
51AGREE THAT YOUR USE OF THE CONTENT IS GOVERNED BY THIS AGREEMENT\n\
52AND/OR THE TERMS AND CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS\n\
53OR NOTICES INDICATED OR REFERENCED BELOW. IF YOU DO NOT AGREE TO THE\n\
54TERMS AND CONDITIONS OF THIS AGREEMENT AND THE TERMS AND CONDITIONS\n\
55OF ANY APPLICABLE LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED\n\
56BELOW, THEN YOU MAY NOT USE THE CONTENT.\n\
57\n\
58Applicable Licenses\n\
59\n\
60Unless otherwise indicated, all Content made available by the\n\
61Eclipse Foundation is provided to you under the terms and conditions of\n\
62the Eclipse Public License Version 1.0 ("EPL"). A copy of the EPL is\n\
63provided with this Content and is also available at http://www.eclipse.org/legal/epl-v10.html.\n\
64For purposes of the EPL, "Program" will mean the Content.\n\
65\n\
66Content includes, but is not limited to, source code, object code,\n\
67documentation and other files maintained in the Eclipse Foundation source code\n\
68repository ("Repository") in software modules ("Modules") and made available\n\
69as downloadable archives ("Downloads").\n\
70\n\
71 - Content may be structured and packaged into modules to facilitate delivering,\n\
72 extending, and upgrading the Content. Typical modules may include plug-ins ("Plug-ins"),\n\
73 plug-in fragments ("Fragments"), and features ("Features").\n\
74 - Each Plug-in or Fragment may be packaged as a sub-directory or JAR (Java(TM) ARchive)\n\
75 in a directory named "plugins".\n\
76 - A Feature is a bundle of one or more Plug-ins and/or Fragments and associated material.\n\
77 Each Feature may be packaged as a sub-directory in a directory named "features".\n\
78 Within a Feature, files named "feature.xml" may contain a list of the names and version\n\
79 numbers of the Plug-ins and/or Fragments associated with that Feature.\n\
80 - Features may also include other Features ("Included Features"). Within a Feature, files\n\
81 named "feature.xml" may contain a list of the names and version numbers of Included Features.\n\
82\n\
83The terms and conditions governing Plug-ins and Fragments should be\n\
84contained in files named "about.html" ("Abouts"). The terms and\n\
85conditions governing Features and Included Features should be contained\n\
86in files named "license.html" ("Feature Licenses"). Abouts and Feature\n\
87Licenses may be located in any directory of a Download or Module\n\
88including, but not limited to the following locations:\n\
89\n\
90 - The top-level (root) directory\n\
91 - Plug-in and Fragment directories\n\
92 - Inside Plug-ins and Fragments packaged as JARs\n\
93 - Sub-directories of the directory named "src" of certain Plug-ins\n\
94 - Feature directories\n\
95\n\
96Note: if a Feature made available by the Eclipse Foundation is installed using the\n\
97Provisioning Technology (as defined below), you must agree to a license ("Feature \n\
98Update License") during the installation process. If the Feature contains\n\
99Included Features, the Feature Update License should either provide you\n\
100with the terms and conditions governing the Included Features or inform\n\
101you where you can locate them. Feature Update Licenses may be found in\n\
102the "license" property of files named "feature.properties" found within a Feature.\n\
103Such Abouts, Feature Licenses, and Feature Update Licenses contain the\n\
104terms and conditions (or references to such terms and conditions) that\n\
105govern your use of the associated Content in that directory.\n\
106\n\
107THE ABOUTS, FEATURE LICENSES, AND FEATURE UPDATE LICENSES MAY REFER\n\
108TO THE EPL OR OTHER LICENSE AGREEMENTS, NOTICES OR TERMS AND CONDITIONS.\n\
109SOME OF THESE OTHER LICENSE AGREEMENTS MAY INCLUDE (BUT ARE NOT LIMITED TO):\n\
110\n\
111 - Common Public License Version 1.0 (available at http://www.eclipse.org/legal/cpl-v10.html)\n\
112 - Apache Software License 1.1 (available at http://www.apache.org/licenses/LICENSE)\n\
113 - Apache Software License 2.0 (available at http://www.apache.org/licenses/LICENSE-2.0)\n\
114 - Metro Link Public License 1.00 (available at http://www.opengroup.org/openmotif/supporters/metrolink/license.html)\n\
115 - Mozilla Public License Version 1.1 (available at http://www.mozilla.org/MPL/MPL-1.1.html)\n\
116\n\
117IT IS YOUR OBLIGATION TO READ AND ACCEPT ALL SUCH TERMS AND CONDITIONS PRIOR\n\
118TO USE OF THE CONTENT. If no About, Feature License, or Feature Update License\n\
119is provided, please contact the Eclipse Foundation to determine what terms and conditions\n\
120govern that particular Content.\n\
121\n\
122\n\Use of Provisioning Technology\n\
123\n\
124The Eclipse Foundation makes available provisioning software, examples of which include,\n\
125but are not limited to, p2 and the Eclipse Update Manager ("Provisioning Technology") for\n\
126the purpose of allowing users to install software, documentation, information and/or\n\
127other materials (collectively "Installable Software"). This capability is provided with\n\
128the intent of allowing such users to install, extend and update Eclipse-based products.\n\
129Information about packaging Installable Software is available at\n\
130http://eclipse.org/equinox/p2/repository_packaging.html ("Specification").\n\
131\n\
132You may use Provisioning Technology to allow other parties to install Installable Software.\n\
133You shall be responsible for enabling the applicable license agreements relating to the\n\
134Installable Software to be presented to, and accepted by, the users of the Provisioning Technology\n\
135in accordance with the Specification. By using Provisioning Technology in such a manner and\n\
136making it available in accordance with the Specification, you further acknowledge your\n\
137agreement to, and the acquisition of all necessary rights to permit the following:\n\
138\n\
139 1. A series of actions may occur ("Provisioning Process") in which a user may execute\n\
140 the Provisioning Technology on a machine ("Target Machine") with the intent of installing,\n\
141 extending or updating the functionality of an Eclipse-based product.\n\
142 2. During the Provisioning Process, the Provisioning Technology may cause third party\n\
143 Installable Software or a portion thereof to be accessed and copied to the Target Machine.\n\
144 3. Pursuant to the Specification, you will provide to the user the terms and conditions that\n\
145 govern the use of the Installable Software ("Installable Software Agreement") and such\n\
146 Installable Software Agreement shall be accessed from the Target Machine in accordance\n\
147 with the Specification. Such Installable Software Agreement must inform the user of the\n\
148 terms and conditions that govern the Installable Software and must solicit acceptance by\n\
149 the end user in the manner prescribed in such Installable Software Agreement. Upon such\n\
150 indication of agreement by the user, the provisioning Technology will complete installation\n\
151 of the Installable Software.\n\
152\n\
153Cryptography\n\
154\n\
155Content may contain encryption software. The country in which you are\n\
156currently may have restrictions on the import, possession, and use,\n\
157and/or re-export to another country, of encryption software. BEFORE\n\
158using any encryption software, please check the country's laws,\n\
159regulations and policies concerning the import, possession, or use, and\n\
160re-export of encryption software, to see if this is permitted.\n\
161\n\
162Java and all Java-based trademarks are trademarks of Oracle Corporation in the United States, other countries, or both.\n
163########### end of license property ##########################################
diff --git a/features/org.yocto.sdk/sourceTemplateFeature/license.html b/features/org.yocto.sdk/sourceTemplateFeature/license.html
new file mode 100644
index 0000000..c184ca3
--- /dev/null
+++ b/features/org.yocto.sdk/sourceTemplateFeature/license.html
@@ -0,0 +1,107 @@
1<?xml version="1.0" encoding="ISO-8859-1" ?>
2<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
3<html xmlns="http://www.w3.org/1999/xhtml">
4<head>
5<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
6<title>Eclipse Foundation Software User Agreement</title>
7</head>
8
9<body lang="EN-US">
10<h2>Eclipse Foundation Software User Agreement</h2>
11<p>April 14, 2010</p>
12
13<h3>Usage Of Content</h3>
14
15<p>THE ECLIPSE FOUNDATION MAKES AVAILABLE SOFTWARE, DOCUMENTATION, INFORMATION AND/OR OTHER MATERIALS FOR OPEN SOURCE PROJECTS
16 (COLLECTIVELY &quot;CONTENT&quot;). USE OF THE CONTENT IS GOVERNED BY THE TERMS AND CONDITIONS OF THIS AGREEMENT AND/OR THE TERMS AND
17 CONDITIONS OF LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW. BY USING THE CONTENT, YOU AGREE THAT YOUR USE
18 OF THE CONTENT IS GOVERNED BY THIS AGREEMENT AND/OR THE TERMS AND CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS OR
19 NOTICES INDICATED OR REFERENCED BELOW. IF YOU DO NOT AGREE TO THE TERMS AND CONDITIONS OF THIS AGREEMENT AND THE TERMS AND
20 CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW, THEN YOU MAY NOT USE THE CONTENT.</p>
21
22<h3>Applicable Licenses</h3>
23
24<p>Unless otherwise indicated, all Content made available by the Eclipse Foundation is provided to you under the terms and conditions of the Eclipse Public License Version 1.0
25 (&quot;EPL&quot;). A copy of the EPL is provided with this Content and is also available at <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>.
26 For purposes of the EPL, &quot;Program&quot; will mean the Content.</p>
27
28<p>Content includes, but is not limited to, source code, object code, documentation and other files maintained in the Eclipse Foundation source code
29 repository (&quot;Repository&quot;) in software modules (&quot;Modules&quot;) and made available as downloadable archives (&quot;Downloads&quot;).</p>
30
31<ul>
32 <li>Content may be structured and packaged into modules to facilitate delivering, extending, and upgrading the Content. Typical modules may include plug-ins (&quot;Plug-ins&quot;), plug-in fragments (&quot;Fragments&quot;), and features (&quot;Features&quot;).</li>
33 <li>Each Plug-in or Fragment may be packaged as a sub-directory or JAR (Java&trade; ARchive) in a directory named &quot;plugins&quot;.</li>
34 <li>A Feature is a bundle of one or more Plug-ins and/or Fragments and associated material. Each Feature may be packaged as a sub-directory in a directory named &quot;features&quot;. Within a Feature, files named &quot;feature.xml&quot; may contain a list of the names and version numbers of the Plug-ins
35 and/or Fragments associated with that Feature.</li>
36 <li>Features may also include other Features (&quot;Included Features&quot;). Within a Feature, files named &quot;feature.xml&quot; may contain a list of the names and version numbers of Included Features.</li>
37</ul>
38
39<p>The terms and conditions governing Plug-ins and Fragments should be contained in files named &quot;about.html&quot; (&quot;Abouts&quot;). The terms and conditions governing Features and
40Included Features should be contained in files named &quot;license.html&quot; (&quot;Feature Licenses&quot;). Abouts and Feature Licenses may be located in any directory of a Download or Module
41including, but not limited to the following locations:</p>
42
43<ul>
44 <li>The top-level (root) directory</li>
45 <li>Plug-in and Fragment directories</li>
46 <li>Inside Plug-ins and Fragments packaged as JARs</li>
47 <li>Sub-directories of the directory named &quot;src&quot; of certain Plug-ins</li>
48 <li>Feature directories</li>
49</ul>
50
51<p>Note: if a Feature made available by the Eclipse Foundation is installed using the Provisioning Technology (as defined below), you must agree to a license (&quot;Feature Update License&quot;) during the
52installation process. If the Feature contains Included Features, the Feature Update License should either provide you with the terms and conditions governing the Included Features or
53inform you where you can locate them. Feature Update Licenses may be found in the &quot;license&quot; property of files named &quot;feature.properties&quot; found within a Feature.
54Such Abouts, Feature Licenses, and Feature Update Licenses contain the terms and conditions (or references to such terms and conditions) that govern your use of the associated Content in
55that directory.</p>
56
57<p>THE ABOUTS, FEATURE LICENSES, AND FEATURE UPDATE LICENSES MAY REFER TO THE EPL OR OTHER LICENSE AGREEMENTS, NOTICES OR TERMS AND CONDITIONS. SOME OF THESE
58OTHER LICENSE AGREEMENTS MAY INCLUDE (BUT ARE NOT LIMITED TO):</p>
59
60<ul>
61 <li>Common Public License Version 1.0 (available at <a href="http://www.eclipse.org/legal/cpl-v10.html">http://www.eclipse.org/legal/cpl-v10.html</a>)</li>
62 <li>Apache Software License 1.1 (available at <a href="http://www.apache.org/licenses/LICENSE">http://www.apache.org/licenses/LICENSE</a>)</li>
63 <li>Apache Software License 2.0 (available at <a href="http://www.apache.org/licenses/LICENSE-2.0">http://www.apache.org/licenses/LICENSE-2.0</a>)</li>
64 <li>Metro Link Public License 1.00 (available at <a href="http://www.opengroup.org/openmotif/supporters/metrolink/license.html">http://www.opengroup.org/openmotif/supporters/metrolink/license.html</a>)</li>
65 <li>Mozilla Public License Version 1.1 (available at <a href="http://www.mozilla.org/MPL/MPL-1.1.html">http://www.mozilla.org/MPL/MPL-1.1.html</a>)</li>
66</ul>
67
68<p>IT IS YOUR OBLIGATION TO READ AND ACCEPT ALL SUCH TERMS AND CONDITIONS PRIOR TO USE OF THE CONTENT. If no About, Feature License, or Feature Update License is provided, please
69contact the Eclipse Foundation to determine what terms and conditions govern that particular Content.</p>
70
71
72<h3>Use of Provisioning Technology</h3>
73
74<p>The Eclipse Foundation makes available provisioning software, examples of which include, but are not limited to, p2 and the Eclipse
75 Update Manager (&quot;Provisioning Technology&quot;) for the purpose of allowing users to install software, documentation, information and/or
76 other materials (collectively &quot;Installable Software&quot;). This capability is provided with the intent of allowing such users to
77 install, extend and update Eclipse-based products. Information about packaging Installable Software is available at <a
78 href="http://eclipse.org/equinox/p2/repository_packaging.html">http://eclipse.org/equinox/p2/repository_packaging.html</a>
79 (&quot;Specification&quot;).</p>
80
81<p>You may use Provisioning Technology to allow other parties to install Installable Software. You shall be responsible for enabling the
82 applicable license agreements relating to the Installable Software to be presented to, and accepted by, the users of the Provisioning Technology
83 in accordance with the Specification. By using Provisioning Technology in such a manner and making it available in accordance with the
84 Specification, you further acknowledge your agreement to, and the acquisition of all necessary rights to permit the following:</p>
85
86<ol>
87 <li>A series of actions may occur (&quot;Provisioning Process&quot;) in which a user may execute the Provisioning Technology
88 on a machine (&quot;Target Machine&quot;) with the intent of installing, extending or updating the functionality of an Eclipse-based
89 product.</li>
90 <li>During the Provisioning Process, the Provisioning Technology may cause third party Installable Software or a portion thereof to be
91 accessed and copied to the Target Machine.</li>
92 <li>Pursuant to the Specification, you will provide to the user the terms and conditions that govern the use of the Installable
93 Software (&quot;Installable Software Agreement&quot;) and such Installable Software Agreement shall be accessed from the Target
94 Machine in accordance with the Specification. Such Installable Software Agreement must inform the user of the terms and conditions that govern
95 the Installable Software and must solicit acceptance by the end user in the manner prescribed in such Installable Software Agreement. Upon such
96 indication of agreement by the user, the provisioning Technology will complete installation of the Installable Software.</li>
97</ol>
98
99<h3>Cryptography</h3>
100
101<p>Content may contain encryption software. The country in which you are currently may have restrictions on the import, possession, and use, and/or re-export to
102 another country, of encryption software. BEFORE using any encryption software, please check the country's laws, regulations and policies concerning the import,
103 possession, or use, and re-export of encryption software, to see if this is permitted.</p>
104
105<p><small>Java and all Java-based trademarks are trademarks of Oracle Corporation in the United States, other countries, or both.</small></p>
106</body>
107</html>
diff --git a/features/org.yocto.sdk/sourceTemplatePlugin/license.html b/features/org.yocto.sdk/sourceTemplatePlugin/license.html
new file mode 100644
index 0000000..c184ca3
--- /dev/null
+++ b/features/org.yocto.sdk/sourceTemplatePlugin/license.html
@@ -0,0 +1,107 @@
1<?xml version="1.0" encoding="ISO-8859-1" ?>
2<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
3<html xmlns="http://www.w3.org/1999/xhtml">
4<head>
5<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
6<title>Eclipse Foundation Software User Agreement</title>
7</head>
8
9<body lang="EN-US">
10<h2>Eclipse Foundation Software User Agreement</h2>
11<p>April 14, 2010</p>
12
13<h3>Usage Of Content</h3>
14
15<p>THE ECLIPSE FOUNDATION MAKES AVAILABLE SOFTWARE, DOCUMENTATION, INFORMATION AND/OR OTHER MATERIALS FOR OPEN SOURCE PROJECTS
16 (COLLECTIVELY &quot;CONTENT&quot;). USE OF THE CONTENT IS GOVERNED BY THE TERMS AND CONDITIONS OF THIS AGREEMENT AND/OR THE TERMS AND
17 CONDITIONS OF LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW. BY USING THE CONTENT, YOU AGREE THAT YOUR USE
18 OF THE CONTENT IS GOVERNED BY THIS AGREEMENT AND/OR THE TERMS AND CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS OR
19 NOTICES INDICATED OR REFERENCED BELOW. IF YOU DO NOT AGREE TO THE TERMS AND CONDITIONS OF THIS AGREEMENT AND THE TERMS AND
20 CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW, THEN YOU MAY NOT USE THE CONTENT.</p>
21
22<h3>Applicable Licenses</h3>
23
24<p>Unless otherwise indicated, all Content made available by the Eclipse Foundation is provided to you under the terms and conditions of the Eclipse Public License Version 1.0
25 (&quot;EPL&quot;). A copy of the EPL is provided with this Content and is also available at <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>.
26 For purposes of the EPL, &quot;Program&quot; will mean the Content.</p>
27
28<p>Content includes, but is not limited to, source code, object code, documentation and other files maintained in the Eclipse Foundation source code
29 repository (&quot;Repository&quot;) in software modules (&quot;Modules&quot;) and made available as downloadable archives (&quot;Downloads&quot;).</p>
30
31<ul>
32 <li>Content may be structured and packaged into modules to facilitate delivering, extending, and upgrading the Content. Typical modules may include plug-ins (&quot;Plug-ins&quot;), plug-in fragments (&quot;Fragments&quot;), and features (&quot;Features&quot;).</li>
33 <li>Each Plug-in or Fragment may be packaged as a sub-directory or JAR (Java&trade; ARchive) in a directory named &quot;plugins&quot;.</li>
34 <li>A Feature is a bundle of one or more Plug-ins and/or Fragments and associated material. Each Feature may be packaged as a sub-directory in a directory named &quot;features&quot;. Within a Feature, files named &quot;feature.xml&quot; may contain a list of the names and version numbers of the Plug-ins
35 and/or Fragments associated with that Feature.</li>
36 <li>Features may also include other Features (&quot;Included Features&quot;). Within a Feature, files named &quot;feature.xml&quot; may contain a list of the names and version numbers of Included Features.</li>
37</ul>
38
39<p>The terms and conditions governing Plug-ins and Fragments should be contained in files named &quot;about.html&quot; (&quot;Abouts&quot;). The terms and conditions governing Features and
40Included Features should be contained in files named &quot;license.html&quot; (&quot;Feature Licenses&quot;). Abouts and Feature Licenses may be located in any directory of a Download or Module
41including, but not limited to the following locations:</p>
42
43<ul>
44 <li>The top-level (root) directory</li>
45 <li>Plug-in and Fragment directories</li>
46 <li>Inside Plug-ins and Fragments packaged as JARs</li>
47 <li>Sub-directories of the directory named &quot;src&quot; of certain Plug-ins</li>
48 <li>Feature directories</li>
49</ul>
50
51<p>Note: if a Feature made available by the Eclipse Foundation is installed using the Provisioning Technology (as defined below), you must agree to a license (&quot;Feature Update License&quot;) during the
52installation process. If the Feature contains Included Features, the Feature Update License should either provide you with the terms and conditions governing the Included Features or
53inform you where you can locate them. Feature Update Licenses may be found in the &quot;license&quot; property of files named &quot;feature.properties&quot; found within a Feature.
54Such Abouts, Feature Licenses, and Feature Update Licenses contain the terms and conditions (or references to such terms and conditions) that govern your use of the associated Content in
55that directory.</p>
56
57<p>THE ABOUTS, FEATURE LICENSES, AND FEATURE UPDATE LICENSES MAY REFER TO THE EPL OR OTHER LICENSE AGREEMENTS, NOTICES OR TERMS AND CONDITIONS. SOME OF THESE
58OTHER LICENSE AGREEMENTS MAY INCLUDE (BUT ARE NOT LIMITED TO):</p>
59
60<ul>
61 <li>Common Public License Version 1.0 (available at <a href="http://www.eclipse.org/legal/cpl-v10.html">http://www.eclipse.org/legal/cpl-v10.html</a>)</li>
62 <li>Apache Software License 1.1 (available at <a href="http://www.apache.org/licenses/LICENSE">http://www.apache.org/licenses/LICENSE</a>)</li>
63 <li>Apache Software License 2.0 (available at <a href="http://www.apache.org/licenses/LICENSE-2.0">http://www.apache.org/licenses/LICENSE-2.0</a>)</li>
64 <li>Metro Link Public License 1.00 (available at <a href="http://www.opengroup.org/openmotif/supporters/metrolink/license.html">http://www.opengroup.org/openmotif/supporters/metrolink/license.html</a>)</li>
65 <li>Mozilla Public License Version 1.1 (available at <a href="http://www.mozilla.org/MPL/MPL-1.1.html">http://www.mozilla.org/MPL/MPL-1.1.html</a>)</li>
66</ul>
67
68<p>IT IS YOUR OBLIGATION TO READ AND ACCEPT ALL SUCH TERMS AND CONDITIONS PRIOR TO USE OF THE CONTENT. If no About, Feature License, or Feature Update License is provided, please
69contact the Eclipse Foundation to determine what terms and conditions govern that particular Content.</p>
70
71
72<h3>Use of Provisioning Technology</h3>
73
74<p>The Eclipse Foundation makes available provisioning software, examples of which include, but are not limited to, p2 and the Eclipse
75 Update Manager (&quot;Provisioning Technology&quot;) for the purpose of allowing users to install software, documentation, information and/or
76 other materials (collectively &quot;Installable Software&quot;). This capability is provided with the intent of allowing such users to
77 install, extend and update Eclipse-based products. Information about packaging Installable Software is available at <a
78 href="http://eclipse.org/equinox/p2/repository_packaging.html">http://eclipse.org/equinox/p2/repository_packaging.html</a>
79 (&quot;Specification&quot;).</p>
80
81<p>You may use Provisioning Technology to allow other parties to install Installable Software. You shall be responsible for enabling the
82 applicable license agreements relating to the Installable Software to be presented to, and accepted by, the users of the Provisioning Technology
83 in accordance with the Specification. By using Provisioning Technology in such a manner and making it available in accordance with the
84 Specification, you further acknowledge your agreement to, and the acquisition of all necessary rights to permit the following:</p>
85
86<ol>
87 <li>A series of actions may occur (&quot;Provisioning Process&quot;) in which a user may execute the Provisioning Technology
88 on a machine (&quot;Target Machine&quot;) with the intent of installing, extending or updating the functionality of an Eclipse-based
89 product.</li>
90 <li>During the Provisioning Process, the Provisioning Technology may cause third party Installable Software or a portion thereof to be
91 accessed and copied to the Target Machine.</li>
92 <li>Pursuant to the Specification, you will provide to the user the terms and conditions that govern the use of the Installable
93 Software (&quot;Installable Software Agreement&quot;) and such Installable Software Agreement shall be accessed from the Target
94 Machine in accordance with the Specification. Such Installable Software Agreement must inform the user of the terms and conditions that govern
95 the Installable Software and must solicit acceptance by the end user in the manner prescribed in such Installable Software Agreement. Upon such
96 indication of agreement by the user, the provisioning Technology will complete installation of the Installable Software.</li>
97</ol>
98
99<h3>Cryptography</h3>
100
101<p>Content may contain encryption software. The country in which you are currently may have restrictions on the import, possession, and use, and/or re-export to
102 another country, of encryption software. BEFORE using any encryption software, please check the country's laws, regulations and policies concerning the import,
103 possession, or use, and re-export of encryption software, to see if this is permitted.</p>
104
105<p><small>Java and all Java-based trademarks are trademarks of Oracle Corporation in the United States, other countries, or both.</small></p>
106</body>
107</html>
diff --git a/features/org.yocto.sdk/sourceTemplatePlugin/plugin.properties b/features/org.yocto.sdk/sourceTemplatePlugin/plugin.properties
new file mode 100644
index 0000000..91baf99
--- /dev/null
+++ b/features/org.yocto.sdk/sourceTemplatePlugin/plugin.properties
@@ -0,0 +1,163 @@
1###############################################################################
2# Copyright (c) 2011 Intel, Inc. and others.
3# All rights reserved. This program and the accompanying materials
4# are made available under the terms of the Eclipse Public License v1.0
5# which accompanies this distribution, and is available at
6# http://www.eclipse.org/legal/epl-v10.html
7#
8# Contributors:
9# Intel - initial implementation
10###############################################################################
11
12# "featureName" property - name of the feature
13pluginName=Yocto Project ADT Plug-in - Source
14
15# "providerName" property - name of the company that provides the feature
16providerName=yoctoproject.org
17
18# "updateSiteName" property - label for the update site
19updateSiteName=Yocto Project Update Site
20
21# "description" property - description of the feature
22description=\
23Eclipse plug-ins for developing embedded applications using Yocto Project
24
25# copyright
26copyright=\
27Copyright (c) 2011 Intel, Inc. and others. \
28All rights reserved. This program and the accompanying materials \
29are made available under the terms of the Eclipse Public License v1.0 \
30which accompanies this distribution, and is available at \
31http://www.eclipse.org/legal/epl-v10.html
32################ end of copyright property ####################################
33
34# "licenseURL" property - URL of the "Feature License"
35# do not translate value - just change to point to a locale-specific HTML page
36licenseURL=license.html
37
38# "license" property - text of the "Feature Update License"
39# should be plain text version of license agreement pointed to be "licenseURL"
40license=\
41Eclipse Foundation Software User Agreement\n\
42April 14, 2010\n\
43\n\
44Usage Of Content\n\
45\n\
46THE ECLIPSE FOUNDATION MAKES AVAILABLE SOFTWARE, DOCUMENTATION, INFORMATION AND/OR\n\
47OTHER MATERIALS FOR OPEN SOURCE PROJECTS (COLLECTIVELY "CONTENT").\n\
48USE OF THE CONTENT IS GOVERNED BY THE TERMS AND CONDITIONS OF THIS\n\
49AGREEMENT AND/OR THE TERMS AND CONDITIONS OF LICENSE AGREEMENTS OR\n\
50NOTICES INDICATED OR REFERENCED BELOW. BY USING THE CONTENT, YOU\n\
51AGREE THAT YOUR USE OF THE CONTENT IS GOVERNED BY THIS AGREEMENT\n\
52AND/OR THE TERMS AND CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS\n\
53OR NOTICES INDICATED OR REFERENCED BELOW. IF YOU DO NOT AGREE TO THE\n\
54TERMS AND CONDITIONS OF THIS AGREEMENT AND THE TERMS AND CONDITIONS\n\
55OF ANY APPLICABLE LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED\n\
56BELOW, THEN YOU MAY NOT USE THE CONTENT.\n\
57\n\
58Applicable Licenses\n\
59\n\
60Unless otherwise indicated, all Content made available by the\n\
61Eclipse Foundation is provided to you under the terms and conditions of\n\
62the Eclipse Public License Version 1.0 ("EPL"). A copy of the EPL is\n\
63provided with this Content and is also available at http://www.eclipse.org/legal/epl-v10.html.\n\
64For purposes of the EPL, "Program" will mean the Content.\n\
65\n\
66Content includes, but is not limited to, source code, object code,\n\
67documentation and other files maintained in the Eclipse Foundation source code\n\
68repository ("Repository") in software modules ("Modules") and made available\n\
69as downloadable archives ("Downloads").\n\
70\n\
71 - Content may be structured and packaged into modules to facilitate delivering,\n\
72 extending, and upgrading the Content. Typical modules may include plug-ins ("Plug-ins"),\n\
73 plug-in fragments ("Fragments"), and features ("Features").\n\
74 - Each Plug-in or Fragment may be packaged as a sub-directory or JAR (Java(TM) ARchive)\n\
75 in a directory named "plugins".\n\
76 - A Feature is a bundle of one or more Plug-ins and/or Fragments and associated material.\n\
77 Each Feature may be packaged as a sub-directory in a directory named "features".\n\
78 Within a Feature, files named "feature.xml" may contain a list of the names and version\n\
79 numbers of the Plug-ins and/or Fragments associated with that Feature.\n\
80 - Features may also include other Features ("Included Features"). Within a Feature, files\n\
81 named "feature.xml" may contain a list of the names and version numbers of Included Features.\n\
82\n\
83The terms and conditions governing Plug-ins and Fragments should be\n\
84contained in files named "about.html" ("Abouts"). The terms and\n\
85conditions governing Features and Included Features should be contained\n\
86in files named "license.html" ("Feature Licenses"). Abouts and Feature\n\
87Licenses may be located in any directory of a Download or Module\n\
88including, but not limited to the following locations:\n\
89\n\
90 - The top-level (root) directory\n\
91 - Plug-in and Fragment directories\n\
92 - Inside Plug-ins and Fragments packaged as JARs\n\
93 - Sub-directories of the directory named "src" of certain Plug-ins\n\
94 - Feature directories\n\
95\n\
96Note: if a Feature made available by the Eclipse Foundation is installed using the\n\
97Provisioning Technology (as defined below), you must agree to a license ("Feature \n\
98Update License") during the installation process. If the Feature contains\n\
99Included Features, the Feature Update License should either provide you\n\
100with the terms and conditions governing the Included Features or inform\n\
101you where you can locate them. Feature Update Licenses may be found in\n\
102the "license" property of files named "feature.properties" found within a Feature.\n\
103Such Abouts, Feature Licenses, and Feature Update Licenses contain the\n\
104terms and conditions (or references to such terms and conditions) that\n\
105govern your use of the associated Content in that directory.\n\
106\n\
107THE ABOUTS, FEATURE LICENSES, AND FEATURE UPDATE LICENSES MAY REFER\n\
108TO THE EPL OR OTHER LICENSE AGREEMENTS, NOTICES OR TERMS AND CONDITIONS.\n\
109SOME OF THESE OTHER LICENSE AGREEMENTS MAY INCLUDE (BUT ARE NOT LIMITED TO):\n\
110\n\
111 - Common Public License Version 1.0 (available at http://www.eclipse.org/legal/cpl-v10.html)\n\
112 - Apache Software License 1.1 (available at http://www.apache.org/licenses/LICENSE)\n\
113 - Apache Software License 2.0 (available at http://www.apache.org/licenses/LICENSE-2.0)\n\
114 - Metro Link Public License 1.00 (available at http://www.opengroup.org/openmotif/supporters/metrolink/license.html)\n\
115 - Mozilla Public License Version 1.1 (available at http://www.mozilla.org/MPL/MPL-1.1.html)\n\
116\n\
117IT IS YOUR OBLIGATION TO READ AND ACCEPT ALL SUCH TERMS AND CONDITIONS PRIOR\n\
118TO USE OF THE CONTENT. If no About, Feature License, or Feature Update License\n\
119is provided, please contact the Eclipse Foundation to determine what terms and conditions\n\
120govern that particular Content.\n\
121\n\
122\n\Use of Provisioning Technology\n\
123\n\
124The Eclipse Foundation makes available provisioning software, examples of which include,\n\
125but are not limited to, p2 and the Eclipse Update Manager ("Provisioning Technology") for\n\
126the purpose of allowing users to install software, documentation, information and/or\n\
127other materials (collectively "Installable Software"). This capability is provided with\n\
128the intent of allowing such users to install, extend and update Eclipse-based products.\n\
129Information about packaging Installable Software is available at\n\
130http://eclipse.org/equinox/p2/repository_packaging.html ("Specification").\n\
131\n\
132You may use Provisioning Technology to allow other parties to install Installable Software.\n\
133You shall be responsible for enabling the applicable license agreements relating to the\n\
134Installable Software to be presented to, and accepted by, the users of the Provisioning Technology\n\
135in accordance with the Specification. By using Provisioning Technology in such a manner and\n\
136making it available in accordance with the Specification, you further acknowledge your\n\
137agreement to, and the acquisition of all necessary rights to permit the following:\n\
138\n\
139 1. A series of actions may occur ("Provisioning Process") in which a user may execute\n\
140 the Provisioning Technology on a machine ("Target Machine") with the intent of installing,\n\
141 extending or updating the functionality of an Eclipse-based product.\n\
142 2. During the Provisioning Process, the Provisioning Technology may cause third party\n\
143 Installable Software or a portion thereof to be accessed and copied to the Target Machine.\n\
144 3. Pursuant to the Specification, you will provide to the user the terms and conditions that\n\
145 govern the use of the Installable Software ("Installable Software Agreement") and such\n\
146 Installable Software Agreement shall be accessed from the Target Machine in accordance\n\
147 with the Specification. Such Installable Software Agreement must inform the user of the\n\
148 terms and conditions that govern the Installable Software and must solicit acceptance by\n\
149 the end user in the manner prescribed in such Installable Software Agreement. Upon such\n\
150 indication of agreement by the user, the provisioning Technology will complete installation\n\
151 of the Installable Software.\n\
152\n\
153Cryptography\n\
154\n\
155Content may contain encryption software. The country in which you are\n\
156currently may have restrictions on the import, possession, and use,\n\
157and/or re-export to another country, of encryption software. BEFORE\n\
158using any encryption software, please check the country's laws,\n\
159regulations and policies concerning the import, possession, or use, and\n\
160re-export of encryption software, to see if this is permitted.\n\
161\n\
162Java and all Java-based trademarks are trademarks of Oracle Corporation in the United States, other countries, or both.\n
163########### end of license property ##########################################