tycho

With maven/tycho build for Nodeclipse Eclipse plugin there is new p2 repository every release. Release is done on Bintray that does not allow to update files. So every version goes in its folder. BaseFolder BaseFolder/VersionFolder1 BaseFolder/VersionFolder2 BaseFolder/VersionFolder3 Is it possible to have BaseFolder prepared once as extendable p2 repository, and VersionFolderN added later? So that there would be only one URL for updates and Eclipse platform could discover updates in the repository. What you are looking for is a composite p2 repository. You'll just need the following two files

I'm trying to build a p2 repository from Tycho feature artifacts which are deployed in a remote Maven repository, without having to install the artifacts into the local Maven repository first (as in Tycho fails to resolve reference from product to eclipse-feature from a different reactor build ), and without having to build all features and the repository together in a single reactor build. Background I have a multi-module Tycho project that builds several Eclipse plugins and features. So that I can build each module separately - and so that I can reference OSGI artifacts in our Nexus Maven

There are two main approaches when developing an OSGi application with Maven: POM-first and MANIFEST first. I'm looking for an answer that is in a form of a table that shows pros and cons of each method. To be more specific, I would also like to know how it relates to: Maturity of toolset Vendor independence Development ease (which includes finding people who can do the development on the tooling) Compatibility Avoiding ClassNotFound Avoiding manual work At present this is what I can come up with POM-First Pros (using maven-bundle-plugin) Leverages existing Maven skills, repositories and

Our company uses Maven. We use the Nexus repository manager in order to store our snapshots and releases. Currently, we are developing a product based on Eclipse. We use Tycho to do that. The problem is the following: In our Eclipse-based product we have many features. Our idea is build each feature (or group of features) separately and put them in internal p2 repositories. When one features requires another feature, we point the target platform to necessary internal p2 repository. Currently, we build application with Tycho. We make our features "deployable", so Tycho produces a P2 site in

I want to build a project in Maven using eclipse-plugin packaging, but I get the following error for my POM: [ERROR] Unknown packaging: eclipse-plugin @ line 15, column 13 . pom.xml: <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> <parent> <relativePath>../releng/pom.xml</relativePath> <groupId>net.sf.logsaw</groupId> <artifactId>parent</artifactId> <version>1.0.0-SNAPSHOT</version> </parent> <artifactId

I created a Tycho project with an eclipse-plugin packaging. The project includes some dependencies that are specified via pom.xml. The relevant pom sections are: <properties> <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding> <tycho.version>0.15.0</tycho.version> </properties> <build> <sourceDirectory>src</sourceDirectory> <plugins> <plugin> <groupId>org.eclipse.tycho</groupId> <artifactId>tycho-maven-plugin</artifactId> <version>${tycho.version}</version> <extensions>true</extensions> </plugin> <plugin> <groupId>org.eclipse.tycho</groupId> <artifactId>target-platform