Skip to main content
summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorZeb Ford-Reitz2012-04-23 12:08:12 +0000
committerZeb Ford-Reitz2012-04-23 12:22:05 +0000
commit2af1faaa1708d2229bd070f7a75a56217dccb1ca (patch)
treeab9d5b6813afcb09e1091d4d027b2ac93eda2cda
parentd8acace8d2f34dbef3aaa2c2be241b6d9a424f01 (diff)
downloadorg.eclipse.jubula.core-2af1faaa1708d2229bd070f7a75a56217dccb1ca.tar.gz
org.eclipse.jubula.core-2af1faaa1708d2229bd070f7a75a56217dccb1ca.tar.xz
org.eclipse.jubula.core-2af1faaa1708d2229bd070f7a75a56217dccb1ca.zip
fixes https://bxapps.bredex.de/bugzilla/show_bug.cgi?id=337
Adds a feature project to the toolkit extension examples. This feature project allows the client-side extension project to be exported as an update site. This in turn allows proper p2-based installation of the extension. Also updates the Extension Manual to reflect the addition of the new feature project and the new method of exporting and installing the extension.
-rw-r--r--org.eclipse.jubula.documentation/extensionapi/en/tex/generalSteps/CONTENT.tex65
-rw-r--r--org.eclipse.jubula.examples.extension.rcp.feature/.project17
-rw-r--r--org.eclipse.jubula.examples.extension.rcp.feature/about.html28
-rw-r--r--org.eclipse.jubula.examples.extension.rcp.feature/build.properties2
-rw-r--r--org.eclipse.jubula.examples.extension.rcp.feature/feature.properties127
-rw-r--r--org.eclipse.jubula.examples.extension.rcp.feature/feature.xml34
-rw-r--r--org.eclipse.jubula.examples.extension.swing.feature/.project17
-rw-r--r--org.eclipse.jubula.examples.extension.swing.feature/about.html28
-rw-r--r--org.eclipse.jubula.examples.extension.swing.feature/build.properties2
-rw-r--r--org.eclipse.jubula.examples.extension.swing.feature/feature.properties127
-rw-r--r--org.eclipse.jubula.examples.extension.swing.feature/feature.xml34
-rw-r--r--org.eclipse.jubula.examples/buildScript.xml2
12 files changed, 463 insertions, 20 deletions
diff --git a/org.eclipse.jubula.documentation/extensionapi/en/tex/generalSteps/CONTENT.tex b/org.eclipse.jubula.documentation/extensionapi/en/tex/generalSteps/CONTENT.tex
index 945e88303..a4830bd90 100644
--- a/org.eclipse.jubula.documentation/extensionapi/en/tex/generalSteps/CONTENT.tex
+++ b/org.eclipse.jubula.documentation/extensionapi/en/tex/generalSteps/CONTENT.tex
@@ -58,7 +58,7 @@ InstallationDir$\backslash$server$\backslash$lib$\backslash$extImplClasses
The following steps have to be done to extend the \app{} client:
\begin{enumerate}
- \item Create an eclipse plug-in project
+ \item Create an eclipse plug-in project and a corresponding feature project.
\item Set ''InstallationDir$\backslash$\app{}$\backslash$plugins'' as your target platform
\item Define plugin dependencies to the toolkit support plugin
\item Enter the toolkit support plugin in your toolkit plugin project
@@ -71,33 +71,58 @@ The following steps have to be done to extend the \app{} client:
\item Define a new component
\end{itemize}
\item Manage the i18n keys
- \item Export the toolkit plugin to \app{}
+ \item Export the toolkit feature to \app{}
\end{enumerate}
Under ''InstallationDirectory/examples/development/extension/src''
you will find a \\ ''eclipseProjects\_ExampleSwingClientExtension.zip'' which contains
- an example \app{} Client Extension for the Swing component ''JSlider''. This project
- is a showcase for steps 1-8.
+ an example \app{} Client Extension for the Swing component ''JSlider'' as well
+ as a corresponding feature project. These projects are a showcase for steps 1-8.
\subsection{Exporting the toolkit plugin to \app{}}
- The only step you have to do after importing this project into your Eclipse workspace and
- setting the target platform (step no. 2) is to export it to the \app{} you want to
- extend. To export the toolkit plugin to \app{}:
+ The only steps you have to do after importing the projects into your Eclipse workspace and
+ setting the target platform (step no. 2) is to export the feature to an update site
+ and then use the update site to install the feature into the \app{} you want to
+ extend.
+
+To export the toolkit feature to an update site:
+
+\begin{enumerate}
+\item In the package explorer, right click on the feature project
+ (ex. \bxname{org.eclipse.jubula.examples.extension.swing.feature}) and select:
+ \bxname{Export...} from the context-sensitive menu.
+\item In the dialog that appears, select \bxname{Deployable features} and click \bxcaption{Next}.
+\item In the next dialog, in the \bxname{Available Features} area, ensure that
+ the checkbox next to the feature you wish to export is selected.
+\item In the \bxname{Destination} tab, enter the location
+ where the feature's update site should be exported to in the \bxname{Directory}
+ field. This can be any writable directory. This directory will serve as an
+ update site, which can later be used to install your feature into \app{}.
+\item In the \bxname{Options} tab, ensure that the \bxname{Package as individual JAR archives} checkbox is selected and click \bxcaption{Finish}.
+\end{enumerate}
+
+To install the toolkit feature from the update site:
\begin{enumerate}
-\item In the package explorer, right click on the \bxname{plugin.xml} file and select:\\
-\bxmenu{Open with}{plugin manifest editor}{}\\
-from the context-sensitive menu.
-\item Select the \bxname{build} tab from the editor.
-\item In the binary build area, select \bxname{meta-inf, bin, build properties, plugin.xml} and \bxname{resources}.
-\item Save the changes in the editor and close the editor.
-\item In the package explorer, right click on the project and select \bxname{export} from the context-sensitive menu.
-\item In the dialog that appears, select \bxname{deployable plugins and fragments} and click \bxcaption{next}.
-\item In the next dialog, in the \bxname{destination} tab, enter the location where the plugin should be exported to in the \bxname{directory} field:\\
-\bxname{InstallationPath/\app{}}
-\item In the \bxname{options} tab, deselect the checkbox which will export the plugin as individual jar archives and click \bxcaption{finish}.
-\item You should be able to find the folder \\ \bxcaption{org.eclipse.jubula.examples.extension.swing.toolkit} in the \bxname{InstallationPath/\app{}/plugins/} folder. The exported plugin is in this folder.
-\item If you need to make changes and export the plugin again, delete the \\ \bxname{org.eclipse.jubula.examples.extension.swing.toolkit} from the \bxname{InstallationPath/\app{}/plugins/} folder first.
+\item Start \app{} and select \bxmenu{Help}{Install new software...}{} from the main menu.
+\item In the \bxname{Install} dialog that appears, click the \bxname{Add...} button.
+\item In the \bxname{Add Repository} dialog that appears, click the \bxname{Local...} button.
+\item In the file selection dialog that appears, navigate to the directory that contains your update site and confirm the dialog.
+\item Click \bxname{OK} to exit the \bxname{Add Repository} dialog.
+ The active dialog should now be \bxname{Install}.
+\item Ensure that the \bxname{Group items by category} checkbox is deselected.
+ Your feature should be visible in the central table of the dialog.
+\item Ensure that the checkbox next to your feature is selected and click \bxname{Next}.
+\item Confirm the \bxname{Installation Details} by again clicking \bxname{Next}.
+\item Accept the license agreement terms and click \bxname{Finish}.
+\item A warning dialog may appear to warn of unsigned content. Click
+ \bxname{OK} in this dialog if the feature comes from a trusted source (ex.
+ if you have written the software yourself, as in this example). This will
+ begin installation.
+\item After installation, a dialog appears suggesting that \app{} be restarted
+ in order to safely finish the update / installation. Click \bxname{Restart Now}
+ to perform the restart. Once the restart completes, your extension feature has
+ been installed in \app{}.
\end{enumerate}
\section{\app{} Server Extension}
diff --git a/org.eclipse.jubula.examples.extension.rcp.feature/.project b/org.eclipse.jubula.examples.extension.rcp.feature/.project
new file mode 100644
index 000000000..122ca3a5d
--- /dev/null
+++ b/org.eclipse.jubula.examples.extension.rcp.feature/.project
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>org.eclipse.jubula.examples.extension.rcp.feature</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ <buildCommand>
+ <name>org.eclipse.pde.FeatureBuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ </buildSpec>
+ <natures>
+ <nature>org.eclipse.pde.FeatureNature</nature>
+ </natures>
+</projectDescription>
diff --git a/org.eclipse.jubula.examples.extension.rcp.feature/about.html b/org.eclipse.jubula.examples.extension.rcp.feature/about.html
new file mode 100644
index 000000000..2477caacc
--- /dev/null
+++ b/org.eclipse.jubula.examples.extension.rcp.feature/about.html
@@ -0,0 +1,28 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>
+<title>About</title>
+</head>
+<body lang="EN-US">
+<h2>About This Content</h2>
+
+<p>April 20, 2012</p>
+<h3>License</h3>
+
+<p>The Eclipse Foundation makes available all content in this plug-in (&quot;Content&quot;). Unless otherwise
+indicated below, the Content is provided to you under the terms and conditions of the
+Eclipse Public License Version 1.0 (&quot;EPL&quot;). A copy of the EPL is available
+at <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>.
+For purposes of the EPL, &quot;Program&quot; will mean the Content.</p>
+
+<p>If you did not receive this Content directly from the Eclipse Foundation, the Content is
+being redistributed by another party (&quot;Redistributor&quot;) and different terms and conditions may
+apply to your use of any object code in the Content. Check the Redistributor's license that was
+provided with the Content. If no such license exists, contact the Redistributor. Unless otherwise
+indicated below, the terms and conditions of the EPL still apply to any source code in the Content
+and such source code may be obtained at <a href="http://www.eclipse.org">http://www.eclipse.org</a>.</p>
+
+</body>
+</html>
diff --git a/org.eclipse.jubula.examples.extension.rcp.feature/build.properties b/org.eclipse.jubula.examples.extension.rcp.feature/build.properties
new file mode 100644
index 000000000..b3a611b5c
--- /dev/null
+++ b/org.eclipse.jubula.examples.extension.rcp.feature/build.properties
@@ -0,0 +1,2 @@
+bin.includes = feature.xml,\
+ feature.properties
diff --git a/org.eclipse.jubula.examples.extension.rcp.feature/feature.properties b/org.eclipse.jubula.examples.extension.rcp.feature/feature.properties
new file mode 100644
index 000000000..7229d05d8
--- /dev/null
+++ b/org.eclipse.jubula.examples.extension.rcp.feature/feature.properties
@@ -0,0 +1,127 @@
+# "license" property - text of the "Feature Update License"
+# should be plain text version of license agreement pointed to be "licenseURL"
+license=\
+Eclipse Foundation Software User Agreement\n\
+February 1, 2011\n\
+\n\
+Usage Of Content\n\
+\n\
+THE ECLIPSE FOUNDATION MAKES AVAILABLE SOFTWARE, DOCUMENTATION, INFORMATION AND/OR\n\
+OTHER MATERIALS FOR OPEN SOURCE PROJECTS (COLLECTIVELY "CONTENT").\n\
+USE OF THE CONTENT IS GOVERNED BY THE TERMS AND CONDITIONS OF THIS\n\
+AGREEMENT AND/OR THE TERMS AND CONDITIONS OF LICENSE AGREEMENTS OR\n\
+NOTICES INDICATED OR REFERENCED BELOW. BY USING THE CONTENT, YOU\n\
+AGREE THAT YOUR USE OF THE CONTENT IS GOVERNED BY THIS AGREEMENT\n\
+AND/OR THE TERMS AND CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS\n\
+OR NOTICES INDICATED OR REFERENCED BELOW. IF YOU DO NOT AGREE TO THE\n\
+TERMS AND CONDITIONS OF THIS AGREEMENT AND THE TERMS AND CONDITIONS\n\
+OF ANY APPLICABLE LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED\n\
+BELOW, THEN YOU MAY NOT USE THE CONTENT.\n\
+\n\
+Applicable Licenses\n\
+\n\
+Unless otherwise indicated, all Content made available by the\n\
+Eclipse Foundation is provided to you under the terms and conditions of\n\
+the Eclipse Public License Version 1.0 ("EPL"). A copy of the EPL is\n\
+provided with this Content and is also available at http://www.eclipse.org/legal/epl-v10.html.\n\
+For purposes of the EPL, "Program" will mean the Content.\n\
+\n\
+Content includes, but is not limited to, source code, object code,\n\
+documentation and other files maintained in the Eclipse Foundation source code\n\
+repository ("Repository") in software modules ("Modules") and made available\n\
+as downloadable archives ("Downloads").\n\
+\n\
+ - Content may be structured and packaged into modules to facilitate delivering,\n\
+ extending, and upgrading the Content. Typical modules may include plug-ins ("Plug-ins"),\n\
+ plug-in fragments ("Fragments"), and features ("Features").\n\
+ - Each Plug-in or Fragment may be packaged as a sub-directory or JAR (Java(TM) ARchive)\n\
+ in a directory named "plugins".\n\
+ - A Feature is a bundle of one or more Plug-ins and/or Fragments and associated material.\n\
+ Each Feature may be packaged as a sub-directory in a directory named "features".\n\
+ Within a Feature, files named "feature.xml" may contain a list of the names and version\n\
+ numbers of the Plug-ins and/or Fragments associated with that Feature.\n\
+ - Features may also include other Features ("Included Features"). Within a Feature, files\n\
+ named "feature.xml" may contain a list of the names and version numbers of Included Features.\n\
+\n\
+The terms and conditions governing Plug-ins and Fragments should be\n\
+contained in files named "about.html" ("Abouts"). The terms and\n\
+conditions governing Features and Included Features should be contained\n\
+in files named "license.html" ("Feature Licenses"). Abouts and Feature\n\
+Licenses may be located in any directory of a Download or Module\n\
+including, but not limited to the following locations:\n\
+\n\
+ - The top-level (root) directory\n\
+ - Plug-in and Fragment directories\n\
+ - Inside Plug-ins and Fragments packaged as JARs\n\
+ - Sub-directories of the directory named "src" of certain Plug-ins\n\
+ - Feature directories\n\
+\n\
+Note: if a Feature made available by the Eclipse Foundation is installed using the\n\
+Provisioning Technology (as defined below), you must agree to a license ("Feature \n\
+Update License") during the installation process. If the Feature contains\n\
+Included Features, the Feature Update License should either provide you\n\
+with the terms and conditions governing the Included Features or inform\n\
+you where you can locate them. Feature Update Licenses may be found in\n\
+the "license" property of files named "feature.properties" found within a Feature.\n\
+Such Abouts, Feature Licenses, and Feature Update Licenses contain the\n\
+terms and conditions (or references to such terms and conditions) that\n\
+govern your use of the associated Content in that directory.\n\
+\n\
+THE ABOUTS, FEATURE LICENSES, AND FEATURE UPDATE LICENSES MAY REFER\n\
+TO THE EPL OR OTHER LICENSE AGREEMENTS, NOTICES OR TERMS AND CONDITIONS.\n\
+SOME OF THESE OTHER LICENSE AGREEMENTS MAY INCLUDE (BUT ARE NOT LIMITED TO):\n\
+\n\
+ - Eclipse Distribution License Version 1.0 (available at http://www.eclipse.org/licenses/edl-v1.0.html)\n\
+ - Common Public License Version 1.0 (available at http://www.eclipse.org/legal/cpl-v10.html)\n\
+ - Apache Software License 1.1 (available at http://www.apache.org/licenses/LICENSE)\n\
+ - Apache Software License 2.0 (available at http://www.apache.org/licenses/LICENSE-2.0)\n\
+ - Metro Link Public License 1.00 (available at http://www.opengroup.org/openmotif/supporters/metrolink/license.html)\n\
+ - Mozilla Public License Version 1.1 (available at http://www.mozilla.org/MPL/MPL-1.1.html)\n\
+\n\
+IT IS YOUR OBLIGATION TO READ AND ACCEPT ALL SUCH TERMS AND CONDITIONS PRIOR\n\
+TO USE OF THE CONTENT. If no About, Feature License, or Feature Update License\n\
+is provided, please contact the Eclipse Foundation to determine what terms and conditions\n\
+govern that particular Content.\n\
+\n\
+\n\Use of Provisioning Technology\n\
+\n\
+The Eclipse Foundation makes available provisioning software, examples of which include,\n\
+but are not limited to, p2 and the Eclipse Update Manager ("Provisioning Technology") for\n\
+the purpose of allowing users to install software, documentation, information and/or\n\
+other materials (collectively "Installable Software"). This capability is provided with\n\
+the intent of allowing such users to install, extend and update Eclipse-based products.\n\
+Information about packaging Installable Software is available at\n\
+http://eclipse.org/equinox/p2/repository_packaging.html ("Specification").\n\
+\n\
+You may use Provisioning Technology to allow other parties to install Installable Software.\n\
+You shall be responsible for enabling the applicable license agreements relating to the\n\
+Installable Software to be presented to, and accepted by, the users of the Provisioning Technology\n\
+in accordance with the Specification. By using Provisioning Technology in such a manner and\n\
+making it available in accordance with the Specification, you further acknowledge your\n\
+agreement to, and the acquisition of all necessary rights to permit the following:\n\
+\n\
+ 1. A series of actions may occur ("Provisioning Process") in which a user may execute\n\
+ the Provisioning Technology on a machine ("Target Machine") with the intent of installing,\n\
+ extending or updating the functionality of an Eclipse-based product.\n\
+ 2. During the Provisioning Process, the Provisioning Technology may cause third party\n\
+ Installable Software or a portion thereof to be accessed and copied to the Target Machine.\n\
+ 3. Pursuant to the Specification, you will provide to the user the terms and conditions that\n\
+ govern the use of the Installable Software ("Installable Software Agreement") and such\n\
+ Installable Software Agreement shall be accessed from the Target Machine in accordance\n\
+ with the Specification. Such Installable Software Agreement must inform the user of the\n\
+ terms and conditions that govern the Installable Software and must solicit acceptance by\n\
+ the end user in the manner prescribed in such Installable Software Agreement. Upon such\n\
+ indication of agreement by the user, the provisioning Technology will complete installation\n\
+ of the Installable Software.\n\
+\n\
+Cryptography\n\
+\n\
+Content may contain encryption software. The country in which you are\n\
+currently may have restrictions on the import, possession, and use,\n\
+and/or re-export to another country, of encryption software. BEFORE\n\
+using any encryption software, please check the country's laws,\n\
+regulations and policies concerning the import, possession, or use, and\n\
+re-export of encryption software, to see if this is permitted.\n\
+\n\
+Java and all Java-based trademarks are trademarks of Oracle Corporation in the United States, other countries, or both.\n
+########### end of license property ##########################################
diff --git a/org.eclipse.jubula.examples.extension.rcp.feature/feature.xml b/org.eclipse.jubula.examples.extension.rcp.feature/feature.xml
new file mode 100644
index 000000000..25c41d156
--- /dev/null
+++ b/org.eclipse.jubula.examples.extension.rcp.feature/feature.xml
@@ -0,0 +1,34 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<feature
+ id="org.eclipse.jubula.examples.extension.rcp.feature"
+ label="Jubula Example - Toolkit Extension - RCP"
+ version="1.2.0.qualifier"
+ provider-name="Eclipse Jubula">
+
+ <description url="http://www.eclipse.org/jubula">
+ Example Jubula Toolkit Extension - RCP
+ </description>
+
+ <copyright url="http://www.eclipse.org/jubula">
+ Copyright (c) 2004, 2012 BREDEX GmbH.
+All rights reserved. This program and the accompanying materials
+are made available under the terms of the Eclipse Public License
+v1.0
+which accompanies this distribution, and is available at
+http://www.eclipse.org/legal/epl-v10.html
+Contributors:
+BREDEX GmbH - initial API and implementation and/or initial documentation
+ </copyright>
+
+ <license url="http://www.eclipse.org/legal/epl-v10.html">
+ %license
+ </license>
+
+ <plugin
+ id="org.eclipse.jubula.examples.extension.rcp.toolkit"
+ download-size="0"
+ install-size="0"
+ version="0.0.0"
+ unpack="false"/>
+
+</feature>
diff --git a/org.eclipse.jubula.examples.extension.swing.feature/.project b/org.eclipse.jubula.examples.extension.swing.feature/.project
new file mode 100644
index 000000000..c51febdf3
--- /dev/null
+++ b/org.eclipse.jubula.examples.extension.swing.feature/.project
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>org.eclipse.jubula.examples.extension.swing.feature</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ <buildCommand>
+ <name>org.eclipse.pde.FeatureBuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ </buildSpec>
+ <natures>
+ <nature>org.eclipse.pde.FeatureNature</nature>
+ </natures>
+</projectDescription>
diff --git a/org.eclipse.jubula.examples.extension.swing.feature/about.html b/org.eclipse.jubula.examples.extension.swing.feature/about.html
new file mode 100644
index 000000000..2477caacc
--- /dev/null
+++ b/org.eclipse.jubula.examples.extension.swing.feature/about.html
@@ -0,0 +1,28 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>
+<title>About</title>
+</head>
+<body lang="EN-US">
+<h2>About This Content</h2>
+
+<p>April 20, 2012</p>
+<h3>License</h3>
+
+<p>The Eclipse Foundation makes available all content in this plug-in (&quot;Content&quot;). Unless otherwise
+indicated below, the Content is provided to you under the terms and conditions of the
+Eclipse Public License Version 1.0 (&quot;EPL&quot;). A copy of the EPL is available
+at <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>.
+For purposes of the EPL, &quot;Program&quot; will mean the Content.</p>
+
+<p>If you did not receive this Content directly from the Eclipse Foundation, the Content is
+being redistributed by another party (&quot;Redistributor&quot;) and different terms and conditions may
+apply to your use of any object code in the Content. Check the Redistributor's license that was
+provided with the Content. If no such license exists, contact the Redistributor. Unless otherwise
+indicated below, the terms and conditions of the EPL still apply to any source code in the Content
+and such source code may be obtained at <a href="http://www.eclipse.org">http://www.eclipse.org</a>.</p>
+
+</body>
+</html>
diff --git a/org.eclipse.jubula.examples.extension.swing.feature/build.properties b/org.eclipse.jubula.examples.extension.swing.feature/build.properties
new file mode 100644
index 000000000..b3a611b5c
--- /dev/null
+++ b/org.eclipse.jubula.examples.extension.swing.feature/build.properties
@@ -0,0 +1,2 @@
+bin.includes = feature.xml,\
+ feature.properties
diff --git a/org.eclipse.jubula.examples.extension.swing.feature/feature.properties b/org.eclipse.jubula.examples.extension.swing.feature/feature.properties
new file mode 100644
index 000000000..7229d05d8
--- /dev/null
+++ b/org.eclipse.jubula.examples.extension.swing.feature/feature.properties
@@ -0,0 +1,127 @@
+# "license" property - text of the "Feature Update License"
+# should be plain text version of license agreement pointed to be "licenseURL"
+license=\
+Eclipse Foundation Software User Agreement\n\
+February 1, 2011\n\
+\n\
+Usage Of Content\n\
+\n\
+THE ECLIPSE FOUNDATION MAKES AVAILABLE SOFTWARE, DOCUMENTATION, INFORMATION AND/OR\n\
+OTHER MATERIALS FOR OPEN SOURCE PROJECTS (COLLECTIVELY "CONTENT").\n\
+USE OF THE CONTENT IS GOVERNED BY THE TERMS AND CONDITIONS OF THIS\n\
+AGREEMENT AND/OR THE TERMS AND CONDITIONS OF LICENSE AGREEMENTS OR\n\
+NOTICES INDICATED OR REFERENCED BELOW. BY USING THE CONTENT, YOU\n\
+AGREE THAT YOUR USE OF THE CONTENT IS GOVERNED BY THIS AGREEMENT\n\
+AND/OR THE TERMS AND CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS\n\
+OR NOTICES INDICATED OR REFERENCED BELOW. IF YOU DO NOT AGREE TO THE\n\
+TERMS AND CONDITIONS OF THIS AGREEMENT AND THE TERMS AND CONDITIONS\n\
+OF ANY APPLICABLE LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED\n\
+BELOW, THEN YOU MAY NOT USE THE CONTENT.\n\
+\n\
+Applicable Licenses\n\
+\n\
+Unless otherwise indicated, all Content made available by the\n\
+Eclipse Foundation is provided to you under the terms and conditions of\n\
+the Eclipse Public License Version 1.0 ("EPL"). A copy of the EPL is\n\
+provided with this Content and is also available at http://www.eclipse.org/legal/epl-v10.html.\n\
+For purposes of the EPL, "Program" will mean the Content.\n\
+\n\
+Content includes, but is not limited to, source code, object code,\n\
+documentation and other files maintained in the Eclipse Foundation source code\n\
+repository ("Repository") in software modules ("Modules") and made available\n\
+as downloadable archives ("Downloads").\n\
+\n\
+ - Content may be structured and packaged into modules to facilitate delivering,\n\
+ extending, and upgrading the Content. Typical modules may include plug-ins ("Plug-ins"),\n\
+ plug-in fragments ("Fragments"), and features ("Features").\n\
+ - Each Plug-in or Fragment may be packaged as a sub-directory or JAR (Java(TM) ARchive)\n\
+ in a directory named "plugins".\n\
+ - A Feature is a bundle of one or more Plug-ins and/or Fragments and associated material.\n\
+ Each Feature may be packaged as a sub-directory in a directory named "features".\n\
+ Within a Feature, files named "feature.xml" may contain a list of the names and version\n\
+ numbers of the Plug-ins and/or Fragments associated with that Feature.\n\
+ - Features may also include other Features ("Included Features"). Within a Feature, files\n\
+ named "feature.xml" may contain a list of the names and version numbers of Included Features.\n\
+\n\
+The terms and conditions governing Plug-ins and Fragments should be\n\
+contained in files named "about.html" ("Abouts"). The terms and\n\
+conditions governing Features and Included Features should be contained\n\
+in files named "license.html" ("Feature Licenses"). Abouts and Feature\n\
+Licenses may be located in any directory of a Download or Module\n\
+including, but not limited to the following locations:\n\
+\n\
+ - The top-level (root) directory\n\
+ - Plug-in and Fragment directories\n\
+ - Inside Plug-ins and Fragments packaged as JARs\n\
+ - Sub-directories of the directory named "src" of certain Plug-ins\n\
+ - Feature directories\n\
+\n\
+Note: if a Feature made available by the Eclipse Foundation is installed using the\n\
+Provisioning Technology (as defined below), you must agree to a license ("Feature \n\
+Update License") during the installation process. If the Feature contains\n\
+Included Features, the Feature Update License should either provide you\n\
+with the terms and conditions governing the Included Features or inform\n\
+you where you can locate them. Feature Update Licenses may be found in\n\
+the "license" property of files named "feature.properties" found within a Feature.\n\
+Such Abouts, Feature Licenses, and Feature Update Licenses contain the\n\
+terms and conditions (or references to such terms and conditions) that\n\
+govern your use of the associated Content in that directory.\n\
+\n\
+THE ABOUTS, FEATURE LICENSES, AND FEATURE UPDATE LICENSES MAY REFER\n\
+TO THE EPL OR OTHER LICENSE AGREEMENTS, NOTICES OR TERMS AND CONDITIONS.\n\
+SOME OF THESE OTHER LICENSE AGREEMENTS MAY INCLUDE (BUT ARE NOT LIMITED TO):\n\
+\n\
+ - Eclipse Distribution License Version 1.0 (available at http://www.eclipse.org/licenses/edl-v1.0.html)\n\
+ - Common Public License Version 1.0 (available at http://www.eclipse.org/legal/cpl-v10.html)\n\
+ - Apache Software License 1.1 (available at http://www.apache.org/licenses/LICENSE)\n\
+ - Apache Software License 2.0 (available at http://www.apache.org/licenses/LICENSE-2.0)\n\
+ - Metro Link Public License 1.00 (available at http://www.opengroup.org/openmotif/supporters/metrolink/license.html)\n\
+ - Mozilla Public License Version 1.1 (available at http://www.mozilla.org/MPL/MPL-1.1.html)\n\
+\n\
+IT IS YOUR OBLIGATION TO READ AND ACCEPT ALL SUCH TERMS AND CONDITIONS PRIOR\n\
+TO USE OF THE CONTENT. If no About, Feature License, or Feature Update License\n\
+is provided, please contact the Eclipse Foundation to determine what terms and conditions\n\
+govern that particular Content.\n\
+\n\
+\n\Use of Provisioning Technology\n\
+\n\
+The Eclipse Foundation makes available provisioning software, examples of which include,\n\
+but are not limited to, p2 and the Eclipse Update Manager ("Provisioning Technology") for\n\
+the purpose of allowing users to install software, documentation, information and/or\n\
+other materials (collectively "Installable Software"). This capability is provided with\n\
+the intent of allowing such users to install, extend and update Eclipse-based products.\n\
+Information about packaging Installable Software is available at\n\
+http://eclipse.org/equinox/p2/repository_packaging.html ("Specification").\n\
+\n\
+You may use Provisioning Technology to allow other parties to install Installable Software.\n\
+You shall be responsible for enabling the applicable license agreements relating to the\n\
+Installable Software to be presented to, and accepted by, the users of the Provisioning Technology\n\
+in accordance with the Specification. By using Provisioning Technology in such a manner and\n\
+making it available in accordance with the Specification, you further acknowledge your\n\
+agreement to, and the acquisition of all necessary rights to permit the following:\n\
+\n\
+ 1. A series of actions may occur ("Provisioning Process") in which a user may execute\n\
+ the Provisioning Technology on a machine ("Target Machine") with the intent of installing,\n\
+ extending or updating the functionality of an Eclipse-based product.\n\
+ 2. During the Provisioning Process, the Provisioning Technology may cause third party\n\
+ Installable Software or a portion thereof to be accessed and copied to the Target Machine.\n\
+ 3. Pursuant to the Specification, you will provide to the user the terms and conditions that\n\
+ govern the use of the Installable Software ("Installable Software Agreement") and such\n\
+ Installable Software Agreement shall be accessed from the Target Machine in accordance\n\
+ with the Specification. Such Installable Software Agreement must inform the user of the\n\
+ terms and conditions that govern the Installable Software and must solicit acceptance by\n\
+ the end user in the manner prescribed in such Installable Software Agreement. Upon such\n\
+ indication of agreement by the user, the provisioning Technology will complete installation\n\
+ of the Installable Software.\n\
+\n\
+Cryptography\n\
+\n\
+Content may contain encryption software. The country in which you are\n\
+currently may have restrictions on the import, possession, and use,\n\
+and/or re-export to another country, of encryption software. BEFORE\n\
+using any encryption software, please check the country's laws,\n\
+regulations and policies concerning the import, possession, or use, and\n\
+re-export of encryption software, to see if this is permitted.\n\
+\n\
+Java and all Java-based trademarks are trademarks of Oracle Corporation in the United States, other countries, or both.\n
+########### end of license property ##########################################
diff --git a/org.eclipse.jubula.examples.extension.swing.feature/feature.xml b/org.eclipse.jubula.examples.extension.swing.feature/feature.xml
new file mode 100644
index 000000000..3f65d9e70
--- /dev/null
+++ b/org.eclipse.jubula.examples.extension.swing.feature/feature.xml
@@ -0,0 +1,34 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<feature
+ id="org.eclipse.jubula.examples.extension.swing.feature"
+ label="Jubula Example - Toolkit Extension - Swing"
+ version="1.2.0.qualifier"
+ provider-name="Eclipse Jubula">
+
+ <description url="http://www.eclipse.org/jubula">
+ Example Jubula Toolkit Extension - Swing
+ </description>
+
+ <copyright url="http://www.eclipse.org/jubula">
+ Copyright (c) 2004, 2012 BREDEX GmbH.
+All rights reserved. This program and the accompanying materials
+are made available under the terms of the Eclipse Public License
+v1.0
+which accompanies this distribution, and is available at
+http://www.eclipse.org/legal/epl-v10.html
+Contributors:
+BREDEX GmbH - initial API and implementation and/or initial documentation
+ </copyright>
+
+ <license url="http://www.eclipse.org/legal/epl-v10.html">
+ %license
+ </license>
+
+ <plugin
+ id="org.eclipse.jubula.examples.extension.swing.toolkit"
+ download-size="0"
+ install-size="0"
+ version="0.0.0"
+ unpack="false"/>
+
+</feature>
diff --git a/org.eclipse.jubula.examples/buildScript.xml b/org.eclipse.jubula.examples/buildScript.xml
index d68d90264..f0ceec623 100644
--- a/org.eclipse.jubula.examples/buildScript.xml
+++ b/org.eclipse.jubula.examples/buildScript.xml
@@ -24,6 +24,7 @@
<property name="GEFExample" value="com.bredexsw.guidancer.examples.aut.gef"/>
<property name="ExampleSwingExtensionClient" value="org.eclipse.jubula.examples.extension.swing.toolkit"/>
+ <property name="ExampleSwingExtensionFeature" value="org.eclipse.jubula.examples.extension.swing.feature"/>
<property name="ExampleSwingExtensionServer" value="org.eclipse.jubula.examples.extension.swing.rc"/>
<property name="ExampleSwingExtensionAUT" value="org.eclipse.jubula.examples.extension.swing.aut"/>
@@ -184,6 +185,7 @@
<mkdir dir="${extensionSourceDir}"/>
<zip destfile="${extensionSourceDir}/eclipseProjects_ExampleSwingClientExtension.zip">
<zipfileset dir="../${ExampleSwingExtensionClient}" prefix="${ExampleSwingExtensionClient}" excludes="build, build/**, target, target/**, buildScript.xml, pom.xml"/>
+ <zipfileset dir="../${ExampleSwingExtensionFeature}" prefix="${ExampleSwingExtensionFeature}" excludes="build, build/**, target, target/**, buildScript.xml, pom.xml"/>
</zip>
<zip destfile="${extensionSourceDir}/eclipseProjects_ExampleSwingServerExtension.zip">
<zipfileset dir="../${ExampleSwingExtensionServer}" prefix="${ExampleSwingExtensionServer}" excludes="build, build/**, buildScript.xml"/>

Back to the top