+ initial commit with extracted components

bin/

*._trace

*.xtendbin

.DS_Store

target/

 No newline at end of file

# This file is a template, and might need editing before it works on your project.

# This is a sample GitLab CI/CD configuration file that should run without any modifications.

# It demonstrates a basic 3 stage CI/CD pipeline. Instead of real tests or scripts,

# it uses echo commands to simulate the pipeline execution.

#

# A pipeline is composed of independent jobs that run scripts, grouped into stages.

# Stages run in sequential order, but jobs within stages run in parallel.

#

# For more information, see: https://docs.gitlab.com/ee/ci/yaml/index.html#stages

#

# You can copy and paste this template into a new `.gitlab-ci.yml` file.

# You should not add this template to an existing `.gitlab-ci.yml` file by using the `include:` keyword.

#

# To contribute improvements to CI/CD templates, please follow the Development guide at:

# https://docs.gitlab.com/ee/development/cicd/templates.html

# This specific template is located at:

# https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Getting-Started.gitlab-ci.yml

# Build JAVA applications using Apache Maven (http://maven.apache.org)

# For docker image tags see https://hub.docker.com/_/maven/

#

# For general lifecycle information see https://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html

# This template will build and test your projects

# * Caches downloaded dependencies and plugins between invocation.

# * Verify but don't deploy merge requests.

# * Deploy built artifacts from master branch only.

variables:

  # CI_TARGET_BRANCH: $CI_DEFAULT_BRANCH

  # CI_TARGET_BRANCH: "ttf-022"

  TTF_CI_TARGET_BRANCH: "ttf-034"  

  DEV_CI_TARGET_BRANCH: "dev"

  MAIN_CI_TARGET_BRANCH: "master"

  CI_TARGET_BRANCH: "${TTF_CI_TARGET_BRANCH}"

  SITE_LOCATION: "updatesite/org.etsi.mts.tdl.extras.updatesite/target"

  ARCHIVE_NAME: "org.etsi.mts.tdl.extras.updatesite-1.0.0-SNAPSHOT.zip"

  SITE_ARCHIVE: "${SITE_LOCATION}/${ARCHIVE_NAME}"

  SITE_PATH: "${SITE_LOCATION}/repository/"

  REPO_PREFIX: "https://labs.etsi.org/rep/top/extras/-/jobs"

  REPO_PATH: "artifacts/raw/updatesite/org.etsi.mts.tdl.extras.updatesite/target/repository/"

  PACKAGE_NAME: "TOP Extras Interim Build"

  PACKAGE_NAME_MAIN: "TOP Extras Build"

  BETA_KEY: "beta"

  MAIN_KEY: "stable"

  RELEASE_KEY: "beta"

  RELEASE_PATH: "public/updatesite/${RELEASE_KEY}"

  RELEASE_PAGE: "https://top.etsi.org/extras/updatesite/${RELEASE_KEY}"

  STANDALONE_LOCATION: "plugins/org.etsi.mts.tdl.standalone/target"

  STANDALONE_NAME: "org.etsi.mts.tdl.standalone-1.0.0-SNAPSHOT-shadow.jar"

  STANDALONE_PATH: "${STANDALONE_LOCATION}/${STANDALONE_NAME}"

  # `showDateTime` will show the passed time in milliseconds. You need to specify `--batch-mode` to make this work.

  MAVEN_OPTS: >-

    -Xmx2048m

    -Dhttps.protocols=TLSv1.2

    -Dmaven.repo.local=$CI_PROJECT_DIR/.m2/repository

    -Dorg.slf4j.simpleLogger.showDateTime=true

    -Djava.awt.headless=true

  # As of Maven 3.3.0 instead of this you MAY define these options in `.mvn/maven.config` so the same config is used

  # when running from the command line.

  # As of Maven 3.6.1, the use of `--no-tranfer-progress` (or `-ntp`) suppresses download and upload messages. The use

  # of the `Slf4jMavenTransferListener` is no longer necessary.

  # `installAtEnd` and `deployAtEnd` are only effective with recent version of the corresponding plugins.

  MAVEN_CLI_OPTS: >-

    --batch-mode

    --errors

    --fail-at-end

    --show-version

    --no-transfer-progress

    -DinstallAtEnd=true

    -DdeployAtEnd=true

.default_rules:

  rules:

    - if: $CI_PIPELINE_SOURCE == "schedule"

      when: never

    - if: $CI_COMMIT_BRANCH == $CI_TARGET_BRANCH

    - if: $CI_COMMIT_BRANCH == $DEV_CI_TARGET_BRANCH

    - if: $CI_PIPELINE_SOURCE == "web"

      when: always

    - if: $CI_COMMIT_TAG

      when: never

    # - when: never

# This template uses the latest Maven 3 release, e.g., 3.8.6, and OpenJDK 8 (LTS)

# for verifying and deploying images

# Maven 3.8.x REQUIRES HTTPS repositories.

# See https://maven.apache.org/docs/3.8.1/release-notes.html#how-to-fix-when-i-get-a-http-repository-blocked for more.

image: maven:3-openjdk-11

# Cache downloaded dependencies and plugins between builds.

# To keep cache across branches add 'key: "$CI_JOB_NAME"'

# Be aware that `mvn deploy` will install the built jar into this repository. If you notice your cache size

# increasing, consider adding `-Dmaven.install.skip=true` to `MAVEN_OPTS` or in `.mvn/maven.config`

cache:

  paths:

    - .m2/repository

# For merge requests do not `deploy` but only run `verify`.

# See https://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html

# .verify:

  # stage: test

  # script:

    # - cd org.etsi.mts.tdl.parent

    # - 'mvn $MAVEN_CLI_OPTS verify'

  # except:

    # variables:

      # - $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH

# Verify merge requests using JDK8

# verify:jdk11:

  # extends:

    # - .verify

# To deploy packages from CI, create a `ci_settings.xml` file

# For deploying packages to GitLab's Maven Repository: See https://docs.gitlab.com/ee/user/packages/maven_repository/index.html#create-maven-packages-with-gitlab-cicd for more details.

# Please note: The GitLab Maven Repository is currently only available in GitLab Premium / Ultimate.

# For `master` or `main` branch run `mvn deploy` automatically.

#deploy:jdk11:

#  stage: deploy

#  script:

#    - if [ ! -f ci_settings.xml ]; then

#        echo "CI settings missing\! If deploying to GitLab Maven Repository, please see https://docs.gitlab.com/ee/user/packages/maven_repository/index.html#create-maven-packages-with-gitlab-cicd for instructions.";

#      fi

#    - 'mvn $MAVEN_CLI_OPTS deploy --settings ci_settings.xml'

#  only:

#    variables:

#      - $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH

stages:          # List of stages for jobs, and their order of execution

  - build

  - test

  - deploy

  - prepare

  - upload

  - release

build-job:       # This job runs in the build stage, which runs first.

  stage: build

  rules:

    - !reference [.default_rules, rules]

  script:

    # Test zip installation

    # - rm -rf /var/lib/apt/lists/*

    # - apt update

    # - apt-cache gencaches

    # - apt install -y zip unzip

    # - zip --help

    - echo "Compiling the code..."

    - echo "BUILD_JOB_ID=$CI_JOB_ID" >> build.env

    - cat build.env

    - cd org.etsi.mts.tdl.extras.parent

    - mvn clean install

    - echo "Compile complete."

  artifacts:

    expire_in: 7 days

    reports:

      dotenv: build.env

    paths:

      - $SITE_ARCHIVE

      - $SITE_PATH

      # - $STANDALONE_PATH 

# Adapted from OpenAPI2TDL converter

prepare-job:

  stage: prepare

  rules:

    - !reference [.default_rules, rules]

  script:

    - VERSION=`date +%Y%m%d.%H.%M`

    - | # Prepare a stable build (only web build?)

      if [ $CI_COMMIT_BRANCH == $MAIN_CI_TARGET_BRANCH ]

      then 

        export RELEASE_KEY=$MAIN_KEY 

        echo "RELEASE_KEY=$RELEASE_KEY" >> variables.env

        echo "PACKAGE_NAME=$PACKAGE_NAME_MAIN" >> variables.env

        echo "RELEASE_PATH=public/updatesite/${RELEASE_KEY}" >> variables.env

        echo "RELEASE_PAGE=https://top.etsi.org/extras/updatesite/${RELEASE_KEY}" >> variables.env

      fi

    - echo "EXTRA_DESCRIPTION=automatic-release" >> variables.env

    - echo "VERSION=$VERSION" >> variables.env

    - echo "PACKAGE_REGISTRY_URL=${CI_API_V4_URL}/projects/${CI_PROJECT_ID}/packages/generic/extras/${VERSION}" >> variables.env

    - echo "PACKAGE_LATEST_URL=${CI_API_V4_URL}/projects/${CI_PROJECT_ID}/packages/generic/extras/latest" >> variables.env

    - cat variables.env

  artifacts:

    reports:

      dotenv: variables.env   # Use artifacts:reports:dotenv to expose the variables to other jobs

# https://gitlab.com/gitlab-org/release-cli/-/tree/master/docs/examples/release-assets-as-generic-package/

upload-job:

  stage: upload

  image: curlimages/curl:latest

  needs:

    - job: prepare-job

      artifacts: true

    - job: build-job

      artifacts: true

  rules:

    - !reference [.default_rules, rules]

  script:

    - echo $BUILD_JOB_ID    

    - echo "${PACKAGE_REGISTRY_URL}/${ARCHIVE_NAME}"

    - |

      curl --header "JOB-TOKEN: ${CI_JOB_TOKEN}" --upload-file ${SITE_ARCHIVE} ${PACKAGE_REGISTRY_URL}/${ARCHIVE_NAME}

    # - |

      # curl --header "JOB-TOKEN: ${CI_JOB_TOKEN}" --upload-file ${STANDALONE_LOCATION} ${PACKAGE_REGISTRY_URL}/${STANDALONE_NAME}

    # - |

      # curl --header "JOB-TOKEN: ${CI_JOB_TOKEN}" --upload-file ${SITE_ARCHIVE} ${PACKAGE_LATEST_URL}/${ARCHIVE_NAME}

    # - |

      # cd ${SITE_LOCATION} && find repository/ -type f -exec echo curl --header "JOB-TOKEN: ${CI_JOB_TOKEN}" --upload-file {} ${PACKAGE_LATEST_URL}/{} \; && cd ~

    # - |

      # cd ${SITE_LOCATION} && find repository/ -type f -exec curl --header "JOB-TOKEN: ${CI_JOB_TOKEN}" --upload-file {} ${PACKAGE_LATEST_URL}/{} \; 

    # - |

      # curl --header "JOB-TOKEN: ${CI_JOB_TOKEN}" --upload-file bin/${MACOS_GUI_JAR} ${PACKAGE_REGISTRY_URL}/${MACOS_GUI_JAR}

    # - |

      # curl --header "JOB-TOKEN: ${CI_JOB_TOKEN}" --upload-file bin/${WINDOWS_GUI_JAR} ${PACKAGE_REGISTRY_URL}/${WINDOWS_GUI_JAR}

    # - |

      # curl --header "JOB-TOKEN: ${CI_JOB_TOKEN}" --upload-file bin/${CLI_JAR} ${PACKAGE_REGISTRY_URL}/${CLI_JAR}

    # - |

      # curl --header "JOB-TOKEN: ${CI_JOB_TOKEN}" --upload-file bin/${LIB_JAR} ${PACKAGE_REGISTRY_URL}/${LIB_JAR}

pages:

  stage: upload

  # image: curlimages/curl:latest

  # image: alpine

  needs:

    - job: prepare-job

      artifacts: true

    - job: build-job

      artifacts: true

  script:

    # Get the previous GitLab Pages content (otherwise other beta/stable branch gets removed..)

    # - rm -rf /var/lib/apt/lists/*

    # - apt update

    # - apt-cache gencaches

    # - apt install -y zip unzip

    # - zip --help

    # - set +e

    # - curl --fail "$CI_PAGES_URL/content.zip" -o "content.zip"

    # - if [ -e "content.zip" ]; then unzip "content.zip"; rm "content.zip"; fi

    # - set -e

    # - ls -la $RELEASE_PATH

    # Cleanup content? -> remove content in release path?

    # Add/update content

    - echo $CI_PAGES_URL

    - echo $RELEASE_PATH

    - mkdir -p $RELEASE_PATH

    # - rm -rf $RELEASE_PATH/*

    - cp -r -f $SITE_PATH/* $RELEASE_PATH

    - ls -la $RELEASE_PATH

    # Zip the content and publish the zip again

    # - zip -r "content.zip" "public"

    # - mv "content.zip" "public/"

    # - mv $SITE_ARCHIVE $RELEASE_PATH/content.zip

  artifacts:

    paths:

      - public

  rules:

    - !reference [.default_rules, rules]

  # only:

    # - tags  

release-job:

  stage: release

  image: registry.gitlab.com/gitlab-org/release-cli:latest

  needs:

    - job: prepare-job

      artifacts: true

    - job: build-job

      artifacts: true

    - job: pages

      artifacts: true

  rules:

    - !reference [.default_rules, rules]

  script:

    # --description "Published automatically, permalink for installation (valid for 7 days) at https://labs.etsi.org/rep/top/ide/-/releases/permalink/latest/downloads/repository." 

    - echo $BUILD_JOB_ID    

    - |

      release-cli create --name "Release $VERSION" \

        --tag-name $VERSION \

        --ref $CI_COMMIT_SHA \

        --assets-link "{\"name\":\"${PACKAGE_NAME} (downloadable archive)\",\"url\":\"${PACKAGE_REGISTRY_URL}/${ARCHIVE_NAME}\",\"filepath\":\"/repository-archive\"}" \

        --assets-link "{\"name\":\"${PACKAGE_NAME} (snapshot ${RELEASE_KEY} repository for ${VERSION} (exipres in 7 days))\",\"url\":\"${REPO_PREFIX}/${BUILD_JOB_ID}/${REPO_PATH}\"}" \

        --assets-link "{\"name\":\"${PACKAGE_NAME} (latest ${RELEASE_KEY} release repository (permalink))\",\"url\":\"${RELEASE_PAGE}\"}" \

        # --assets-link "{\"name\":\"${PACKAGE_NAME} (latest standalone (exipres in 7 days))\",\"url\":\"${PACKAGE_REGISTRY_URL}/${STANDALONE_NAME}\"}" \

        # --assets-link "{\"name\":\"${PACKAGE_NAME} (latest)\",\"url\":\"${PACKAGE_LATEST_URL}/${ARCHIVE_NAME}\"}" \

        # --assets-link "{\"name\":\"${MACOS_GUI_JAR}\",\"url\":\"${PACKAGE_REGISTRY_URL}/${MACOS_GUI_JAR}\"}" \

        # --assets-link "{\"name\":\"${WINDOWS_GUI_JAR}\",\"url\":\"${PACKAGE_REGISTRY_URL}/${WINDOWS_GUI_JAR}\"}" \

        # --assets-link "{\"name\":\"${CLI_JAR}\",\"url\":\"${PACKAGE_REGISTRY_URL}/${CLI_JAR}\"}" \

        # --assets-link "{\"name\":\"${LIB_JAR}\",\"url\":\"${PACKAGE_REGISTRY_URL}/${LIB_JAR}\"}"

Eclipse Public License - v 1.0

THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS ECLIPSE PUBLIC

LICENSE ("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION OF THE PROGRAM

CONSTITUTES RECIPIENT'S ACCEPTANCE OF THIS AGREEMENT.

1. DEFINITIONS

"Contribution" means:

a) in the case of the initial Contributor, the initial code and documentation

   distributed under this Agreement, and

b) in the case of each subsequent Contributor:

    i) changes to the Program, and

   ii) additions to the Program;

   where such changes and/or additions to the Program originate from and are

   distributed by that particular Contributor. 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. 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.

"Contributor" means any person or entity that distributes the Program.

"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.

"Program" means the Contributions distributed in accordance with this

Agreement.

"Recipient" means anyone who receives the Program under this Agreement,

including all Contributors.

2. GRANT OF RIGHTS

  a) Subject to the terms of this Agreement, each Contributor hereby grants

     Recipient a non-exclusive, worldwide, royalty-free copyright license to

     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.

  b) Subject to the terms of this Agreement, each Contributor hereby grants

     Recipient a non-exclusive, worldwide, 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.

  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.

  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.

3. REQUIREMENTS

A Contributor may choose to distribute the Program in object code form under

its own license agreement, provided that:

  a) it complies with the terms and conditions of this Agreement; and

  b) its license agreement:

      i) effectively disclaims 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;

     ii) effectively excludes on behalf of all Contributors all liability for

         damages, including direct, indirect, special, incidental and

         consequential damages, such as lost profits;

    iii) states that any provisions which differ from this Agreement are

         offered by that Contributor alone and not by any other party; and

     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.

When the Program is made available in source code form:

  a) it must be made available under this Agreement; and

  b) a copy of this Agreement must be included with each copy of the Program.

     Contributors may not remove or alter any copyright notices contained

     within the Program.

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.

4. COMMERCIAL DISTRIBUTION

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.

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.

5. NO WARRANTY

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 solely responsible for determining the appropriateness of using

and distributing the Program and assumes all risks associated with its

exercise of rights under this Agreement , including but not limited to the

risks and costs of program errors, compliance with applicable laws, damage to

or loss of data, programs or equipment, and unavailability or interruption of

operations.

6. DISCLAIMER OF LIABILITY

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 (INCLUDING WITHOUT LIMITATION

LOST PROFITS), 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.

7. GENERAL

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.

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.

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.

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

publish new versions (including revisions) of this Agreement from time to

time. No one other than the Agreement Steward has the right to modify this

Agreement. The Eclipse Foundation is the initial Agreement Steward. The

Eclipse Foundation may assign the responsibility to serve as the Agreement

Steward to a suitable separate entity. 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 version. 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, by implication, estoppel or otherwise. All rights in the

Program not expressly granted under this Agreement are reserved.

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.

 No newline at end of file

<?xml version="1.0" encoding="UTF-8"?>

<projectDescription>

	<name>org.etsi.mts.tdl.extras.feature</name>

	<comment></comment>

	<projects>

	</projects>

	<buildSpec>

		<buildCommand>

			<name>org.eclipse.pde.FeatureBuilder</name>

			<arguments>

			</arguments>

		</buildCommand>

		<buildCommand>

			<name>org.eclipse.m2e.core.maven2Builder</name>

			<arguments>

			</arguments>

		</buildCommand>

	</buildSpec>

	<natures>

		<nature>org.eclipse.m2e.core.maven2Nature</nature>

		<nature>org.eclipse.pde.FeatureNature</nature>

	</natures>

</projectDescription>