commit | 1e401ee83e081f078429bbd40d932231e11a1d69 | [log] [tgz] |
---|---|---|
author | Jens Lidestrom <jens.lidestrom@rt-labs.com> | Mon May 08 18:38:39 2017 +0200 |
committer | Jens Lidestrom <jens.lidestrom@rt-labs.com> | Tue May 16 10:52:53 2017 +0200 |
tree | f48c58f549705e652e1d2f4b6cb936fd207eb6ef | |
parent | 69f6db53a8fae491968cf438522a731ab5c8fd46 [diff] |
Fix struct comment duplicated and indentation bugs * When the CDT handler added an annotation to a struct it doesn't remove an already existing annotation. The old one remains alongside the new one. This change makes sure that the old comment is overwritten. * When the CDT handler added an annotation to an element with other elements on the same line the added comment is gobbled. This change fixes that. * Enables the replace-annotation and preserve-comment tests. * Fix empty line when preserving annotation issue. Change-Id: Iba6898d5dd4953e2ad6d72fe784d9736e8cce311 Signed-off-by: Jens Lidestrom <jens.lidestrom@rt-labs.com>
Capra is a configurable and extendable traceability management tool. It is created in the context of an ITEA funded project called AMALTHEA4Public whose main aim is to develop a platform that will improve the development of embedded multicore and many core systems.
Capra uses the Eclipse Modelling Framework (EMF) as its base technology and stores the traceability model as an EMF model. The traceability metamodel is not fixed and can be defined by the user. It relies on the Eclipse Extension mechanism and provides an extension point for artifacts types to be supported. To add a new type of artifact, one simply needs to add an extension to this extension point and implement the provided interfaces.
Before downloading and using Capra, download Eclipse Modelling Environment and make sure you have the listed dependencies installed.
If compilation errors occur during the first build, check if any of the dependencies above are missing. Cleaning all binaries also often helps resolve issues.
Install Maven. Run maven in the root folder:
mvn clean verify
Please make sure that all points in the following checklist are fullfilled before committing your work to a Capra repository:
Organisation of imports and code formatting can be automated by selecting them as save actions for the Java editor in the Eclipse preferences.
It is important to maintain the correct copyright messages, indicating the contributors of each file and that it is covered by the EPL. You can use automation to insert a correct copyright header.
Install the Eclipse Releng Tools. They contain the copyright tool. Use the following copyright header:
Copyright (c) ${date} Chalmers | University of Gothenburg, rt-labs and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html Contributors: Chalmers | University of Gothenburg and rt-labs - initial API and implementation and/or initial documentation
The Contributors entry can be replaced with the appropriate names. Use “Fix copyrights” from the context menu to add the copyrights to all relevant files in a project or folder.