aboutsummaryrefslogtreecommitdiffstats
path: root/openecomp-be/lib/openecomp-tosca-converter-lib/openecomp-tosca-converter-core/pom.xml
blob: 15e5ea84d81ce540da98c9ba5098a0bd21b1f24f (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
  <modelVersion>4.0.0</modelVersion>
  <dependencies>
    <dependency>
      <groupId>org.openecomp.sdc</groupId>
      <artifactId>openecomp-tosca-converter-api</artifactId>
      <version>${project.version}</version>
    </dependency>
    <dependency>
      <groupId>org.openecomp.sdc</groupId>
      <artifactId>openecomp-sdc-translator-core</artifactId>
      <version>${project.version}</version>
    </dependency>
    <dependency>
      <groupId>org.openecomp.sdc.be</groupId>
      <artifactId>common-be-tests-utils</artifactId>
      <version>${project.version}</version>
      <scope>test</scope>
      <exclusions>
        <exclusion>
          <groupId>org.springframework</groupId>
          <artifactId>spring-core</artifactId>
        </exclusion>
        <exclusion>
          <groupId>org.eclipse.jetty</groupId>
          <artifactId>jetty-server</artifactId>
        </exclusion>
        <exclusion>
          <groupId>org.eclipse.jetty</groupId>
          <artifactId>jetty-servlet</artifactId>
        </exclusion>
      </exclusions>
    </dependency>
    <dependency>
      <groupId>org.hamcrest</groupId>
      <artifactId>hamcrest</artifactId>
      <version>${hamcrest.version}</version>
      <scope>test</scope>
    </dependency>
    <dependency>
      <groupId>org.hamcrest</groupId>
      <artifactId>hamcrest-library</artifactId>
      <version>${hamcrest.version}</version>
      <scope>test</scope>
    </dependency>
    <dependency>
      <groupId>javax.validation</groupId>
      <artifactId>validation-api</artifactId>
      <version>${javax.validation.version}</version>
    </dependency>
  </dependencies>

  <parent>
    <groupId>org.openecomp.sdc</groupId>
    <artifactId>openecomp-tosca-converter-lib</artifactId>
    <version>1.13.4-SNAPSHOT</version>
  </parent>

  <artifactId>openecomp-tosca-converter-core</artifactId>
  <build>
    <testResources>
      <testResource>
        <directory>src/test/resources</directory>
        <excludes>
        <exclude>**/*.csar</exclude>
        </excludes>
		<filtering>true</filtering>
      </testResource>
      <testResource>
        <directory>src/test/resources/csar</directory>
        <includes>
          <include>**.csar</include>
        </includes>
        <filtering>false</filtering>
        <targetPath>csar</targetPath>
      </testResource>
    </testResources>
  </build>
</project>
yer, access control, resiliency, and software lifecycle management. Project Specific Release Notes ++++++++++++++++++++++++++++++ ONAP releases are specified by a list of project artifact versions in a :ref:`manifest<doc-release-manifest>`. Each project provides detailed :ref:`release notes<doc-releaserepos>` and prepends to these if/when any updated versions the project team believes are compatible with a major release are made available. Platforms Requirements ++++++++++++++++++++++ ONAP Beijing Release has been tested on Linux OSs. Details are :ref:`available here <demo-installing-running-onap-requirements>`. .. index:: Download Download & Install ++++++++++++++++++ There are 3 approaches to install ONAP: * Full ONAP installation using Heat template * Advanced installation to install individual components * Experimental installation using Kubernetes Full ONAP installation using Heat template ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From a complete demo solution perspective. This installs the whole ONAP, refer to :ref:`Setting Up ONAP <demo-installing-running-onap>`. Advanced installation to install individual components ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From a developer perspective, ONAP can be installed component per component. For details, refer to :ref:`the installation procedure available for each component<index-setting-individual-components>`. The advanced installation procedure is recommended only for experienced developers who desire to focus their attention on a few components and who have a deep understanding of dependencies between components. This type of installation is not recommended to fully install ONAP. * The list of ports used by default within ONAP is documented in `ONAP Service List <https://wiki.onap.org/display/DW/ONAP+Services+List>`_. * The ONAP Source Code is available through Gerrit at https://gerrit.onap.org or Git at https://git.onap.org/. * ONAP is packaged within Docker and can be dowloaded from Docker Hub at https://hub.docker.com/r/onap. Experimental installation using Kubernetes ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From a complete demo solution perspective using Kubernetes. This installs the whole ONAP, refer to :ref:`ONAP Operations Manager - Quick Start Guide <onap-operations-manager-project>`. Documentation +++++++++++++ ONAP Beijing Release documentation is available :ref:`here <master_index>`. For Beijing this includes: * A high level :ref:`architecture view<doc-architecture>` of how components relate to each other. * A collection of documentation provided by :ref:`each project <doc_onap-developer_guide_projects>`. * Application Programming Interface Reference :ref:`available here <doc-apiref>`. * The `developer wiki <http://wiki.onap.org>`_ remains a good source of information on meeting plans and notes from committees, project teams and community events. Usage +++++ This section is intended to provide users on the usage of ONAP components. Instructions on using the ONAP deployment including Robot, Portal, SDC and VID in the context of running (Onboarding, service creation, service deployment, VNF creation, VNF preload, VF Module creation and closed loop operations) the vFirewall sanity use case is documented in `Running the ONAP Demos <https://wiki.onap.org/display/DW/Running+the+ONAP+Demos>`_. .. index:: Licensing Licenses ++++++++ ONAP Source Code is licensed under the `Apache Version 2 License <http://www.apache.org/licenses/LICENSE-2.0>`_. ONAP Documentation is licensed under the `Creative Commons Attribution 4.0 International License <http://creativecommons.org/licenses/by/4.0>`_. Known Issues and Limitations ++++++++++++++++++++++++++++ Known Issues and limitations are documented in each :ref:`project Release Notes <doc-releaserepos>`. .. index:: Reporting Bugs How to Report a Bug +++++++++++++++++++ There are 2 ways to report a bug in ONAP. * In case you are familiar within ONAP, you can directly report a bug by creating a Jira issue at `ONAP Jira <https://jira.onap.org>`_. * If you don't know you are facing a bug or have a question, post your question into the `Ask question <https://wiki.onap.org/display/DW/questions/all>`_. You will need a Linux Foundation ID to login and post your question. Get a Linux Foundation Identity using this `quick procedure <https://wiki.onap.org/display/DW/Joining+the+Community>`_. You may consider these `recommendations <https://wiki.onap.org/display/DW/Tracking+Issues+with+JIRA#TrackingIssueswithJIRA-RecommendationsforwrittingProperJIRAIssue>`_ to elaborate the issue you are facing. .. Include files referenced by link in the toctree as hidden .. toctree:: :hidden: release-manifest.rst releaserepos.rst repolist.rst