tycho

问题 Is it possible to use the same .target file for every maven subproject? Snippet from the parent .pom file <groupId>root.server</groupId> <artifactId>root.server</artifactId> Snippet from child .pom file <groupId>child.project</groupId> <artifactId>child.project.parent</artifactId> <target> <artifact> <groupId>root.server</groupId> <artifactId>root.server</artifactId> <version>${project.version}</version> <classifier>targetfile</classifier> </artifact> </target> When I try a "mvn clean install

问题 How to build an eclipse RCP app based on Java 11 with tycho? I'm using eclipse 2018-09 RCP + the Java 11 plugin + OpenJDK 11 My application is plugin-based and in all the plugins, the MANIFEST.MF file contains: Bundle-RequiredExecutionEnvironment: JavaSE-11 The tycho build fails with the following exception: [ERROR] Internal error: org.eclipse.tycho.core.osgitools.OsgiManifestParserException: Exception parsing OSGi MANIFEST {...}\META-INF\MANIFEST.MF: Unknown OSGi execution environment:

问题 This is my current test fragment: <packaging>eclipse-test-plugin</packaging> <dependencies> <dependency> <groupId>org.junit</groupId> <artifactId>com.springsource.org.junit</artifactId> <version>4.7.0</version> </dependency> </dependencies> with the following plugins configuration: <plugin> <groupId>org.eclipse.tycho</groupId> <artifactId>tycho-surefire-plugin</artifactId> <version>${tycho.version}</version> <configuration> <dependencies> <dependency> <type>p2-installable-unit</type>

问题 In the past, we had our bundles and features on the file system and made them available in Eclipse through a target definition file with a 'Directory' location. In this way, it was easy to use them with the Export wizards in Eclipse. Now I'm trying to build an eclipse-plugin with Tycho which has third party dependencies, e.g. javax.vecmath and org.apache.commons.math . From what I know, the best way to obtain the dependencies in a Tycho build is through a p2 repository. So I'm using one for

问题 I working with a project similar to the project described here. So, it has a few modules in parent pom.xml: <modules> <module>../de.vogella.tycho.plugin</module> <module>../de.vogella.tycho.feature</module> <module>../de.vogella.tycho.p2updatesite</module> </modules> These modules have a general version number e.g. 1.0.0-SNAPSHOT or without -SNAPSHOT . The feature.xml file needs to contain the same version number: <feature id="com.my.feature" label="My plugin feature" version="1.0.0"> and:

问题 I have a plugin and a feature project in my workspace. When I export the feature manually via File > Export As > Feature everything works well. I'm trying to write an automatic plugin building and exporting script to get rid of this chore. I converted feature project to Maven project and filled pom.xml with: <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

问题 Background My Eclipse RCP application is built using Tycho. It consists of multiple components (in the form of OSGi bundles/Eclipse plug-ins). One of these component contains the product file and materializes the product. There is a reactor POM at the application root, which builds all components in order, but I also want to build other components independently (using mvn deploy ) . Building such a single component works as follows: Retrieve the latest versions of all the component's

问题 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 回答1: At present this is what I can

问题 I have a bunch of Eclipse-based plugins that I have been migrating to Maven/Tycho. Most of these plugins depend on separate libraries that I now manage through Maven, rather than muddle around with .jar files. The most cumbersome part of my current setup is due to the apparent inability of Tycho to process Maven-only (i.e. non-OSGi) artifacts. My current setup works like this: In the pom.xml of each Eclipse plugin I issue an unpack goal to maven-dependency-plugin during the initialize phase.

问题 In my parent pom I got this configuration to deploy sources jars: <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-source-plugin</artifactId> <executions> <execution> <goals> <goal>jar</goal> <goal>test-jar</goal> </goals> </execution> </executions> </plugin> But the tycho build modules ignore that, so their sources aren't installed/deployed in the maven repository. Which means I can't include them in an assembly (especially if the assembly module is located in another