tycho

How to analyze low-level OSGi problems during tycho test execution?

╄→гoц情女王★ 提交于 2019-12-03 13:23:29
When executing JUnit test with tycho-surefire-plugin , tycho forks an equinox runtime. In rare cases it may happen that some bundles in the OSGi test runtime cannot be resolved/started (e.g. package uses conflicts). If you read the debug log (maven CLI option -X ), you will find something like !ENTRY org.eclipse.osgi 2 0 2012-10-08 16:41:31.635 !MESSAGE The following is a complete list of bundles which are not resolved, see the prior log entry for the root cause if it exists: !SUBENTRY 1 org.eclipse.osgi 2 0 2012-10-08 16:41:31.635 An error has occurred. See the log file C:\mytestproject.tests

How to automate version number update process for my Eclipse plugin built with Maven

a 夏天 提交于 2019-12-03 10:31:16
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: <plugin id="com.my.plugin" download-size="0" install-size="0" version="1.0.0" unpack="false"/> The files

How can I use a local directory as target platform for a Tycho build?

孤街醉人 提交于 2019-12-03 06:04:55
问题 I want to build an RCP-Application with a target platform which is a directory with Maven/Tycho. Now I have some troubles that the dependencies could not be resolved. Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from de.test.prototype.main 1.0.0.qualifier to bundle org.eclipse.ui 0.0.0.", "Unable to satisfy dependency from de.test.prototype.main 1.0.0.qualifier to bundle org.eclipse.core.runtime 0.0.0.",

How can I use a local directory as target platform for a Tycho build?

倖福魔咒の 提交于 2019-12-02 19:34:41
I want to build an RCP-Application with a target platform which is a directory with Maven/Tycho. Now I have some troubles that the dependencies could not be resolved. Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from de.test.prototype.main 1.0.0.qualifier to bundle org.eclipse.ui 0.0.0.", "Unable to satisfy dependency from de.test.prototype.main 1.0.0.qualifier to bundle org.eclipse.core.runtime 0.0.0.", ... All in all there are several dependency resolution problems, so I think Tycho can't use my target

How to build a feature to a zip file using Tycho

谁说胖子不能爱 提交于 2019-12-02 10:52:58
问题 I'm trying to export an Eclipse feature using Tycho, replacing the "Export Wizard" found on the Eclipse overview of the feature. The wizard gives the option for the export destination as a zip file. Is there a way to do the same with Tycho? 回答1: In order to build a zip file with the feature and the feature's plug-ins, you need to add a module of the assembly packaging type eclipse-repository to your reactor: Add an eclipse-repository module with the same parent POM as the eclipse-feature

Tycho cannot resolve dependency to bundle although present in the target file

送分小仙女□ 提交于 2019-12-02 06:06:20
问题 I set up a Tycho build for multiple plug-ins, a feature, a site and a target defined within the pom.xml s. I can run my application from within the Eclipse IDE. Also, a mvn clean package builds just fine. However, when I add a plug-in which needs ca.odell.glazedlists (which is also in my target definition) I can still run it from within the IDE, but the mvn clean package build fails. Any ideas what to do? Maven output and pom.xml follow. Maven output [INFO] Computing target platform for

Set a Target Platform for pom.xml Based Repositories

喜夏-厌秋 提交于 2019-12-02 04:15:21
问题 In Tycho there are two ways to define the target platform: a target file and the <repositories> tag of the pom.xml . According to the manual, both can be used; they just have different drawbacks. The target file is easy and straightforward, especially if you worked with Eclipse PDE before switching to Tycho. What I don't get is how do you develop against a target definition defined in the pom.xml . Dependencies are not added to a "Maven Dependencies" folder in the Java project, like they are

How to add the plugin with my RCP application in the Tycho SWTBot test runtime

烂漫一生 提交于 2019-12-01 18:32:03
问题 My RCP was created on a 3.x Eclipse and is now on 4.x using the compatibility layer. This is the setup that I have: I have two plugins: xyz-plugin and xyz-rcp-plugin . My RCP application is composed of these two plugins. I have a Test fragment ( xyz-test ) whose host plugin is xyz-plugin and contains SWTBot tests. My product configuration points to the application defined in the plugin.xml of xyz-rcp-plugin . When I run the SWTBot Test via Eclipse, it all works ok. I point it to the correct

How to add the plugin with my RCP application in the Tycho SWTBot test runtime

穿精又带淫゛_ 提交于 2019-12-01 17:54:26
My RCP was created on a 3.x Eclipse and is now on 4.x using the compatibility layer. This is the setup that I have: I have two plugins: xyz-plugin and xyz-rcp-plugin . My RCP application is composed of these two plugins. I have a Test fragment ( xyz-test ) whose host plugin is xyz-plugin and contains SWTBot tests. My product configuration points to the application defined in the plugin.xml of xyz-rcp-plugin . When I run the SWTBot Test via Eclipse, it all works ok. I point it to the correct application on the Main tab and it launches the correct one. When I try to run it via Maven (using mvn

Mac distribution of Eclipse RCP application built with Tycho on Windows doesn't start

北慕城南 提交于 2019-12-01 17:53:50
I have built an Eclipse RCP application (Indigo) with Tycho. The build is run on a Win 7, 64-bit machine. The parent POM includes: <plugin> <groupId>org.eclipse.tycho</groupId> <artifactId>target-platform-configuration</artifactId> <version>${tycho-version}</version> <configuration> <resolver>p2</resolver> <environment> <os>linux</os> <ws>gtk</ws> <arch>x86_64</arch> </environment> <environment> <os>win32</os> <ws>win32</ws> <arch>x86_64</arch> </environment> <environment> <os>macosx</os> <ws>cocoa</ws> <arch>x86_64</arch> </environment> ... The product configuration looks like this (with a