Eagle517/tge
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Initial commit

Browse Source
This commit is contained in:
Eagle517
2026-01-14 10:27:57 -06:00
commit c1576fee30
11290 changed files with 1552799 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
TBE/Eclipse/eclipse/plugins/org.eclipse.pde.build_3.0.1/.options Normal file
View File

@@ -0,0 +1,2 @@
# Debugging options for the org.eclipse.pde.build plug-in.
org.eclipse.pde.build/debug = false

21
TBE/Eclipse/eclipse/plugins/org.eclipse.pde.build_3.0.1/META-INF/MANIFEST.MF Normal file
View File

@@ -0,0 +1,21 @@
Bundle-Name: %pluginName
Bundle-Version: 3.0.1
Bundle-SymbolicName: org.eclipse.pde.build
Bundle-Vendor: %providerName
Bundle-ClassPath: pdebuild.jar
Bundle-Activator: org.eclipse.pde.internal.build.BuildActivator
Require-Bundle:
org.eclipse.core.runtime,
org.eclipse.ant.core,
org.eclipse.update.core,
org.apache.ant,
org.eclipse.core.runtime.compatibility;optional=true
Provide-Package:
org.eclipse.pde.internal.build.site,
org.eclipse.pde.internal.build.packager,
org.eclipse.pde.internal.build,
org.eclipse.pde.internal.build.ant,
org.eclipse.pde.internal.build.builder
Bundle-Localization: plugin
Eclipse-AutoStart: true
Eclipse-AutoStop: true

30
TBE/Eclipse/eclipse/plugins/org.eclipse.pde.build_3.0.1/about.html Normal file
View File

@@ -0,0 +1,30 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
<html>
<head>
<title>About</title>
<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1">
</head>
<body lang="EN-US">
<h2>About This Content</h2>
<p>20th June, 2002</p>
<h3>License</h3>
<p>Eclipse.org 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
Common Public License Version 1.0 (&quot;CPL&quot;). A copy of the CPL is available at <a href="http://www.eclipse.org/legal/cpl-v10.html">http://www.eclipse.org/legal/cpl-v10.html</a>.
For purposes of the CPL, &quot;Program&quot; will mean the Content.</p>
<h3>Contributions</h3>
<p>If this Content is licensed to you under the terms and conditions of the CPL, any Contributions, as defined in the CPL, uploaded, submitted, or otherwise
made available to Eclipse.org, members of Eclipse.org and/or the host of Eclipse.org web site, by you that relate to such
Content are provided under the terms and conditions of the CPL and can be made available to others under the terms of the CPL.</p>
<p>If this Content is licensed to you under license terms and conditions other than the CPL (&quot;Other License&quot;), any modifications, enhancements and/or
other code and/or documentation (&quot;Modifications&quot;) uploaded, submitted, or otherwise made available to Eclipse.org, members of Eclipse.org and/or the
host of Eclipse.org, by you that relate to such Content are provided under terms and conditions of the Other License and can be made available
to others under the terms of the Other License. In addition, with regard to Modifications for which you are the copyright holder, you are also
providing the Modifications under the terms and conditions of the CPL and such Modifications can be made available to others under the terms of
the CPL.</p>
</body>
</html>

11
TBE/Eclipse/eclipse/plugins/org.eclipse.pde.build_3.0.1/feature/.project Normal file
View File

@@ -0,0 +1,11 @@
<?xml version="1.0" encoding="UTF-8"?>
<projectDescription>
<name>org.eclipse.releng.builder</name>
<comment></comment>
<projects>
</projects>
<buildSpec>
</buildSpec>
<natures>
</natures>
</projectDescription>

10
TBE/Eclipse/eclipse/plugins/org.eclipse.pde.build_3.0.1/feature/build.properties Normal file
View File

@@ -0,0 +1,10 @@
bin.includes =\
cpl-v10.html,\
eclipse_update_120.jpg,\
feature.xml,\
feature.properties,\
license.html
root=rootfiles,file:../../plugins/org.eclipse.platform/startup.jar

45
TBE/Eclipse/eclipse/plugins/org.eclipse.pde.build_3.0.1/feature/builder/build.properties Normal file
View File

@@ -0,0 +1,45 @@
###############################################################################
# Copyright (c) 2003, 2004 IBM Corporation and others.
# All rights reserved. This program and the accompanying materials
# are made available under the terms of the Common Public License v1.0
# which accompanies this distribution, and is available at
# http://www.eclipse.org/legal/cpl-v10.html
#
# Contributors:
# IBM Corporation - initial API and implementation
###############################################################################
#####################
# Parameters describing how and where to execute the build.
# Typical users need only update the following properties:
# baseLocation - where things you are building against are installed
# bootclasspath - The base jars to compile against (typicaly rt.jar)
#
# Of course any of the settings here can be overridden by spec'ing
# them on the command line (e.g., -DbaseLocation=d:/eclipse
mapVersionTag=HEAD
buildDirectory=${basedir}/build
buildType=I
buildId=build
buildLabel=${buildType}.${buildId}
timestamp=007
collectingFolder=eclipse
archivePrefix=eclipse
configs=*,*,*
fetchTag=HEAD
bootclasspath=${java.home}/lib/rt.jar
javacFailOnError=false
javacDebugInfo=on
javacVerbose=true
baseLocation=
baseos=win32
basews=win32
basearch=x86
zipargs=

141
TBE/Eclipse/eclipse/plugins/org.eclipse.pde.build_3.0.1/feature/builder/customTargets.xml Normal file
View File

@@ -0,0 +1,141 @@
<project name="Build specific targets and properties" default="noDefault" >
<!-- ===================================================================== -->
<!-- Global properties -->
<!-- ===================================================================== -->
<!-- ===================================================================== -->
<!-- Run a given ${target} on all elements being built -->
<!-- ===================================================================== -->
<target name="allElements">
<ant antfile="${genericTargets}" target="${target}" >
<property name="type" value="feature" />
<property name="id" value="org.eclipse.pde.builder" />
</ant>
</target>
<!-- ===================================================================== -->
<!-- Targets to assemble the built elements for the pde builder feature -->
<!-- ===================================================================== -->
<target name="assemble.org.eclipse.pde.builder">
<ant antfile="${assembleScriptName}"/>
</target>
<!-- ===================================================================== -->
<!-- Check out map files from correct repository -->
<!-- Replace values for cvsRoot, package and mapVersionTag as desired. -->
<!-- ===================================================================== -->
<target name="getMapFiles">
<property name="cvsRoot" value=":pserver:anonymous@dev.eclipse.org:/home/eclipse" />
<property name="mapVersionTag" value="HEAD" />
<cvs cvsRoot="${cvsRoot}"
package="org.eclipse.releng"
dest="${buildDirectory}/maps"
tag="${mapVersionTag}"
/>
<!--tag the map files project-->
<antcall target="tagMapFiles" />
</target>
<target name="tagMapFiles" if="tag">
<cvs dest="org.eclipse.releng" command="tag v${timestamp}" />
</target>
<!-- ===================================================================== -->
<!-- Steps to do before setup -->
<!-- ===================================================================== -->
<target name="preSetup">
</target>
<!-- ===================================================================== -->
<!-- Steps to do after setup but before starting the build proper -->
<!-- ===================================================================== -->
<target name="postSetup">
</target>
<!-- ===================================================================== -->
<!-- Steps to do before fetching the build elements -->
<!-- ===================================================================== -->
<target name="preFetch">
</target>
<!-- ===================================================================== -->
<!-- Steps to do after the fetch. -->
<!-- ===================================================================== -->
<target name="postFetch">
<replace dir="${buildDirectory}/plugins" value="${timestamp}" token="@build@">
<include name="**/about.mappings" />
</replace>
</target>
<!-- ===================================================================== -->
<!-- Steps to do before generating the build scripts. -->
<!-- ===================================================================== -->
<target name="preGenerate">
</target>
<!-- ===================================================================== -->
<!-- Steps to do after generating the build scripts. -->
<!-- ===================================================================== -->
<target name="postGenerate">
</target>
<!-- ===================================================================== -->
<!-- Steps to do before running the build.xmls for the elements being built. -->
<!-- ===================================================================== -->
<target name="preProcess">
<ant antfile="${genericTargets}" target="fetchElement">
<property name="type" value="plugin" />
<property name="id" value="platform-launcher" />
</ant>
</target>
<!-- ===================================================================== -->
<!-- Steps to do after running the build.xmls for the elements being built. -->
<!-- ===================================================================== -->
<target name="postProcess">
</target>
<!-- ===================================================================== -->
<!-- Steps to do before running assemble. -->
<!-- ===================================================================== -->
<target name="preAssemble">
</target>
<!-- ===================================================================== -->
<!-- Steps to do after running assemble. -->
<!-- ===================================================================== -->
<target name="postAssemble">
</target>
<!-- ===================================================================== -->
<!-- Steps to do after everything is built and assembled -->
<!-- (e.g., testing, posting, emailing, ...) -->
<!-- ===================================================================== -->
<target name="postBuild">
</target>
<!-- ===================================================================== -->
<!-- Steps to do to test the build results -->
<!-- ===================================================================== -->
<target name="test">
</target>
<!-- ===================================================================== -->
<!-- Steps to do to publish the build results -->
<!-- ===================================================================== -->
<target name="publish">
</target>
<!-- ===================================================================== -->
<!-- Default target -->
<!-- ===================================================================== -->
<target name="noDefault">
<echo message="You must specify a target when invoking this file" />
</target>
</project>

125
TBE/Eclipse/eclipse/plugins/org.eclipse.pde.build_3.0.1/feature/cpl-v10.html Normal file
View File

@@ -0,0 +1,125 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
<HTML>
<HEAD>
<TITLE>Common Public License - v 1.0</TITLE>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</HEAD>
<BODY BGCOLOR="#FFFFFF" VLINK="#800000">
<P ALIGN="CENTER"><B>Common Public License - v 1.0</B>
<P><B></B><FONT SIZE="3"></FONT>
<P><FONT SIZE="3"></FONT><FONT SIZE="2">THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS COMMON PUBLIC LICENSE ("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION OF THE PROGRAM CONSTITUTES RECIPIENT'S ACCEPTANCE OF THIS AGREEMENT.</FONT>
<P><FONT SIZE="2"></FONT>
<P><FONT SIZE="2"><B>1. DEFINITIONS</B></FONT>
<P><FONT SIZE="2">"Contribution" means:</FONT>
<UL><FONT SIZE="2">a) in the case of the initial Contributor, the initial code and documentation distributed under this Agreement, and<BR CLEAR="LEFT">
b) in the case of each subsequent Contributor:</FONT></UL>
<UL><FONT SIZE="2">i) changes to the Program, and</FONT></UL>
<UL><FONT SIZE="2">ii) additions to the Program;</FONT></UL>
<UL><FONT SIZE="2">where such changes and/or additions to the Program originate from and are distributed by that particular Contributor. </FONT><FONT SIZE="2">A Contribution 'originates' from a Contributor if it was added to the Program by such Contributor itself or anyone acting on such Contributor's behalf. </FONT><FONT SIZE="2">Contributions do not include additions to the Program which: (i) are separate modules of software distributed in conjunction with the Program under their own license agreement, and (ii) are not derivative works of the Program. </FONT></UL>
<P><FONT SIZE="2"></FONT>
<P><FONT SIZE="2">"Contributor" means any person or entity that distributes the Program.</FONT>
<P><FONT SIZE="2"></FONT><FONT SIZE="2"></FONT>
<P><FONT SIZE="2">"Licensed Patents " mean patent claims licensable by a Contributor which are necessarily infringed by the use or sale of its Contribution alone or when combined with the Program. </FONT>
<P><FONT SIZE="2"></FONT><FONT SIZE="2"></FONT>
<P><FONT SIZE="2"></FONT><FONT SIZE="2">"Program" means the Contributions distributed in accordance with this Agreement.</FONT>
<P><FONT SIZE="2"></FONT>
<P><FONT SIZE="2">"Recipient" means anyone who receives the Program under this Agreement, including all Contributors.</FONT>
<P><FONT SIZE="2"><B></B></FONT>
<P><FONT SIZE="2"><B>2. GRANT OF RIGHTS</B></FONT>
<UL><FONT SIZE="2"></FONT><FONT SIZE="2">a) </FONT><FONT SIZE="2">Subject to the terms of this Agreement, each Contributor hereby grants</FONT><FONT SIZE="2"> Recipient a non-exclusive, worldwide, royalty-free copyright license to</FONT><FONT SIZE="2" COLOR="#FF0000"> </FONT><FONT SIZE="2">reproduce, prepare derivative works of, publicly display, publicly perform, distribute and sublicense the Contribution of such Contributor, if any, and such derivative works, in source code and object code form.</FONT></UL>
<UL><FONT SIZE="2"></FONT></UL>
<UL><FONT SIZE="2"></FONT><FONT SIZE="2">b) Subject to the terms of this Agreement, each Contributor hereby grants </FONT><FONT SIZE="2">Recipient a non-exclusive, worldwide,</FONT><FONT SIZE="2" COLOR="#008000"> </FONT><FONT SIZE="2">royalty-free patent license under Licensed Patents to make, use, sell, offer to sell, import and otherwise transfer the Contribution of such Contributor, if any, in source code and object code form. This patent license shall apply to the combination of the Contribution and the Program if, at the time the Contribution is added by the Contributor, such addition of the Contribution causes such combination to be covered by the Licensed Patents. The patent license shall not apply to any other combinations which include the Contribution. No hardware per se is licensed hereunder. </FONT></UL>
<UL><FONT SIZE="2"></FONT></UL>
<UL><FONT SIZE="2">c) Recipient understands that although each Contributor grants the licenses to its Contributions set forth herein, no assurances are provided by any Contributor that the Program does not infringe the patent or other intellectual property rights of any other entity. Each Contributor disclaims any liability to Recipient for claims brought by any other entity based on infringement of intellectual property rights or otherwise. As a condition to exercising the rights and licenses granted hereunder, each Recipient hereby assumes sole responsibility to secure any other intellectual property rights needed, if any. For example, if a third party patent license is required to allow Recipient to distribute the Program, it is Recipient's responsibility to acquire that license before distributing the Program.</FONT></UL>
<UL><FONT SIZE="2"></FONT></UL>
<UL><FONT SIZE="2">d) Each Contributor represents that to its knowledge it has sufficient copyright rights in its Contribution, if any, to grant the copyright license set forth in this Agreement. </FONT></UL>
<UL><FONT SIZE="2"></FONT></UL>
<P><FONT SIZE="2"><B>3. REQUIREMENTS</B></FONT>
<P><FONT SIZE="2"><B></B>A Contributor may choose to distribute the Program in object code form under its own license agreement, provided that:</FONT>
<UL><FONT SIZE="2">a) it complies with the terms and conditions of this Agreement; and</FONT></UL>
<UL><FONT SIZE="2">b) its license agreement:</FONT></UL>
<UL><FONT SIZE="2">i) effectively disclaims</FONT><FONT SIZE="2"> on behalf of all Contributors all warranties and conditions, express and implied, including warranties or conditions of title and non-infringement, and implied warranties or conditions of merchantability and fitness for a particular purpose; </FONT></UL>
<UL><FONT SIZE="2">ii) effectively excludes on behalf of all Contributors all liability for damages, including direct, indirect, special, incidental and consequential damages, such as lost profits; </FONT></UL>
<UL><FONT SIZE="2">iii)</FONT><FONT SIZE="2"> states that any provisions which differ from this Agreement are offered by that Contributor alone and not by any other party; and</FONT></UL>
<UL><FONT SIZE="2">iv) states that source code for the Program is available from such Contributor, and informs licensees how to obtain it in a reasonable manner on or through a medium customarily used for software exchange.</FONT><FONT SIZE="2" COLOR="#0000FF"> </FONT><FONT SIZE="2" COLOR="#FF0000"></FONT></UL>
<UL><FONT SIZE="2" COLOR="#FF0000"></FONT><FONT SIZE="2"></FONT></UL>
<P><FONT SIZE="2">When the Program is made available in source code form:</FONT>
<UL><FONT SIZE="2">a) it must be made available under this Agreement; and </FONT></UL>
<UL><FONT SIZE="2">b) a copy of this Agreement must be included with each copy of the Program. </FONT></UL>
<P><FONT SIZE="2"></FONT><FONT SIZE="2" COLOR="#0000FF"><STRIKE></STRIKE></FONT>
<P><FONT SIZE="2" COLOR="#0000FF"><STRIKE></STRIKE></FONT><FONT SIZE="2">Contributors may not remove or alter any copyright notices contained within the Program. </FONT>
<P><FONT SIZE="2"></FONT>
<P><FONT SIZE="2">Each Contributor must identify itself as the originator of its Contribution, if any, in a manner that reasonably allows subsequent Recipients to identify the originator of the Contribution. </FONT>
<P><FONT SIZE="2"></FONT>
<P><FONT SIZE="2"><B>4. COMMERCIAL DISTRIBUTION</B></FONT>
<P><FONT SIZE="2">Commercial distributors of software may accept certain responsibilities with respect to end users, business partners and the like. While this license is intended to facilitate the commercial use of the Program, the Contributor who includes the Program in a commercial product offering should do so in a manner which does not create potential liability for other Contributors. Therefore, if a Contributor includes the Program in a commercial product offering, such Contributor ("Commercial Contributor") hereby agrees to defend and indemnify every other Contributor ("Indemnified Contributor") against any losses, damages and costs (collectively "Losses") arising from claims, lawsuits and other legal actions brought by a third party against the Indemnified Contributor to the extent caused by the acts or omissions of such Commercial Contributor in connection with its distribution of the Program in a commercial product offering. The obligations in this section do not apply to any claims or Losses relating to any actual or alleged intellectual property infringement. In order to qualify, an Indemnified Contributor must: a) promptly notify the Commercial Contributor in writing of such claim, and b) allow the Commercial Contributor to control, and cooperate with the Commercial Contributor in, the defense and any related settlement negotiations. The Indemnified Contributor may participate in any such claim at its own expense.</FONT>
<P><FONT SIZE="2"></FONT>
<P><FONT SIZE="2">For example, a Contributor might include the Program in a commercial product offering, Product X. That Contributor is then a Commercial Contributor. If that Commercial Contributor then makes performance claims, or offers warranties related to Product X, those performance claims and warranties are such Commercial Contributor's responsibility alone. Under this section, the Commercial Contributor would have to defend claims against the other Contributors related to those performance claims and warranties, and if a court requires any other Contributor to pay any damages as a result, the Commercial Contributor must pay those damages.</FONT>
<P><FONT SIZE="2"></FONT><FONT SIZE="2" COLOR="#0000FF"></FONT>
<P><FONT SIZE="2" COLOR="#0000FF"></FONT><FONT SIZE="2"><B>5. NO WARRANTY</B></FONT>
<P><FONT SIZE="2">EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM IS PROVIDED ON AN "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Each Recipient is</FONT><FONT SIZE="2"> solely responsible for determining the appropriateness of using and distributing </FONT><FONT SIZE="2">the Program</FONT><FONT SIZE="2"> and assumes all risks associated with its exercise of rights under this Agreement</FONT><FONT SIZE="2">, including but not limited to the risks and costs of program errors, compliance with applicable laws, damage to or loss of data, </FONT><FONT SIZE="2">programs or equipment, and unavailability or interruption of operations</FONT><FONT SIZE="2">. </FONT><FONT SIZE="2"></FONT>
<P><FONT SIZE="2"></FONT>
<P><FONT SIZE="2"></FONT><FONT SIZE="2"><B>6. DISCLAIMER OF LIABILITY</B></FONT>
<P><FONT SIZE="2"></FONT><FONT SIZE="2">EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT NOR ANY CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES </FONT><FONT SIZE="2">(INCLUDING WITHOUT LIMITATION LOST PROFITS),</FONT><FONT SIZE="2"> HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OR DISTRIBUTION OF THE PROGRAM OR THE EXERCISE OF ANY RIGHTS GRANTED HEREUNDER, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.</FONT>
<P><FONT SIZE="2"></FONT><FONT SIZE="2"></FONT>
<P><FONT SIZE="2"><B>7. GENERAL</B></FONT>
<P><FONT SIZE="2"></FONT><FONT SIZE="2">If any provision of this Agreement is invalid or unenforceable under applicable law, it shall not affect the validity or enforceability of the remainder of the terms of this Agreement, and without further action by the parties hereto, such provision shall be reformed to the minimum extent necessary to make such provision valid and enforceable.</FONT>
<P><FONT SIZE="2"></FONT>
<P><FONT SIZE="2">If Recipient institutes patent litigation against a Contributor with respect to a patent applicable to software (including a cross-claim or counterclaim in a lawsuit), then any patent licenses granted by that Contributor to such Recipient under this Agreement shall terminate as of the date such litigation is filed. In addition, if Recipient institutes patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Program itself (excluding combinations of the Program with other software or hardware) infringes such Recipient's patent(s), then such Recipient's rights granted under Section 2(b) shall terminate as of the date such litigation is filed. </FONT><FONT SIZE="2"></FONT>
<P><FONT SIZE="2"></FONT>
<P><FONT SIZE="2">All Recipient's rights under this Agreement shall terminate if it fails to comply with any of the material terms or conditions of this Agreement and does not cure such failure in a reasonable period of time after becoming aware of such noncompliance. If all Recipient's rights under this Agreement terminate, Recipient agrees to cease use and distribution of the Program as soon as reasonably practicable. However, Recipient's obligations under this Agreement and any licenses granted by Recipient relating to the Program shall continue and survive. </FONT><FONT SIZE="2"></FONT>
<P><FONT SIZE="2"></FONT>
<P><FONT SIZE="2"></FONT><FONT SIZE="2">Everyone is permitted to copy and distribute copies of this Agreement, but in order to avoid inconsistency the Agreement is copyrighted and may only be modified in the following manner. The Agreement Steward reserves the right to </FONT><FONT SIZE="2">publish new versions (including revisions) of this Agreement from time to </FONT><FONT SIZE="2">time. No one other than the Agreement Steward has the right to modify this Agreement. IBM is the initial Agreement Steward. IBM may assign the responsibility to serve as the Agreement Steward to a suitable separate entity. </FONT><FONT SIZE="2">Each new version of the Agreement will be given a distinguishing version number. The Program (including Contributions) may always be distributed subject to the version of the Agreement under which it was received. In addition, after a new version of the Agreement is published, Contributor may elect to distribute the Program (including its Contributions) under the new </FONT><FONT SIZE="2">version. </FONT><FONT SIZE="2">Except as expressly stated in Sections 2(a) and 2(b) above, Recipient receives no rights or licenses to the intellectual property of any Contributor under this Agreement, whether expressly, </FONT><FONT SIZE="2">by implication, estoppel or otherwise</FONT><FONT SIZE="2">.</FONT><FONT SIZE="2"> All rights in the Program not expressly granted under this Agreement are reserved.</FONT>
<P><FONT SIZE="2"></FONT>
<P><FONT SIZE="2">This Agreement is governed by the laws of the State of New York and the intellectual property laws of the United States of America. No party to this Agreement will bring a legal action under this Agreement more than one year after the cause of action arose. Each party waives its rights to a jury trial in any resulting litigation.</FONT>
<P><FONT SIZE="2"></FONT><FONT SIZE="2"></FONT>
<P><FONT SIZE="2"></FONT>
</BODY>
</HTML>

BIN
TBE/Eclipse/eclipse/plugins/org.eclipse.pde.build_3.0.1/feature/eclipse_update_120.jpg Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 14 KiB

124
TBE/Eclipse/eclipse/plugins/org.eclipse.pde.build_3.0.1/feature/feature.properties Normal file
View File

@@ -0,0 +1,124 @@
###############################################################################
# Copyright (c) 2003, 2004 IBM Corporation and others.
# All rights reserved. This program and the accompanying materials
# are made available under the terms of the Common Public License v1.0
# which accompanies this distribution, and is available at
# http://www.eclipse.org/legal/cpl-v10.html
#
# Contributors:
# IBM Corporation - initial API and implementation
###############################################################################
# feature.properties
# contains externalized strings for feature.xml
# "%foo" in feature.xml corresponds to the key "foo" in this file
# java.io.Properties file (ISO 8859-1 with "\" escapes)
# This file should be translated.
# "featureName" property - name of the feature
featureName=Eclipse Builder
# "providerName" property - name of the company that provides the feature
providerName=Eclipse.org
# "updateSiteName" property - label for the update site
updateSiteName=Eclipse.org update site
# "description" property - description of the feature
description=The Eclipse builder
# "licenseURL" property - URL of the "Feature License"
# do not translate value - just change to point to a locale-specific HTML page
licenseURL=license.html
# "license" property - text of the "Feature Update License"
# should be plain text version of license agreement pointed to be "licenseURL"
license=\
ECLIPSE.ORG SOFTWARE USER AGREEMENT\n\
15th June, 2004\n\
\n\
Usage Of Content\n\
\n\
ECLIPSE.ORG 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 Eclipse.org\n\
is provided to you under the terms and conditions of the Common Public\n\
License Version 1.0 ("CPL"). A copy of the CPL is provided with this\n\
Content and is also available at http://www.eclipse.org/legal/cpl-v10.html.\n\
For purposes of the CPL, "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.org CVS\n\
repository ("Repository") in CVS modules ("Modules") and made available\n\
as downloadable archives ("Downloads").\n\
\n\
Content may be apportioned into plug-ins ("Plug-ins"), plug-in fragments\n\
("Fragments"), and features ("Features"). A Feature is a bundle of one or\n\
more Plug-ins and/or Fragments and associated material. Files named\n\
"feature.xml" may contain a list of the names and version numbers of the\n\
Plug-ins and/or Fragments associated with a Feature. Plug-ins and Fragments\n\
are located in directories named "plugins" and Features are located in\n\
directories named "features".\n\
\n\
Features may also include other Features ("Included Features"). Files named\n\
"feature.xml" may contain a list of the names and version numbers of\n\
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\
- Subdirectories of the directory named "src" of certain Plug-ins\n\
- Feature directories\n\
\n\
Note: if a Feature made available by Eclipse.org is installed using the\n\
Eclipse Update Manager, you must agree to a license ("Feature Update\n\
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". Such Abouts,\n\
Feature Licenses and Feature Update Licenses contain the terms and\n\
conditions (or references to such terms and conditions) that govern your\n\
use of the associated Content in that directory.\n\
\n\
THE ABOUTS, FEATURE LICENSES AND FEATURE UPDATE LICENSES MAY REFER\n\
TO THE CPL 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 Public License Version 1.0 (available at http://www.eclipse.org/legal/epl-v10.html)\n\
- Apache Software License 1.1 (available at http://www.apache.org/licenses/LICENSE)\n\
- IBM Public License 1.0 (available at http://oss.software.ibm.com/developerworks/opensource/license10.html)\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 Eclipse.org to determine what terms and conditions\n\
govern that particular Content.\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,\n\
and re-export of encryption software, to see if this is permitted.\n
########### end of license property ##########################################

105
TBE/Eclipse/eclipse/plugins/org.eclipse.pde.build_3.0.1/feature/feature.xml Normal file
View File

@@ -0,0 +1,105 @@
<?xml version="1.0" encoding="UTF-8"?>
<feature
id="org.eclipse.pde.builder"
label="%featureName"
version="3.0.0"
provider-name="%providerName"
image="eclipse_update_120.jpg"
primary="true"
application="org.eclipse.ant.core.antRunner">
<description>
%description
</description>
<plugin
id="org.apache.ant"
download-size="0"
install-size="0"
version="0.0.0"/>
<plugin
id="org.eclipse.ant.core"
download-size="0"
install-size="0"
version="0.0.0"/>
<plugin
id="org.eclipse.core.variables"
download-size="0"
install-size="0"
version="0.0.0"/>
<plugin
id="org.eclipse.text"
download-size="0"
install-size="0"
version="0.0.0"/>
<plugin
id="org.eclipse.core.resources"
download-size="0"
install-size="0"
version="0.0.0"/>
<plugin
id="org.eclipse.core.runtime"
download-size="0"
install-size="0"
version="0.0.0"/>
<plugin
id="org.eclipse.osgi"
download-size="0"
install-size="0"
version="0.0.0"/>
<plugin
id="org.eclipse.osgi.util"
download-size="0"
install-size="0"
version="0.0.0"/>
<plugin
id="org.eclipse.osgi.services"
download-size="0"
install-size="0"
version="0.0.0"/>
<plugin
id="org.eclipse.core.runtime.compatibility"
download-size="0"
install-size="0"
version="0.0.0"/>
<plugin
id="org.eclipse.jdt.core"
download-size="0"
install-size="0"
version="0.0.0"/>
<plugin
id="org.eclipse.pde.build"
download-size="0"
install-size="0"
version="0.0.0"/>
<plugin
id="org.eclipse.update.core"
download-size="0"
install-size="0"
version="0.0.0"/>
<plugin
id="org.eclipse.update.configurator"
download-size="0"
install-size="0"
version="0.0.0"/>
<plugin
id="org.eclipse.platform"
download-size="0"
install-size="0"
version="0.0.0"/>
</feature>

72
TBE/Eclipse/eclipse/plugins/org.eclipse.pde.build_3.0.1/feature/license.html Normal file
View File

@@ -0,0 +1,72 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
<html>
<head>
<meta http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<title>Eclipse.org Software User Agreement</title>
</head>
<body lang="EN-US" link=blue vlink=purple>
<h2>Eclipse.org Software User Agreement</h2>
<p>15<sup>th</sup> June, 2004</p>
<h3>Usage Of Content</h3>
<p>ECLIPSE.ORG MAKES AVAILABLE SOFTWARE, DOCUMENTATION, INFORMATION AND/OR OTHER MATERIALS FOR OPEN SOURCE PROJECTS
(COLLECTIVELY &quot;CONTENT&quot;). USE OF THE CONTENT IS GOVERNED BY THE TERMS AND CONDITIONS OF THIS AGREEMENT AND/OR THE TERMS AND
CONDITIONS OF LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW. BY USING THE CONTENT, YOU AGREE THAT YOUR USE
OF THE CONTENT IS GOVERNED BY THIS AGREEMENT AND/OR THE TERMS AND CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS OR
NOTICES INDICATED OR REFERENCED BELOW. IF YOU DO NOT AGREE TO THE TERMS AND CONDITIONS OF THIS AGREEMENT AND THE TERMS AND
CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW, THEN YOU MAY NOT USE THE CONTENT.</p>
<h3>Applicable Licenses</h3>
<p>Unless otherwise indicated, all Content made available by Eclipse.org is provided to you under the terms and conditions of the Common Public License Version 1.0
(&quot;CPL&quot;). A copy of the CPL is provided with this Content and is also available at <a href="http://www.eclipse.org/legal/cpl-v10.html">http://www.eclipse.org/legal/cpl-v10.html</a>.
For purposes of the CPL, &quot;Program&quot; will mean the Content.</p>
<p>Content includes, but is not limited to, source code, object code, documentation and other files maintained in the Eclipse.org CVS repository (&quot;Repository&quot;) in CVS
modules (&quot;Modules&quot;) and made available as downloadable archives (&quot;Downloads&quot;).</p>
<p>Content may be apportioned into plug-ins (&quot;Plug-ins&quot;), plug-in fragments (&quot;Fragments&quot;), and features (&quot;Features&quot;). A Feature is a bundle of one or more Plug-ins and/or Fragments and associated material. Files named &quot;feature.xml&quot; may contain a list of the names and version numbers of the Plug-ins and/or Fragments associated with a Feature. Plug-ins and Fragments are located in directories
named &quot;plugins&quot; and Features are located in directories named &quot;features&quot;.</p>
<p>Features may also include other Features (&quot;Included Features&quot;). Files named &quot;feature.xml&quot; may contain a list of the names and version numbers of Included Features.</p>
<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
Included 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
including, but not limited to the following locations:</p>
<ul>
<li>The top-level (root) directory</li>
<li>Plug-in and Fragment directories</li>
<li>Subdirectories of the directory named &quot;src&quot; of certain Plug-ins</li>
<li>Feature directories</li>
</ul>
<p>Note: if a Feature made available by Eclipse.org is installed using the Eclipse Update Manager, you must agree to a license (&quot;Feature Update License&quot;) during the
installation 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
inform 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;.
Such 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
that directory.</p>
<p>THE ABOUTS, FEATURE LICENSES AND FEATURE UPDATE LICENSES MAY REFER TO THE CPL OR OTHER LICENSE AGREEMENTS, NOTICES OR TERMS AND CONDITIONS. SOME OF THESE
OTHER LICENSE AGREEMENTS MAY INCLUDE (BUT ARE NOT LIMITED TO):</p>
<ul>
<li>Eclipse Public License Version 1.0 (available at <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>)</li>
<li>Apache Software License 1.1 (available at <a href="http://www.apache.org/licenses/LICENSE">http://www.apache.org/licenses/LICENSE</a>)</li>
<li>IBM Public License 1.0 (available at <a href="http://oss.software.ibm.com/developerworks/opensource/license10.html">http://oss.software.ibm.com/developerworks/opensource/license10.html</a>)</li>
<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>
<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>
</ul>
<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
contact Eclipse.org to determine what terms and conditions govern that particular Content.</p>
<h3>Cryptography</h3>
<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
another country, of encryption software. BEFORE using any encryption software, please check the country's laws, regulations and policies concerning the import,
possession, or use, and re-export of encryption software, to see if this is permitted.</p>
</body>
</html>

3
TBE/Eclipse/eclipse/plugins/org.eclipse.pde.build_3.0.1/feature/rootfiles/.eclipseproduct Normal file
View File

@@ -0,0 +1,3 @@
name=Eclipse Builder
id=org.eclipse.releng.builder
version=2.1.0

125
TBE/Eclipse/eclipse/plugins/org.eclipse.pde.build_3.0.1/feature/rootfiles/cpl-v10.html Normal file
View File

@@ -0,0 +1,125 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
<HTML>
<HEAD>
<TITLE>Common Public License - v 1.0</TITLE>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</HEAD>
<BODY BGCOLOR="#FFFFFF" VLINK="#800000">
<P ALIGN="CENTER"><B>Common Public License - v 1.0</B>
<P><B></B><FONT SIZE="3"></FONT>
<P><FONT SIZE="3"></FONT><FONT SIZE="2">THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS COMMON PUBLIC LICENSE ("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION OF THE PROGRAM CONSTITUTES RECIPIENT'S ACCEPTANCE OF THIS AGREEMENT.</FONT>
<P><FONT SIZE="2"></FONT>
<P><FONT SIZE="2"><B>1. DEFINITIONS</B></FONT>
<P><FONT SIZE="2">"Contribution" means:</FONT>
<UL><FONT SIZE="2">a) in the case of the initial Contributor, the initial code and documentation distributed under this Agreement, and<BR CLEAR="LEFT">
b) in the case of each subsequent Contributor:</FONT></UL>
<UL><FONT SIZE="2">i) changes to the Program, and</FONT></UL>
<UL><FONT SIZE="2">ii) additions to the Program;</FONT></UL>
<UL><FONT SIZE="2">where such changes and/or additions to the Program originate from and are distributed by that particular Contributor. </FONT><FONT SIZE="2">A Contribution 'originates' from a Contributor if it was added to the Program by such Contributor itself or anyone acting on such Contributor's behalf. </FONT><FONT SIZE="2">Contributions do not include additions to the Program which: (i) are separate modules of software distributed in conjunction with the Program under their own license agreement, and (ii) are not derivative works of the Program. </FONT></UL>
<P><FONT SIZE="2"></FONT>
<P><FONT SIZE="2">"Contributor" means any person or entity that distributes the Program.</FONT>
<P><FONT SIZE="2"></FONT><FONT SIZE="2"></FONT>
<P><FONT SIZE="2">"Licensed Patents " mean patent claims licensable by a Contributor which are necessarily infringed by the use or sale of its Contribution alone or when combined with the Program. </FONT>
<P><FONT SIZE="2"></FONT><FONT SIZE="2"></FONT>
<P><FONT SIZE="2"></FONT><FONT SIZE="2">"Program" means the Contributions distributed in accordance with this Agreement.</FONT>
<P><FONT SIZE="2"></FONT>
<P><FONT SIZE="2">"Recipient" means anyone who receives the Program under this Agreement, including all Contributors.</FONT>
<P><FONT SIZE="2"><B></B></FONT>
<P><FONT SIZE="2"><B>2. GRANT OF RIGHTS</B></FONT>
<UL><FONT SIZE="2"></FONT><FONT SIZE="2">a) </FONT><FONT SIZE="2">Subject to the terms of this Agreement, each Contributor hereby grants</FONT><FONT SIZE="2"> Recipient a non-exclusive, worldwide, royalty-free copyright license to</FONT><FONT SIZE="2" COLOR="#FF0000"> </FONT><FONT SIZE="2">reproduce, prepare derivative works of, publicly display, publicly perform, distribute and sublicense the Contribution of such Contributor, if any, and such derivative works, in source code and object code form.</FONT></UL>
<UL><FONT SIZE="2"></FONT></UL>
<UL><FONT SIZE="2"></FONT><FONT SIZE="2">b) Subject to the terms of this Agreement, each Contributor hereby grants </FONT><FONT SIZE="2">Recipient a non-exclusive, worldwide,</FONT><FONT SIZE="2" COLOR="#008000"> </FONT><FONT SIZE="2">royalty-free patent license under Licensed Patents to make, use, sell, offer to sell, import and otherwise transfer the Contribution of such Contributor, if any, in source code and object code form. This patent license shall apply to the combination of the Contribution and the Program if, at the time the Contribution is added by the Contributor, such addition of the Contribution causes such combination to be covered by the Licensed Patents. The patent license shall not apply to any other combinations which include the Contribution. No hardware per se is licensed hereunder. </FONT></UL>
<UL><FONT SIZE="2"></FONT></UL>
<UL><FONT SIZE="2">c) Recipient understands that although each Contributor grants the licenses to its Contributions set forth herein, no assurances are provided by any Contributor that the Program does not infringe the patent or other intellectual property rights of any other entity. Each Contributor disclaims any liability to Recipient for claims brought by any other entity based on infringement of intellectual property rights or otherwise. As a condition to exercising the rights and licenses granted hereunder, each Recipient hereby assumes sole responsibility to secure any other intellectual property rights needed, if any. For example, if a third party patent license is required to allow Recipient to distribute the Program, it is Recipient's responsibility to acquire that license before distributing the Program.</FONT></UL>
<UL><FONT SIZE="2"></FONT></UL>
<UL><FONT SIZE="2">d) Each Contributor represents that to its knowledge it has sufficient copyright rights in its Contribution, if any, to grant the copyright license set forth in this Agreement. </FONT></UL>
<UL><FONT SIZE="2"></FONT></UL>
<P><FONT SIZE="2"><B>3. REQUIREMENTS</B></FONT>
<P><FONT SIZE="2"><B></B>A Contributor may choose to distribute the Program in object code form under its own license agreement, provided that:</FONT>
<UL><FONT SIZE="2">a) it complies with the terms and conditions of this Agreement; and</FONT></UL>
<UL><FONT SIZE="2">b) its license agreement:</FONT></UL>
<UL><FONT SIZE="2">i) effectively disclaims</FONT><FONT SIZE="2"> on behalf of all Contributors all warranties and conditions, express and implied, including warranties or conditions of title and non-infringement, and implied warranties or conditions of merchantability and fitness for a particular purpose; </FONT></UL>
<UL><FONT SIZE="2">ii) effectively excludes on behalf of all Contributors all liability for damages, including direct, indirect, special, incidental and consequential damages, such as lost profits; </FONT></UL>
<UL><FONT SIZE="2">iii)</FONT><FONT SIZE="2"> states that any provisions which differ from this Agreement are offered by that Contributor alone and not by any other party; and</FONT></UL>
<UL><FONT SIZE="2">iv) states that source code for the Program is available from such Contributor, and informs licensees how to obtain it in a reasonable manner on or through a medium customarily used for software exchange.</FONT><FONT SIZE="2" COLOR="#0000FF"> </FONT><FONT SIZE="2" COLOR="#FF0000"></FONT></UL>
<UL><FONT SIZE="2" COLOR="#FF0000"></FONT><FONT SIZE="2"></FONT></UL>
<P><FONT SIZE="2">When the Program is made available in source code form:</FONT>
<UL><FONT SIZE="2">a) it must be made available under this Agreement; and </FONT></UL>
<UL><FONT SIZE="2">b) a copy of this Agreement must be included with each copy of the Program. </FONT></UL>
<P><FONT SIZE="2"></FONT><FONT SIZE="2" COLOR="#0000FF"><STRIKE></STRIKE></FONT>
<P><FONT SIZE="2" COLOR="#0000FF"><STRIKE></STRIKE></FONT><FONT SIZE="2">Contributors may not remove or alter any copyright notices contained within the Program. </FONT>
<P><FONT SIZE="2"></FONT>
<P><FONT SIZE="2">Each Contributor must identify itself as the originator of its Contribution, if any, in a manner that reasonably allows subsequent Recipients to identify the originator of the Contribution. </FONT>
<P><FONT SIZE="2"></FONT>
<P><FONT SIZE="2"><B>4. COMMERCIAL DISTRIBUTION</B></FONT>
<P><FONT SIZE="2">Commercial distributors of software may accept certain responsibilities with respect to end users, business partners and the like. While this license is intended to facilitate the commercial use of the Program, the Contributor who includes the Program in a commercial product offering should do so in a manner which does not create potential liability for other Contributors. Therefore, if a Contributor includes the Program in a commercial product offering, such Contributor ("Commercial Contributor") hereby agrees to defend and indemnify every other Contributor ("Indemnified Contributor") against any losses, damages and costs (collectively "Losses") arising from claims, lawsuits and other legal actions brought by a third party against the Indemnified Contributor to the extent caused by the acts or omissions of such Commercial Contributor in connection with its distribution of the Program in a commercial product offering. The obligations in this section do not apply to any claims or Losses relating to any actual or alleged intellectual property infringement. In order to qualify, an Indemnified Contributor must: a) promptly notify the Commercial Contributor in writing of such claim, and b) allow the Commercial Contributor to control, and cooperate with the Commercial Contributor in, the defense and any related settlement negotiations. The Indemnified Contributor may participate in any such claim at its own expense.</FONT>
<P><FONT SIZE="2"></FONT>
<P><FONT SIZE="2">For example, a Contributor might include the Program in a commercial product offering, Product X. That Contributor is then a Commercial Contributor. If that Commercial Contributor then makes performance claims, or offers warranties related to Product X, those performance claims and warranties are such Commercial Contributor's responsibility alone. Under this section, the Commercial Contributor would have to defend claims against the other Contributors related to those performance claims and warranties, and if a court requires any other Contributor to pay any damages as a result, the Commercial Contributor must pay those damages.</FONT>
<P><FONT SIZE="2"></FONT><FONT SIZE="2" COLOR="#0000FF"></FONT>
<P><FONT SIZE="2" COLOR="#0000FF"></FONT><FONT SIZE="2"><B>5. NO WARRANTY</B></FONT>
<P><FONT SIZE="2">EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM IS PROVIDED ON AN "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Each Recipient is</FONT><FONT SIZE="2"> solely responsible for determining the appropriateness of using and distributing </FONT><FONT SIZE="2">the Program</FONT><FONT SIZE="2"> and assumes all risks associated with its exercise of rights under this Agreement</FONT><FONT SIZE="2">, including but not limited to the risks and costs of program errors, compliance with applicable laws, damage to or loss of data, </FONT><FONT SIZE="2">programs or equipment, and unavailability or interruption of operations</FONT><FONT SIZE="2">. </FONT><FONT SIZE="2"></FONT>
<P><FONT SIZE="2"></FONT>
<P><FONT SIZE="2"></FONT><FONT SIZE="2"><B>6. DISCLAIMER OF LIABILITY</B></FONT>
<P><FONT SIZE="2"></FONT><FONT SIZE="2">EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT NOR ANY CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES </FONT><FONT SIZE="2">(INCLUDING WITHOUT LIMITATION LOST PROFITS),</FONT><FONT SIZE="2"> HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OR DISTRIBUTION OF THE PROGRAM OR THE EXERCISE OF ANY RIGHTS GRANTED HEREUNDER, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.</FONT>
<P><FONT SIZE="2"></FONT><FONT SIZE="2"></FONT>
<P><FONT SIZE="2"><B>7. GENERAL</B></FONT>
<P><FONT SIZE="2"></FONT><FONT SIZE="2">If any provision of this Agreement is invalid or unenforceable under applicable law, it shall not affect the validity or enforceability of the remainder of the terms of this Agreement, and without further action by the parties hereto, such provision shall be reformed to the minimum extent necessary to make such provision valid and enforceable.</FONT>
<P><FONT SIZE="2"></FONT>
<P><FONT SIZE="2">If Recipient institutes patent litigation against a Contributor with respect to a patent applicable to software (including a cross-claim or counterclaim in a lawsuit), then any patent licenses granted by that Contributor to such Recipient under this Agreement shall terminate as of the date such litigation is filed. In addition, if Recipient institutes patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Program itself (excluding combinations of the Program with other software or hardware) infringes such Recipient's patent(s), then such Recipient's rights granted under Section 2(b) shall terminate as of the date such litigation is filed. </FONT><FONT SIZE="2"></FONT>
<P><FONT SIZE="2"></FONT>
<P><FONT SIZE="2">All Recipient's rights under this Agreement shall terminate if it fails to comply with any of the material terms or conditions of this Agreement and does not cure such failure in a reasonable period of time after becoming aware of such noncompliance. If all Recipient's rights under this Agreement terminate, Recipient agrees to cease use and distribution of the Program as soon as reasonably practicable. However, Recipient's obligations under this Agreement and any licenses granted by Recipient relating to the Program shall continue and survive. </FONT><FONT SIZE="2"></FONT>
<P><FONT SIZE="2"></FONT>
<P><FONT SIZE="2"></FONT><FONT SIZE="2">Everyone is permitted to copy and distribute copies of this Agreement, but in order to avoid inconsistency the Agreement is copyrighted and may only be modified in the following manner. The Agreement Steward reserves the right to </FONT><FONT SIZE="2">publish new versions (including revisions) of this Agreement from time to </FONT><FONT SIZE="2">time. No one other than the Agreement Steward has the right to modify this Agreement. IBM is the initial Agreement Steward. IBM may assign the responsibility to serve as the Agreement Steward to a suitable separate entity. </FONT><FONT SIZE="2">Each new version of the Agreement will be given a distinguishing version number. The Program (including Contributions) may always be distributed subject to the version of the Agreement under which it was received. In addition, after a new version of the Agreement is published, Contributor may elect to distribute the Program (including its Contributions) under the new </FONT><FONT SIZE="2">version. </FONT><FONT SIZE="2">Except as expressly stated in Sections 2(a) and 2(b) above, Recipient receives no rights or licenses to the intellectual property of any Contributor under this Agreement, whether expressly, </FONT><FONT SIZE="2">by implication, estoppel or otherwise</FONT><FONT SIZE="2">.</FONT><FONT SIZE="2"> All rights in the Program not expressly granted under this Agreement are reserved.</FONT>
<P><FONT SIZE="2"></FONT>
<P><FONT SIZE="2">This Agreement is governed by the laws of the State of New York and the intellectual property laws of the United States of America. No party to this Agreement will bring a legal action under this Agreement more than one year after the cause of action arose. Each party waives its rights to a jury trial in any resulting litigation.</FONT>
<P><FONT SIZE="2"></FONT><FONT SIZE="2"></FONT>
<P><FONT SIZE="2"></FONT>
</BODY>
</HTML>

14
TBE/Eclipse/eclipse/plugins/org.eclipse.pde.build_3.0.1/feature/rootfiles/install.ini Normal file
View File

@@ -0,0 +1,14 @@
# install.ini
# java.io.Properties file (ISO 8859-1 with "\" escapes)
# This file does not need to be translated.
# Required property "feature.default.id" contains id of the primary feature
# (the primary feature controls product branding, splash screens, and plug-in
# customization)
feature.default.id=org.eclipse.pde.builder
# Required property "feature.default.application" contains id of the core
# application that gets control on startup. For products with a UI, this
# is always org.eclipse.ui.workbench; for "headless" products, this is
# product-specific.
feature.default.application=org.eclipse.ant.core.antRunner

72
TBE/Eclipse/eclipse/plugins/org.eclipse.pde.build_3.0.1/feature/rootfiles/notice.html Normal file
View File

@@ -0,0 +1,72 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
<html>
<head>
<meta http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<title>Eclipse.org Software User Agreement</title>
</head>
<body lang="EN-US" link=blue vlink=purple>
<h2>Eclipse.org Software User Agreement</h2>
<p>15<sup>th</sup> June, 2004</p>
<h3>Usage Of Content</h3>
<p>ECLIPSE.ORG MAKES AVAILABLE SOFTWARE, DOCUMENTATION, INFORMATION AND/OR OTHER MATERIALS FOR OPEN SOURCE PROJECTS
(COLLECTIVELY &quot;CONTENT&quot;). USE OF THE CONTENT IS GOVERNED BY THE TERMS AND CONDITIONS OF THIS AGREEMENT AND/OR THE TERMS AND
CONDITIONS OF LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW. BY USING THE CONTENT, YOU AGREE THAT YOUR USE
OF THE CONTENT IS GOVERNED BY THIS AGREEMENT AND/OR THE TERMS AND CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS OR
NOTICES INDICATED OR REFERENCED BELOW. IF YOU DO NOT AGREE TO THE TERMS AND CONDITIONS OF THIS AGREEMENT AND THE TERMS AND
CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW, THEN YOU MAY NOT USE THE CONTENT.</p>
<h3>Applicable Licenses</h3>
<p>Unless otherwise indicated, all Content made available by Eclipse.org is provided to you under the terms and conditions of the Common Public License Version 1.0
(&quot;CPL&quot;). A copy of the CPL is provided with this Content and is also available at <a href="http://www.eclipse.org/legal/cpl-v10.html">http://www.eclipse.org/legal/cpl-v10.html</a>.
For purposes of the CPL, &quot;Program&quot; will mean the Content.</p>
<p>Content includes, but is not limited to, source code, object code, documentation and other files maintained in the Eclipse.org CVS repository (&quot;Repository&quot;) in CVS
modules (&quot;Modules&quot;) and made available as downloadable archives (&quot;Downloads&quot;).</p>
<p>Content may be apportioned into plug-ins (&quot;Plug-ins&quot;), plug-in fragments (&quot;Fragments&quot;), and features (&quot;Features&quot;). A Feature is a bundle of one or more Plug-ins and/or Fragments and associated material. Files named &quot;feature.xml&quot; may contain a list of the names and version numbers of the Plug-ins and/or Fragments associated with a Feature. Plug-ins and Fragments are located in directories
named &quot;plugins&quot; and Features are located in directories named &quot;features&quot;.</p>
<p>Features may also include other Features (&quot;Included Features&quot;). Files named &quot;feature.xml&quot; may contain a list of the names and version numbers of Included Features.</p>
<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
Included 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
including, but not limited to the following locations:</p>
<ul>
<li>The top-level (root) directory</li>
<li>Plug-in and Fragment directories</li>
<li>Subdirectories of the directory named &quot;src&quot; of certain Plug-ins</li>
<li>Feature directories</li>
</ul>
<p>Note: if a Feature made available by Eclipse.org is installed using the Eclipse Update Manager, you must agree to a license (&quot;Feature Update License&quot;) during the
installation 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
inform 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;.
Such 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
that directory.</p>
<p>THE ABOUTS, FEATURE LICENSES AND FEATURE UPDATE LICENSES MAY REFER TO THE CPL OR OTHER LICENSE AGREEMENTS, NOTICES OR TERMS AND CONDITIONS. SOME OF THESE
OTHER LICENSE AGREEMENTS MAY INCLUDE (BUT ARE NOT LIMITED TO):</p>
<ul>
<li>Eclipse Public License Version 1.0 (available at <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>)</li>
<li>Apache Software License 1.1 (available at <a href="http://www.apache.org/licenses/LICENSE">http://www.apache.org/licenses/LICENSE</a>)</li>
<li>IBM Public License 1.0 (available at <a href="http://oss.software.ibm.com/developerworks/opensource/license10.html">http://oss.software.ibm.com/developerworks/opensource/license10.html</a>)</li>
<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>
<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>
</ul>
<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
contact Eclipse.org to determine what terms and conditions govern that particular Content.</p>
<h3>Cryptography</h3>
<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
another country, of encryption software. BEFORE using any encryption software, please check the country's laws, regulations and policies concerning the import,
possession, or use, and re-export of encryption software, to see if this is permitted.</p>
</body>
</html>

1401
TBE/Eclipse/eclipse/plugins/org.eclipse.pde.build_3.0.1/feature/rootfiles/readme/readme_eclipse.html Normal file
View File

File diff suppressed because it is too large Load Diff

BIN
TBE/Eclipse/eclipse/plugins/org.eclipse.pde.build_3.0.1/lib/pdebuild-ant.jar Normal file
View File

Binary file not shown.

220
TBE/Eclipse/eclipse/plugins/org.eclipse.pde.build_3.0.1/notes/m2 notes.html Normal file
View File

@@ -0,0 +1,220 @@
<html>
<head>
<meta http-equiv="Content-Language" content="en-us">
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
<meta name="GENERATOR" content="Microsoft FrontPage 4.0">
<meta name="ProgId" content="FrontPage.Editor.Document">
<title>Eclipse 3.0 M2 News</title>
</head>
<body>
<table border="0" cellpadding="10" cellspacing="0">
<tr>
<td colspan="2">
<hr>
</td>
</tr>
<tr>
<td width="30%" valign="top" align="left">
<p align="right"><b><font face="Verdana" size="2">Introduction of new properties in the build.properties file of feature</font></b></p>
<td width="70%" valign="top" align="left">
<p><font face="Verdana" size="2">When building an eclipse based product from features, it is now possible to copy files or directories to the eclipse directory. This is achieved thanks to the following properties:
<ul>
root=a comma separated list of files and directories
</ul>
To refer to a file prefix the name with "file:", to refer to a directory, simply list the name.
<P>
It is also possible to set permissions on those root files:
<ul>
root.permissions.XXX=a comma separated list of files and directories
</ul>
where XXX is a unix chmod style permission description.
It is also possible to copy files and apply permissions on a configuration basis
<ul>
root.configName=
root.configName.permissions.XXX=
</ul>
where configName is a doted description of the platform (os.ws.arch).
Here an example for org.eclipse.platform
<ul>
root=eclipse
root.macosx.carbon.ppc=macosx.carbon,../../plugins/platform-launcher/bin/macosx
root.macosx.carbon.ppc.link=Eclipse.app/Contents/MacOS/eclipse,eclipse
root.macosx.carbon.ppc.permissions.755=Eclipse.app/Contents/MacOS/eclipse
</ul>
It is also possible to trigger the generation of source features and plugins
<ul>
generate.feature@nameOfTheFeatureToGenerate=featureName, plugin@XXXX
</ul>
generate a feature called 'nameOfTheFeatureToGenerate' from the plugins contained in the feature called 'featureName' and also include the plugin xxxx
<ul>
Example : generate.feature@org.eclipse.jdt.source=org.eclipse.jdt, plugin@org.eclipse.jdt.doc.isv</font></p>
</ul>
</td>
<tr>
<td colspan="2">
<hr>
</td>
</tr>
<tr>
<td width="30%" valign="top" align="left">
<p align="right"><b><font face="Verdana" size="2">
Introduction of new properties in the build.properties file of plugin</font></b></p>
<td width="70%" valign="top" align="left">
<p><font face="Verdana" size="2">
For every jar file that is being built three variables can be provided. Note that "{jarname}" describes the name of the jar file including its path relative to the project.
<ul>
<li>a variable named "source.{jarname}" describing where the source of the jar
can be found. The expected value is a path relative to the project (for example "src/").</li>
<li>a variable named "output.{jarname}" describing where the bin of the jar can
be found. The expected value is a path relative to the project (for
example "bin/").</li>
<li>a variable named "extra.{jarname}" describing the list of jars required to
compile this jar. The expected values are paths relative to the place where the
project is.</li>
</ul>
A short way to explain the content of those variables is to see them as variables used for the compilation:
<ul>
<li>the source indicates where to find the source of the jar.</li>
<li>the extra gives extra values to be put at the end of the classpath when we
are compiling the source.</li>
<li>the output indicates where the content of a compiled version of the library
exists (this is typically used in the classpath of plugins requiring this jar).</li>
</font></p>
</td>
</tr>
<tr>
<td colspan="2">
<hr>
</td>
</tr>
<tr>
<td width="30%" valign="top" align="left">
<p align="right"><b><font face="Verdana" size="2">Setting permissions on a per basis plugin</font></b></p>
<td width="70%" valign="top" align="left">
<p><font face="Verdana" size="2">During a build it is now possible to set permissions and create links on a per plugin basis. Those information are listed in a file called permissions.properties provided at the root of the plugin (as a sibling of build.properties). The format of the file is as follow:
<ul><ol>permissions.executable=list of files </ol>
<ol>permissions.link=list of files</ol>
<ol>permissions.XXX=list of files</ol>
</ul>
</font></p>
</td>
</tr>
<tr>
<td colspan="2">
<hr>
</td>
</tr>
<tr>
<td width="30%" valign="top" align="left">
<p align="right"><b><font face="Verdana" size="2">Enhancement of the map file</font></b></p>
<td width="70%" valign="top" align="left">
<p><font face="Verdana" size="2">The map file entries have been enhanced to allow plugins and features to be located anywhere in a cvs repository.<p>
feature|fragment|plugin@elementID=versionName,CVSRepository,passwordInfo,pathInTheRepository (no starting slash)
<p>
example:
feature@com.foo=v101,:pserver:anon@foo.com:/home/cvs,,a/b/foo-feature</font></p>
</td>
</tr>
<tr>
<td colspan="2">
<hr>
</td>
</tr>
<tr>
<td width="30%" valign="top" align="left">
<p align="right"><b><font face="Verdana" size="2">New properties introduced to control the compilation of plugins</font></b></p>
<td width="70%" valign="top" align="left">
<p><font face="Verdana" size="2">
javacSource: Give the format of the source code. Legal values are 1.3 and 1.4.<br>
javacTarget: Generate class files for specific VM version.<br>
javacFailOnError: Indicates whether the build will continue even if there are compilation errors.<br>
javacDebugInfo: Indicates whether source should be compiled with debug information.<br>
javacVerbose: Asks the compiler for verbose output.<br>
bootclasspath: Set the classpath of the jdk you compile against.<br>
All those properties are surfaced in the pde ui.</font></p>
</td>
</tr>
<tr>
<td colspan="2">
<hr>
</td>
</tr>
<tr>
<td width="30%" valign="top" align="left">
<p align="right"><b><font face="Verdana" size="2">Reusable automated build process</font></b></p>
<td width="70%" valign="top" align="left">
<p><font face="Verdana" size="2">The new pde build process ease the creation of automated build process by providing a set of template scripts and a general script. Those scripts and templates are used to build the 3.0 build of eclipse (see the project org.eclipse.releng.eclipsebuilder). A small example of their usage is also provided in the feature folder of the plugin.
</font></p>
</td>
</tr>
<tr>
<td colspan="2">
<hr>
</td>
</tr>
<tr>
<td width="30%" valign="top" align="left">
<p align="right"><b><font face="Verdana" size="2">Filling version numbers of features</font></b></p>
<td width="70%" valign="top" align="left">
<p><font face="Verdana" size="2">In the features, version numbers for nested features and plugins can now be specified to 0.0.0 and will be filled in by the appropriate values by the pde build engine.
</font></p>
</td>
</tr>
</table>
</body>
</html>

252
TBE/Eclipse/eclipse/plugins/org.eclipse.pde.build_3.0.1/notes/usingPDEBuild.html Normal file
View File

@@ -0,0 +1,252 @@
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<title>Using PDE Core to build Plug-ins, Fragments and Features</title>
</head>
<body>
<h2>What is PDE Build?</h2>
PDE Build is a plug-in that helps users build their own plug-ins. The term build here is related to deployment
and not development. PDE Build takes an Eclipse Plug-in Project, its plugin.xml and build.properties
files and generates a build.xml script to be run by Ant. Building plug-ins, fragments or features consists of the
3 stages: <em>fetch</em>, <em>generate scripts</em> and <em>build</em> that are described bellow.
<p>
<b>Fetch</b><br>
Consists of taking the interesting elements from a repository to the build machine. These elements can be
plug-ins, fragments or features. &quot;Directory files&quot; or &quot;map files&quot; are responsible for identifying
where, how and which plug-ins should go to the build machine. These files are basically Java properties files
where the entries have the following format:
<p>
<tt>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; element@element_id=tag,:connection_type:user@host:repository</tt>
<p>
The current implementation of fetch only works against CVS repositories and there are no plans for supporting
different kinds. Skipping or substituting this step should not be hard for users of other VCM systems or other kind
of storage.
<p>
Examples:
<p>
<tt>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; plugin@org.eclipse.pde.build=v20020717, :pserver:anonymous@dev.eclipse.org:/home/eclipse,<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; fragment@org.eclipse.core.resources.win32=v20020627, :pserver:anonymous@dev.eclipse.org:/home/eclipse, <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; plugin@org.eclipse.platform=v20020820, :pserver:anonymous@dev.eclipse.org:/home/eclipse, <br>
</tt>
<p>
<b>Generate Ant buildfiles</b><br>
Once the plug-ins, fragments and features are in
place, we need to generate the build.xml scripts. These Ant buildfiles drive
the build process. In order to generate them, PDE Build takes as input the plugin.xml, fragment.xml, feature.xml and build.properties files. The complete
description of the first three files are elsewhere in the Eclipse documentation. Here we will only fully
describe the build.properties file and relevant parts of the others.
<p>
<b>Build</b><br>
This step is basically executed by Ant. One important thing here is
to know exactly what targets to call in order to get the desired result.
<p>
<h2>How do I use PDE Build?</h2>
<h3>Fetch</h3>
This step is done by the <code>eclipse.fetch</code>
Ant task provided by PDE Build. Here is an example:
<pre>
&lt;eclipse.fetch
&nbsp;&nbsp;&nbsp;&nbsp;scriptName=<font COLOR="#008000">&quot;fetch.xml&quot;</font>
&nbsp;&nbsp;&nbsp;&nbsp;elements=<font COLOR="#008000">&quot;feature@org.eclipse.platform-feature&quot;</font>
&nbsp;&nbsp;&nbsp;&nbsp;directory=<font COLOR="#008000">&quot;${basedir}/test.map&quot;</font>
&nbsp;&nbsp;&nbsp;&nbsp;install=<font COLOR="#008000">&quot;${basedir}/source&quot;</font>
&nbsp;&nbsp;&nbsp; children=<font COLOR="#008000">&quot;true&quot;</font>
/&gt;
</pre>
The above task generates an Ant buildfile called <em>fetch.xml</em>. It consists of Ant
CVS tasks that retrieve the Eclipse Platform feature and all its plug-ins and
fragments.
<p>
<h2>Generate Scripts</h2>
<p>
Once features, plug-ins and fragments are downloaded you
need to generate their Ant buildfiles. This step is done by the <code>eclipse.buildScripts</code>
Ant task provided by PDE Build. Here is an example:
<pre>
&lt;eclipse.buildScript
&nbsp;&nbsp;&nbsp;&nbsp;elements=<font COLOR="#008000">&quot;feature@org.eclipse.platform-feature&quot;</font>
&nbsp;&nbsp;&nbsp;&nbsp;install=<font COLOR="#008000">&quot;${basedir}/source&quot;</font>
&nbsp;&nbsp;&nbsp;&nbsp;children=<font COLOR="#008000">&quot;true&quot;</font>
/&gt;
</pre>
The above task will generate Ant buildfiles for the
Eclipse Platform feature and all its plug-ins and fragments.
<p>
<b>build.properties</b>
<br>
The build mechanism is driven by a build specification.
The specification for an individual plug-in, fragment, or feature is found
in a build.properties file in the corresponding element (feature, plug-in or
fragment). It is a simple
properties file that describes, for example, where to find the source code for the element.&nbsp;
Other entries describe which files should be included/excluded in/from
various forms of distribution (e.g., binary, source). The possible entries
are described bellow:
<p>
<b><code>custom = yes</code></b><br>
Tells the script generator that no script is necessary
for the current element. It is usually used when a custom build.xml script
is provided. The build.xml script has to be in the root folder of the element.
<p><b>bin.includes =</b>
<br><b>bin.excludes =</b>
<p><b>source.&lt;jar_name>=&lt;source_locations></b>
<br>&nbsp;&nbsp;&nbsp; Indicates, for the specified jar, where to find
its source. The source_locations is a comma-separated list of <b><font color="#CC0000">[element-relative?]</font></b>
locations. Plug-ins <b><font color="#CC0000">[elements?]</font></b> requiring
compilation must define this entry.
<br>&nbsp;&nbsp;&nbsp; Example:
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; source.resources.jar = src/
<p style="margin-top: 0; margin-bottom: 0">&nbsp;<p style="margin-top: 0; margin-bottom: 0"><b>jars.compile.order =</b>
&lt;comma separated list of JARs&gt;<br>&nbsp;&nbsp;&nbsp; Specifies in what order the
JARs should be compiled. Should be used to solve build dependencies within the
same plug-in/fragment.<p style="margin-top: 0; margin-bottom: 0">&nbsp;&nbsp;&nbsp;
Example:<p style="margin-top: 0; margin-bottom: 0">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
jars.compile.order=resources.jar,lib/resources-ant.jar
<p>
<h2>Build</h2>
The generated build.xml scripts from the previous step have many targets. The
public ones described bellow. These are the targets that a custom build.xml script
<em>must</em> implement.
<p><b><font size=+2>Feature targets:</font></b>
<p><b>all.children</b>
<br>&nbsp;&nbsp;&nbsp; Calls plugin-template and fragment-template.
<p><b>all.plugins</b>
<br>&nbsp;&nbsp;&nbsp; Delegates target calls to all the feature's plug-ins.
<p><b>all.fragments</b>
<br>&nbsp;&nbsp;&nbsp; Delegates target calls to all the feature's fragments.
<p><b>build.jars</b>
<br>&nbsp;&nbsp;&nbsp; Generates the required jars for the feature and
its children.
<p><b>build.sources</b>
<br>&nbsp;&nbsp;&nbsp; Creates all the *src.zip files corresponding to
this feature's jars and its children. E.g. for startup.jar, it creates
startupsrc.zip .
<p><b>build.update.jar</b>
<br>&nbsp;&nbsp;&nbsp; Creates a jar file containing a binary build of
the feature. Source is not included. The jar is in a format supported by
install/update.
<p><b>gather.bin.parts</b>
<br>&nbsp;&nbsp;&nbsp; Copies all feature relevant parts (defined by <b>bin.includes</b>
and <b>bin.excludes</b>) to ${destination}/install/features/${feature}.
<p><b>gather.logs</b>
<br>&nbsp;&nbsp;&nbsp; Copies *.log files to ${destination}/install/features/${feature}.
<p><b>gather.sources</b>
<br>&nbsp;&nbsp;&nbsp; Copies files generated by <b>build.sources</b> (*src.zip)
to ${destination}/install/features/${feature}.
<br>&nbsp;
<p><b><font size=+2>Plug-ins and fragments targets:</font></b>
<p><b>build.jars</b>
<br>&nbsp;&nbsp;&nbsp; Generates the required jars for this plugin/fragment.
<p><b>build.sources</b>
<br>&nbsp;&nbsp;&nbsp; Creates all the *src.zip files corresponding to
this element's jars. E.g. for resources.jar, it creates resourcessrc.zip
.
<p><b>build.update.jar</b>
<br>&nbsp;&nbsp;&nbsp; Creates a jar file containing a binary build of
the element. Source is not included. The jar is in a format supported by
install/update.
<p><b>clean</b>
<br>&nbsp;&nbsp;&nbsp; Cleans all temp files and folders plus files created
by the script targets (e.g. *.jar, *.zip, ...).
<p><b>gather.bin.parts</b>
<br>&nbsp;&nbsp;&nbsp; Copies all plugin relevant parts (defined by <b>bin.includes</b>
and <b>bin.excludes</b>) to ${destination}/(plugins | fragments)/(${plugin}
| ${fragment}). E.g., ${destination}/plugins/${plugin}.
<p><b>gather.logs</b>
<br>&nbsp;&nbsp;&nbsp; Copies *.log files to ${destination}/(plugins |
fragments)/(${plugin} | ${fragment}). E.g., ${destination}/plugins/${plugin}.
<p><b>gather.sources</b>
<br>&nbsp;&nbsp;&nbsp; Copies files generated by <b>build.sources</b> (*src.zip)
to ${destination}/(plugins | fragments)/(${plugin} | ${fragment}). E.g.,
${destination}/plugins/${plugin}.
<p>
<h2>General notes on PDE Build</h2>
This section is not organized in any way. It just contains
general knowledge on the use and implementation of the PDE Build plug-in.
Although it should be up to date there is no guarantee about it. Check with your
favorite pde build developer before making any assumptions based on it.
<p>
<ul>
<li>units are features, plug-ins and fragments</li>
<li>Ant is the base technology</li>
<li>CVS is the supported repository for the fetch task</li>
<li>The build basically consists of these steps: fetch, generate buildfiles
and build. Te steps are triggered by Ant tasks defined by pde build.</li>
<li>Besides the basic steps any other step can be included by the releng team.
It will only depend on the bootstrap buildfile. This buildfile is not
generated by the pde.build.</li>
<li>Features, plug-ins and fragments can have custom build scripts as long as
they conform with the API (automatically generated script).</li>
<li>The Ant buildfiles generate by pde build have to run in 2 different
environments correctly: headless (Eclipse releng style) and the Eclipse UI.</li>
<li>When implementing a new functionality or changing an existing one there
are two modes to consider. One is the build running headless like the releng
does and the other is the script being executed by a user of Eclipse using the
external tools UI. They can have completely different characteristics and
point of views. If one assumption is correct for one of these scenarios it
does not mean it is correct for the other. One of the fundamental differences
is that there is no concept of &quot;project&quot; when running headless. PDE Build does
not even know about the Resources plug-in.</li>
<li>Buildfiles for features, plug-ins and fragments have to run independently
of Eclipse since we also support source builds. If possible they should
contain only the core Ant tasks. Any Eclipse relative task in a buildfile must
not be a requirement. Only add those in optional targets when extra value for
the user is needed (e.g. refresh local, JDT compiler, etc.).</li>
<li>Changing the buildfile is almost like an API change since there are
plug-ins using their own custom scripts (a good example is SWT). For example,
renaming a target called build.jars to build.all.jars is a breaking change
since SWT does not provide such target. Adding targets is also a breaking
change. Again, it has to be handled like an API change.</li>
<li>The Java runtime library can be defined by the user setting the
bootclasspath property (e.g. &lt;property name=&quot;bootclasspath&quot; value=&quot;c:\runtime\rt.jar&quot;/&gt;.
This is necessary, for example, when building an Eclipse Windows drop from a
Linux machine.</li>
<li>Compile paths in the buildfiles are represented as relative paths when
possible and full paths otherwise. In order for source builds to work, ALL
paths have to be relative since it has to be portable to any user that wants
to build Eclipse. In order to achieve it, the fetch task retrieve the projects
from CVS in a pre-defined structure. Many places in the pde build code will
rely on this structure so that changes to it should be considered very
carefully. The easiest way to understand the structure is to take a look at a
recent generated fetch script.</li>
<li>During the Eclipse Platform build the SWT plug-in and its fragments have
to be built before the platform feature since it is a very special plug-in.
All the JARs are placed in its platform specific fragments. For example, when
building Eclipse Platform for Win32, if we build the platform feature first
there will be no swt.jar since its JAR is built by the swt.win32 fragment and
it is not part of the base platform feature (it is part of the win32 platform
feature). So the eclipse.ui plug-in will not build since it depends on SWT and
the JAR is not there yet.</li>
<li>Plug-ins and fragments from one feature cannot depend on plug-ins from
another feature unless one feature depends on the other. For example, a
plug-in in the JDT feature can depend on a plug-in in the Platform feature but
not the other way around.</li>
</ul>
</body>
</html>

BIN
TBE/Eclipse/eclipse/plugins/org.eclipse.pde.build_3.0.1/pdebuild.jar Normal file
View File

Binary file not shown.

2
TBE/Eclipse/eclipse/plugins/org.eclipse.pde.build_3.0.1/plugin.properties Normal file
View File

@@ -0,0 +1,2 @@
pluginName = Plug-in Development Environment Build Support
providerName = Eclipse.org

89
TBE/Eclipse/eclipse/plugins/org.eclipse.pde.build_3.0.1/plugin.xml Normal file
View File

@@ -0,0 +1,89 @@
<?xml version="1.0" encoding="UTF-8"?>
<?eclipse version="3.0"?>
<plugin>
<!-- Tasks -->
<extension
point="org.eclipse.ant.core.antTasks">
<antTask
library="lib/pdebuild-ant.jar"
name="eclipse.fetch"
class="org.eclipse.pde.internal.build.tasks.FetchTask">
</antTask>
<antTask
library="lib/pdebuild-ant.jar"
name="eclipse.buildScript"
class="org.eclipse.pde.internal.build.tasks.BuildScriptGeneratorTask">
</antTask>
<antTask
library="lib/pdebuild-ant.jar"
name="eclipse.buildManifest"
class="org.eclipse.pde.internal.build.tasks.BuildManifestTask">
</antTask>
<antTask
library="lib/pdebuild-ant.jar"
name="eclipse.assembler"
class="org.eclipse.pde.internal.build.tasks.AssemblerTask">
</antTask>
<antTask
library="lib/pdebuild-ant.jar"
name="eclipse.idReplacer"
class="org.eclipse.pde.internal.build.tasks.IdReplaceTask">
</antTask>
<antTask
library="lib/pdebuild-ant.jar"
name="eclipse.unzipperBuilder"
class="org.eclipse.pde.internal.build.tasks.UnzipperGeneratorTask">
</antTask>
<antTask
library="lib/pdebuild-ant.jar"
name="eclipse.fetchFilesGenerator"
class="org.eclipse.pde.internal.build.tasks.FetchFileGeneratorTask">
</antTask>
<antTask
library="lib/pdebuild-ant.jar"
name="eclipse.versionReplacer"
class="org.eclipse.pde.internal.build.tasks.GenericVersionReplacer">
</antTask>
</extension>
<!-- Extra Classpath -->
<extension
point="org.eclipse.ant.core.extraClasspathEntries">
<extraClasspathEntry
library="lib/pdebuild-ant.jar">
</extraClasspathEntry>
</extension>
<extension
id="BuildScriptGenerator"
point="org.eclipse.core.runtime.applications">
<application>
<run
class="org.eclipse.pde.internal.build.BuildScriptGeneratorApplication">
</run>
</application>
</extension>
<extension
id="FetchScriptGenerator"
point="org.eclipse.core.runtime.applications">
<application>
<run
class="org.eclipse.pde.internal.build.FetchScriptGeneratorApplication">
</run>
</application>
</extension>
<extension
id="buildtimesite"
point="org.eclipse.update.core.siteTypes">
<site-factory
class="org.eclipse.pde.internal.build.site.BuildTimeSiteFactory">
</site-factory>
</extension>
<extension
id="BuildTimeFeatureFactory"
point="org.eclipse.update.core.featureTypes">
<feature-factory
class="org.eclipse.pde.internal.build.site.BuildTimeFeatureFactory">
</feature-factory>
</extension>
</plugin>

89
TBE/Eclipse/eclipse/plugins/org.eclipse.pde.build_3.0.1/scripts/build-template.properties Normal file
View File

@@ -0,0 +1,89 @@
###############################################################################
# Copyright (c) 2003, 2004 IBM Corporation and others.
# All rights reserved. This program and the accompanying materials
# are made available under the terms of the Common Public License v1.0
# which accompanies this distribution, and is available at
# http://www.eclipse.org/legal/cpl-v10.html
#
# Contributors:
# IBM Corporation - initial API and implementation
###############################################################################
#####################
# Parameters describing how and where to execute the build.
# Typical users need only update the following properties:
# baseLocation - where things you are building against are installed
# bootclasspath - The base jars to compile against (typicaly rt.jar)
# configs - the list of {os, ws, arch} configurations to build.
#
# Of course any of the settings here can be overridden by spec'ing
# them on the command line (e.g., -DbaseLocation=d:/eclipse
############# CVS CONTROL ################
# The CVS tag to use when fetching the map files from the repository
mapVersionTag=HEAD
# The CVS tag to use when fetching elements to build. By default the
# builder will use whatever is in the maps. Use this value to override
# for example, when doing a nightly build out of HEAD
# fetchTag=HEAD
############## BUILD / GENERATION CONTROL ################
# The directory into which the build elements will be fetched and where
# the build will take place.
buildDirectory=build
# Type of build. Used in naming the build output. Typically this value is
# one of I, N, M, S, ...
buildType=I
# ID of the build. Used in naming the build output.
buildId=TestBuild
# Label for the build. Used in naming the build output
buildLabel=${buildType}.${buildId}
# Timestamp for the build. Used in naming the build output
timestamp=007
# Base location for anything the build needs to compile against. For example,
# when building GEF, the baseLocation should be the location of a previously
# installed Eclipse against which the GEF code will be compiled.
baseLocation=
#Os/Ws/Arch/nl of the eclipse specified by baseLocation
#baseos
#basews
#basearch
#basenl
# The location underwhich all of the build output will be collected.
collectingFolder=eclipse
# The prefix that will be used in the generated archive.
archivePrefix=eclipse
# The list of {os, ws, arch} configurations to build. This
# value is a '&' separated list of ',' separate triples. For example,
# configs=win32,win32,x86 & linux,motif,x86
# By default the value is *,*,*
#configs=*,*,*
#Arguments to send to the zip executable
#zipArgs=
############# JAVA COMPILER OPTIONS ##############
# The location of the Java jars to compile against. Typically the rt.jar for your JDK/JRE
bootclasspath=d:/ibm1.3.1/jre/lib/rt.jar
# Whether or not to include debug info in the output jars
javacDebugInfo=false
# Whether or not to fail the build if there are compiler errors
javacfailonerror=true
# The version of the source code
#javaSource=1.3
# The version of the byte code targeted
#javacTarget=1.1

112
TBE/Eclipse/eclipse/plugins/org.eclipse.pde.build_3.0.1/scripts/build.xml Normal file
View File

@@ -0,0 +1,112 @@
<project name="Build All Elements" default="main">
<!-- ===================================================================== -->
<!-- Global properties. See the build.properties for information on -->
<!-- the properties which callers can control. -->
<!-- ===================================================================== -->
<property name="builderDirectory" location="${builder}"/>
<property name="buildProperties" location="${builder}/build.properties"/>
<property file="${buildProperties}"/>
<property name="customTargets" location="${builderDirectory}/customTargets.xml"/>
<property name="genericTargets" location="genericTargets.xml"/>
<!-- ===================================================================== -->
<!-- main entry point to setup, fetch, generate, build etc. Use -->
<!-- the customTargets.xml to modify the build behaviour. -->
<!-- ===================================================================== -->
<!-- ******* add in the descriptions for each of the top level targets to teh target decl -->
<target name="main" description="the main build target">
<antcall target="preBuild" />
<antcall target="fetch" />
<antcall target="generate" />
<antcall target="process" />
<antcall target="assemble" />
<antcall target="postBuild" />
</target>
<!-- ===================================================================== -->
<!-- Steps to do before starting the build. Typical setup includes -->
<!-- fetching the map files and building the directory. -->
<!-- ===================================================================== -->
<target name="preBuild">
<mkdir dir="${buildDirectory}" />
<ant antfile="${customTargets}" target="preSetup" />
<ant antfile="${customTargets}" target="getMapFiles" />
<concat destfile="${buildDirectory}/directory.txt" fixlastline="yes">
<fileset dir="${buildDirectory}" includes="maps/**/*.map"/>
</concat>
<ant antfile="${customTargets}" target="postSetup" />
</target>
<!-- ===================================================================== -->
<!-- Fetch the elements identified in the customTargets -->
<!-- ===================================================================== -->
<target name="fetch">
<ant antfile="${customTargets}" target="preFetch"/>
<!-- Generates and then execute the fetch scripts for each build element-->
<ant antfile="${customTargets}" target="allElements">
<property name="target" value="fetchElement" />
</ant>
<ant antfile="${customTargets}" target="postFetch"/>
</target>
<!-- ===================================================================== -->
<!-- Generate the build scripts for each element identified in the customTargets -->
<!-- ===================================================================== -->
<target name="generate">
<ant antfile="${customTargets}" target="preGenerate"/>
<!-- Generate the build.xml for each build element-->
<ant antfile="${customTargets}" target="allElements">
<property name="target" value="generateScript" />
</ant>
<ant antfile="${customTargets}" target="postGenerate"/>
</target>
<!-- ===================================================================== -->
<!-- Run the build scripts for each element identified in the customTargets -->
<!-- ===================================================================== -->
<target name="process">
<!-- Run custom tasks before processing, i.e. creating source build zip files -->
<ant antfile="${customTargets}" target="preProcess" />
<!-- Process all of the build elements-->
<ant antfile="${customTargets}" target="allElements">
<property name="target" value="processElement" />
</ant>
<!-- Run custom tasks after compiling, i.e. reporting compile errors -->
<ant antfile="${customTargets}" target="postProcess" />
</target>
<!-- ===================================================================== -->
<!-- Assemble the build elements into final distributions -->
<!-- ===================================================================== -->
<target name="assemble">
<ant antfile="${customTargets}" target="preAssemble"/>
<ant antfile="${customTargets}" target="allElements">
<property name="target" value="assembleElement"/>
</ant>
<ant antfile="${customTargets}" target="postAssemble"/>
</target>
<!-- ===================================================================== -->
<!-- Do any steps required after the build (e.g., posting, testing, ...) -->
<!-- ===================================================================== -->
<target name="postBuild">
<ant antfile="${customTargets}" target="postBuild" />
</target>
<!-- ===================================================================== -->
<!-- Clean the build elements. This target is here as an entry -->
<!-- point to the customTargets. It is not called directly in the normal -->
<!-- course of events. -->
<!-- ===================================================================== -->
<target name="clean">
<ant antfile="${customTargets}" target="allElements">
<property name="target" value="cleanElement"/>
</ant>
</target>
</project>

127
TBE/Eclipse/eclipse/plugins/org.eclipse.pde.build_3.0.1/scripts/customTargets-template.xml Normal file
View File

@@ -0,0 +1,127 @@
<project name="Build specific targets and properties" default="noDefault" >
<!-- ===================================================================== -->
<!-- Run a given ${target} on all elements being built -->
<!-- Add on <ant> task for each top level element being built. -->
<!-- ===================================================================== -->
<target name="allElements">
<ant antfile="${genericTargets}" target="${target}" >
<property name="type" value="<feature | plugin | fragment>" />
<property name="id" value="<element.id>" />
</ant>
</target>
<!-- ===================================================================== -->
<!-- Targets to assemble the built elements for particular configurations -->
<!-- These generally call the generated assemble scripts (named in -->
<!-- ${assembleScriptName}) but may also add pre and post processing -->
<!-- Add one target for each root element and each configuration -->
<!-- ===================================================================== -->
<target name="assemble.<element.id>[.config.spec]">
<ant antfile="${assembleScriptName}" dir="${buildDirectory}"/>
</target>
<!-- ===================================================================== -->
<!-- Check out map files from correct repository -->
<!-- Replace values for cvsRoot, package and mapVersionTag as desired. -->
<!-- ===================================================================== -->
<target name="getMapFiles">
<!-- Notify recipients that build has started.-->
<property name="cvsRoot" value="<cvs repo locator and login info>" />
<property name="mapVersionTag" value="HEAD" />
<cvs
package="<repo location of map files>"
dest="${buildDirectory}/maps"
tag="${mapVersionTag}"
/>
</target>
<!-- ===================================================================== -->
<!-- Steps to do before setup -->
<!-- ===================================================================== -->
<target name="preSetup">
</target>
<!-- ===================================================================== -->
<!-- Steps to do after setup but before starting the build proper -->
<!-- ===================================================================== -->
<target name="postSetup">
</target>
<!-- ===================================================================== -->
<!-- Steps to do before fetching the build elements -->
<!-- ===================================================================== -->
<target name="preFetch">
</target>
<!-- ===================================================================== -->
<!-- Steps to do after fetching the build elements -->
<!-- ===================================================================== -->
<target name="postFetch">
</target>
<!-- ===================================================================== -->
<!-- Steps to do before generating the build scripts. -->
<!-- ===================================================================== -->
<target name="preGenerate">
</target>
<!-- ===================================================================== -->
<!-- Steps to do after generating the build scripts. -->
<!-- ===================================================================== -->
<target name="postGenerate">
</target>
<!-- ===================================================================== -->
<!-- Steps to do before running the build.xmls for the elements being built. -->
<!-- ===================================================================== -->
<target name="preProcess">
</target>
<!-- ===================================================================== -->
<!-- Steps to do after running the build.xmls for the elements being built. -->
<!-- ===================================================================== -->
<target name="postProcess">
</target>
<!-- ===================================================================== -->
<!-- Steps to do before running assemble. -->
<!-- ===================================================================== -->
<target name="preAssemble">
</target>
<!-- ===================================================================== -->
<!-- Steps to do after running assemble. -->
<!-- ===================================================================== -->
<target name="postAssemble">
</target>
<!-- ===================================================================== -->
<!-- Steps to do after the build is done. -->
<!-- ===================================================================== -->
<target name="postBuild">
</target>
<!-- ===================================================================== -->
<!-- Steps to do to test the build results -->
<!-- ===================================================================== -->
<target name="test">
</target>
<!-- ===================================================================== -->
<!-- Steps to do to publish the build results -->
<!-- ===================================================================== -->
<target name="publish">
</target>
<!-- ===================================================================== -->
<!-- Default target -->
<!-- ===================================================================== -->
<target name="noDefault">
<echo message="You must specify a target when invoking this file" />
</target>
</project>

145
TBE/Eclipse/eclipse/plugins/org.eclipse.pde.build_3.0.1/scripts/genericTargets.xml Normal file
View File

@@ -0,0 +1,145 @@
<project name="Generic Build Targets" default="noDefault">
<!-- Properties that must be passed to this script:
buildDirectory
id
type
ignoreTagInfo
recursiveGeneration
workingDirectory
configInfo
-->
<!-- ===================================================================== -->
<!-- Setup default values -->
<!-- configs : by default build a platform-independent configuration -->
<!-- fetchTag : by default use the CVS tags as spec'd in directory.txt -->
<!-- ===================================================================== -->
<property name="configs" value="*,*,*"/>
<property name="fetchTag" value=""/>
<property name="buildingOSGi" value="true"/>
<!-- ===================================================================== -->
<!-- Fetch a single element (feature, plugin, fragment) -->
<!-- ===================================================================== -->
<target name="fetchElement" description="Checking out source from repository..." depends="init">
<mkdir dir="${buildDirectory}/features"/>
<mkdir dir="${buildDirectory}/plugins"/>
<eclipse.fetch
elements="${type}@${id}"
buildDirectory="${buildDirectory}"
directory="${buildDirectory}/directory.txt"
fetchTag="${fetchTag}"
configInfo="${configs}"
/>
<!-- Run generated fetch script -->
<ant antfile="${buildDirectory}/fetch_${id}.xml">
<!-- ************ should not have to spec these *************** -->
<property name="featureOnly" value="true"/>
<property name="featureAndPlugins" value="true"/>
<property name="featuresRecursively" value="true"/>
</ant>
</target>
<!-- ===================================================================== -->
<!-- Clean previously built elements -->
<!-- ===================================================================== -->
<target name="cleanElement" description="Scrubbing features and plugins of old jars..." depends="init">
<echo message="${elementPath}"/>
<ant antfile="build.xml" dir="${elementPath}" target="clean"/>
</target>
<!-- ===================================================================== -->
<!-- Generate a build.xml file for an element -->
<!-- ===================================================================== -->
<target name="generateScript" description="Generating build scripts..." depends="init">
<eclipse.buildScript
elements="${type}@${id}"
buildDirectory="${buildDirectory}"
configInfo="${configs}"
baseLocation="${baseLocation}"
buildingOSGi="${buildingOSGi}"
/>
</target>
<!-- ===================================================================== -->
<!-- Run build.xml for a single element-->
<!-- ===================================================================== -->
<target name="processElement" description="Processing build scripts..." depends="init">
<ant antfile="build.xml" dir="${elementPath}" target="build.jars">
<property name="target" value="build.jars"/>
</ant>
</target>
<!-- **********************
1) the gather targets do more than just gather. These are packaging targets.
We need to continue ot separate the two concepts (gather and package) as
the packaging is different if we wanted to create an update site packaging
(for example). The gathers are commented out for now as the new generated
scripts do not seem to have them.
2) do we really need the ws and os properties? In all cases? Do they have to be
set here?
-->
<!-- ===================================================================== -->
<!-- Gather items listed in bin.includes -->
<!-- ===================================================================== -->
<target name="gatherBinaries" description="Gathering binary distribution..." depends="init">
<!-- ant antfile="build.xml" dir="${elementPath}" target="gather.bin.parts"/ -->
<ant antfile="build.xml" dir="${elementPath}" target="zip.distribution">
<property name="os" value="${os}" />
<property name="ws" value="${ws}" />
</ant>
</target>
<!-- ===================================================================== -->
<!-- Gather source for a build element -->
<!-- ===================================================================== -->
<target name="gatherSources" description="Gathering source distribution..." depends="init">
<!--suspect: this call is required to create the *.src.zip inside each plugin-->
<ant antfile="build.xml" dir="${elementPath}" target="build.sources">
<property name="os" value="${os}" />
<property name="ws" value="${ws}" />
</ant>
<ant antfile="build.xml" dir="${elementPath}" target="zip.sources">
<property name="os" value="${os}" />
<property name="ws" value="${ws}" />
</ant>
</target>
<!-- ===================================================================== -->
<!-- Gather log files for an element -->
<!-- Suspect: We just unzip these right away -->
<!-- ===================================================================== -->
<target name="gatherLogs" description="Gathering build logs..." depends="init">
<ant antfile="build.xml" dir="${elementPath}" target="zip.logs" >
<property name="buildDirectory" value="${buildDirectory}" />
</ant>
</target>
<!-- ===================================================================== -->
<!-- Default target -->
<!-- ===================================================================== -->
<target name="noDefault">
<echo message="This file must be called with explicit targets" />
</target>
<!-- ===================================================================== -->
<!-- Assemble one build element -->
<!-- ===================================================================== -->
<target name="assembleElement" description="Assembling the build..." depends="init">
<ant antfile="assemble.${id}.all.xml" dir="${buildDirectory}"/>
</target>
<!-- ===================================================================== -->
<!-- Miscellaneous helper targets -->
<!-- ===================================================================== -->
<target name="init">
<condition property="elementPath" value="${buildDirectory}/plugins/${id}">
<equals arg1="${type}" arg2="fragment" />
</condition>
<property name="elementPath" value="${buildDirectory}/${type}s/${id}" />
</target>
</project>

62
TBE/Eclipse/eclipse/plugins/org.eclipse.pde.build_3.0.1/scripts/package.xml Normal file
View File

@@ -0,0 +1,62 @@
<project name="packager" default="main" basedir=".">
<target name="init">
<mkdir dir="${workingDirectory}"/>
<mkdir dir="${downloadDirectory}"/>
<mkdir dir="${tempDirectory}"/>
</target>
<target name="retrieveMapFiles">
<available property="mapsFetched" file="${workingDirectory}/all.maps"/>
<ant antfile="${customTargets}" target="getMapFiles" />
<concat destfile="${workingDirectory}/all.maps">
<fileset dir="${downloadDirectory}" includes="**/*.map"/>
</concat>
</target>
<!-- take the content of all.maps, retrieve the files according to the filtering options (config, content),
and generate a directory.txt for the rest of the process using config as a key, and containing the name of the zip and the directory -->
<target name="retrieveFiles">
<eclipse.fetchFilesGenerator map="${workingDirectory}/all.maps"
workingDirectory="${workingDirectory}"
configInfo="${config}"
contentFilter="${contentFilter}"
componentFilter="${componentFilter}"/>
<ant antfile="fetch.xml" dir="${workingDirectory}" />
</target>
<!-- Process the directory.txt to create unzipper.xml, and run unzipper.xml-->
<target name="prepareResources">
<eclipse.unzipperBuilder workingDirectory="${workingDirectory}"
configInfo="${config}"
packagePropertyFile="${packagingPropertyFile}"/>
<ant antfile="${workingDirectory}/unzipper.xml"/>
</target>
<!-- Generate an assemble script (assemble.xml) for the given features -->
<target name="generateAssembleScripts">
<eclipse.assembler featureList="${featureList}"
workingDirectory="${workingDirectory}"
configInfo="${config}"
baseLocation="${tempDirectory}/${featurePaths}"
packagePropertyFile="${packagingPropertyFile}" />
</target>
<!-- Call the assemble.xml script -->
<target name="callAssembleScripts">
<ant antfile="assemble.xml" dir="${workingDirectory}"/>
</target>
<target name="main" description="Start the packager for a given config">
<property file="${packagingInfo}/packager.properties"/>
<property name="customTargets" location="${packagingInfo}/customTargets.xml"/>
<property name="packagingPropertyFile" location="${packagingInfo}/${packagingProperties}"/>
<antcall target="init"/>
<antcall target="retrieveMapFiles"/>
<antcall target="retrieveFiles"/>
<antcall target="prepareResources"/>
<antcall target="generateAssembleScripts"/>
<antcall target="callAssembleScripts"/>
</target>
</project>

18
TBE/Eclipse/eclipse/plugins/org.eclipse.pde.build_3.0.1/templates/fragment/fragment.xml Normal file
View File

@@ -0,0 +1,18 @@
<?xml version="1.0" encoding="UTF-8"?>
<?eclipse version="3.0"?>
<fragment
id="FRAGMENT_ID"
name="%pluginName"
version="FRAGMENT_VERSION"
provider-name="Eclipse.org"
plugin-id="PLUGIN_ID"
plugin-version="PLUGIN_VERSION">
<runtime>
</runtime>
<extension point = "org.eclipse.pde.core.source">
<location path="src" />
</extension>
</fragment>

13
TBE/Eclipse/eclipse/plugins/org.eclipse.pde.build_3.0.1/templates/plugin/plugin.xml Normal file
View File

@@ -0,0 +1,13 @@
<?xml version="1.0" encoding="UTF-8"?>
<?eclipse version="3.0"?>
<plugin
name="%pluginName"
id="PLUGIN_ID"
version="PLUGIN_VERSION"
provider-name="%providerName">
<extension point = "org.eclipse.pde.core.source">
<location path="src" />
</extension>
</plugin>