Palladio Maven Tycho Parent

A common parent POM for Maven Tycho based builds of Palladio related Eclipse extensions.

License	The Apache License, Version 2.0
Categories	CLI User Interface
GroupId	org.palladiosimulator
ArtifactId	eclipse-parent
Last Version	0.1.10
Release Date	Oct 10, 2018
Type	pom
Description	Palladio Maven Tycho Parent A common parent POM for Maven Tycho based builds of Palladio related Eclipse extensions.
Project URL	http://www.palladiosimulator.org
Source Code Management	http://github.com/palladiosimulator/palladio-build-mavenparent/tree/master

Download eclipse-parent

Filename	Size
eclipse-parent-0.1.10.pom	9 KB

How to add to project

Apache Maven

<!-- https://jarcasting.com/artifacts/org.palladiosimulator/eclipse-parent/ -->
<dependency>
    <groupId>org.palladiosimulator</groupId>
    <artifactId>eclipse-parent</artifactId>
    <version>0.1.10</version>
    <type>pom</type>
</dependency>

Gradle Groovy

// https://jarcasting.com/artifacts/org.palladiosimulator/eclipse-parent/
implementation 'org.palladiosimulator:eclipse-parent:0.1.10'

Gradle Kotlin

// https://jarcasting.com/artifacts/org.palladiosimulator/eclipse-parent/
implementation ("org.palladiosimulator:eclipse-parent:0.1.10")

Apache Buildr

'org.palladiosimulator:eclipse-parent:pom:0.1.10'

Apache Ivy

<dependency org="org.palladiosimulator" name="eclipse-parent" rev="0.1.10">
  <artifact name="eclipse-parent" type="pom" />
</dependency>

Groovy Grape

@Grapes(
@Grab(group='org.palladiosimulator', module='eclipse-parent', version='0.1.10')
)

Scala SBT

libraryDependencies += "org.palladiosimulator" % "eclipse-parent" % "0.1.10"

Leiningen

[org.palladiosimulator/eclipse-parent "0.1.10"]

Dependencies

There are no dependencies for this project. It is a standalone project that does not depend on any other jars.

Project Modules

There are no modules declared in this project.

Palladio-Build-MavenParent

Using the eclipse-parent-updatesite base POM, you can define Maven Tycho based Palladio builds with little effort. The parent POM covers

• compilation of java and xtend code
• building of plugins and features
• building of source plugins and source features
• test execution and coverage reports
• API documentation using javadoc
• checkstyle generation
• updating, filtering, and merging of target platform definitions

Requirements

• your project has to have a root POM that is an aggregating POM as well
• you have to activate the following extensions in the extensions.xml in the .mvn folder
  • org.eclipse.tycho.extras:tycho-pomless:1.7.0
  • org.palladiosimulator:tycho-tp-refresh-maven-plugin:0.2.5
• you have to refer to the parent POM in your root POM

Target Platform

You can define your target platform explicitly or by just giving repository URLs to resolve bundles. If you want to use the latter, you have to use the eclipse-parent-updatesite-notp POM. If you want to omit checkstyle checks and source feature generation, you should use eclipse-parent-product.

To define your target platform explicitly, you have to create target platform definitions. The parent POM will take care of merging multiple target definitions. You can refer to target files by defining a property org.palladiosimulator.maven.tychotprefresh.tplocation.n with the path to the file. You can use project coordinates (groupdId:artifactId:version:classifier:fileExtension) as well if your target definition resides inside a maven artifact. Please note that you have to use different numbers for n starting with 2.

You can use additional attributes in the target definition file to filter entries or update version numbers. Please note that you cannot use the Eclipse editor anymore to edit files containing additional attributes.

To select only a subset of your target definition during a build, you have to add the attribute filter to a location element and set the value to any name you like. Afterwards, you have to add a property org.palladiosimulator.maven.tychotprefresh.filter.n with the name you chose to your root POM. Use different numbers n for different filters starting with 2. The parent POM already defines the filters nightly and release that are activated by activating the nightly or release profile. The former is activated if the latter is not activated.

To update versions of units mentioned in the target platform, you have to add the attribute refresh and set it to true. Before the build takes place, the latest versions available in the given location will be used.

You can always have a look at the generated target platform definition in the target folder of your root project.

Update site / JavaDoc

To define an update site, you have to create a POM with packaging type eclipse-repository and place a category.xml besides it. You can edit this file using the default Eclipse editors. The resulting update site will be placed in target/repository. The JavaDoc files will be placed in a javadoc folder inside the repository.

Palladio Simulator

Versions

Version
0.1.10 Oct 10, 2018
0.1.9 Jul 27, 2018
0.1.8 Jun 26, 2018
0.1.7 Jun 25, 2018
0.1.6 Jun 25, 2018
0.1.5 Jun 25, 2018
0.1.4 Apr 26, 2018
0.1.3 Apr 13, 2018
0.1.2 Apr 13, 2018
0.1.1 Mar 23, 2018
0.1.0 Mar 7, 2018