Commit 034b1ce5 authored by Yuri Blankenstein's avatar Yuri Blankenstein
Browse files

Merge branch 'develop' into 'master'

v0.1

See merge request !20
parents 24306e9b 68076929
Pipeline #5170 passed with stage
in 0 seconds
////
// Copyright (c) 2021 Contributors to the Eclipse Foundation
//
// This program and the accompanying materials are made
// available under the terms of the Eclipse Public License 2.0
// which is available at https://www.eclipse.org/legal/epl-2.0/
//
// SPDX-License-Identifier: EPL-2.0
////
# Community Code of Conduct
**Version 1.2** +
**August 19, 2020**
## Our Pledge
In the interest of fostering an open and welcoming environment, we as community members, contributors, committers, and project leaders pledge to make participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
## Our Standards
Examples of behavior that contributes to creating a positive environment include:
* Using welcoming and inclusive language
* Being respectful of differing viewpoints and experiences
* Gracefully accepting constructive criticism
* Focusing on what is best for the community
* Showing empathy towards other community members
Examples of unacceptable behavior by participants include:
* The use of sexualized language or imagery and unwelcome sexual attention or advances
* Trolling, insulting/derogatory comments, and personal or political attacks
* Public or private harassment
* Publishing others' private information, such as a physical or electronic address, without explicit permission
* Other conduct which could reasonably be considered inappropriate in a professional setting
## Our Responsibilities
With the support of the Eclipse Foundation staff (the “Staff”), project committers and leaders are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
Project committers and leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
## Scope
This Code of Conduct applies within all project spaces, and it also applies when an individual is representing the Eclipse Foundation project or its community in public spaces. Examples of representing a project or community include posting via an official social media account, or acting as a project representative at an online or offline event. Representation of a project may be further defined and clarified by project committers, leaders, or the EMO.
## Enforcement
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the Staff at codeofconduct@eclipse.org. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The Staff is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
Project committers or leaders who do not follow the Code of Conduct in good faith may face temporary or permanent repercussions as determined by the Staff.
## Attribution
This Code of Conduct is adapted from the https://www.contributor-covenant.org[Contributor Covenant] , version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct/[https://www.contributor-covenant.org/version/1/4/code-of-conduct.html]
\ No newline at end of file
////
// Copyright (c) 2021 Contributors to the Eclipse Foundation
//
// This program and the accompanying materials are made
// available under the terms of the Eclipse Public License 2.0
// which is available at https://www.eclipse.org/legal/epl-2.0/
//
// SPDX-License-Identifier: EPL-2.0
////
include::docs/_attributes.asciidoc[]
# Security Policy
The {trace} project follows the https://www.eclipse.org/security/policy.php[Eclipse Vulnerability Reporting Policy].
Vulnerabilities are tracked by the Eclipse security team, in cooperation with the TRACE4CPS project leads.
Fixing vulnerabilities is taken care of by the TRACE4CPS project committers, with assistance and guidance of the security team.
## Supported Versions
Whenever the {trace} project fixes a vulnerability, it will be included in the next release.
## Reporting a Vulnerability
We recommend that in case of suspected vulnerabilities you do not use the TRACE4CPS public issue tracker, but instead contact the Eclipse Security Team directly via security@eclipse.org.
......@@ -14,18 +14,27 @@ include::_attributes.asciidoc[]
include::dev-env-setup.asciidoc[]
[[maven-build]]
== Building with Maven
[CAUTION]
====
{trace} should be built using a _Java 1.8 VM_.
The JDK can be downloaded from e.g. https://www.oracle.com/technetwork/pt/java/javase/downloads/jdk8-downloads-2133151.html[Oracle] or https://adoptium.net/archive.html?variant=openjdk8&jvmVariant=hotspot[Adoptium]. +
To test which Java version is used by Maven, type `mvn -version` in a command shell.
====
To build {trace} with Maven execute the following command in the root:
Linux :: `./build.sh`
Windows :: `.\build.cmd`
Other :: `mvn -Dtycho.pomless.aggregator.names=releng,temporallogic,trace,jfreechart`
NOTE: In the remainder of this document this command will be referred to as `build.sh`
== License header
The Maven build uses https://github.com/mycila/license-maven-plugin[license-maven-plugin] to determine if the link:../releng/legal-defaults/license-header.txt[correct license headers] are used for source files.
The <<maven-build, Maven build>> uses https://github.com/mycila/license-maven-plugin[license-maven-plugin] to determine if the link:../releng/legal-defaults/license-header.txt[correct license headers] are used for source files.
If the header is incorrect the build fails.
Handy commands:
......
......@@ -16,7 +16,7 @@ include::_initCommon.adoc[]
The release notes of {trace} are listed below, in reverse chronological order.
[[release-notes-v0.1]]
=== Version 0.1
=== Version 0.1 (2022-06-17)
The first release of the {trace} project.
This version is a port of https://esi.nl/research/output/tools/trace[ESI TRACE v2.0] that is prepared for its release to the Eclipse foundation.
......@@ -106,14 +106,12 @@
<groupId>org.eclipse.xtext</groupId>
<artifactId>org.eclipse.xtext.xtext.generator</artifactId>
<version>${xtext.version}</version>
<!-- Workaround for https://github.com/eclipse/xtext/issues/1976 and -->
<!-- Workaround for https://github.com/eclipse-equinox/equinox.bundles/issues/54 -->
<exclusions>
<exclusion>
<groupId>org.eclipse.platform</groupId>
<artifactId>org.eclipse.equinox.common</artifactId>
</exclusion>
<exclusion>
<groupId>org.eclipse.platform</groupId>
<artifactId>org.eclipse.core.runtime</artifactId>
<artifactId>*</artifactId>
</exclusion>
</exclusions>
</dependency>
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment