tycho

Is it possible to use Tycho without using p2 to download dependencies or publish the resulting artifacts in? I already have a Maven repository with all the dependencies and I don't want to have a p2 repository with duplicate artifacts just to compile these osgi projects. I also want to publish the resulting artifacts in that same maven repository so that i can have a real centralized repository instead of a maven repository and a p2 repository So basically, i want to remove the need for p2 from my build. I know one option would be to use POM-first tools instead of tycho, but the problem is the

I've got two reactor builds: The first one builds some bundles and an according feature. After a successful clean install the feature is in my local Maven repo. Tycho has also generated p2 meta information ... -p2artifacts.xml and ... -p2metadata.xml The second build contains a feature-based product which is referencing the feature built in the first reactor. When trying a clean install Tycho complains about an unresolved feature - the one of the other reactor build. Failed to execute goal org.eclipse.tycho:tycho-p2-repository-plugin:0.12.0:assemble-repository [...] ["Unable to satisfy

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/maven-4.0.0.xsd"> <modelVersion>4.0.0</modelVersion> <groupId>MyProject</groupId> <artifactId

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 dependencies from our company (p2) repository. Build the component. Deploy the component to our company

I have a project with a couple of dozen Eclipse plugins, all inter-related and living in different subfolders. The build was converted to a multi-module manifest-first Tycho build a couple of years ago and it works quite well. One of the plugins is rather key, and can also be built as a standalone Java app, which doesn't use an Eclipse runtime. Currently it has its own POM file ( pom-standalone.xml ) so that Jenkins can build the standalone app separately and the Tycho build knows nothing about it - the pom-standalone just lists the previously-built plugin jars (thanks Tycho!) and Eclipse

I'm currently trying to get my build (~30 bundles) done by tycho. I faced some confusing problems when using Mockito in my unit tests. I created an eclipse-test-plugin as fragment project to the tested bundle. Since tycho should resolve the required bundles using the manifest, I removed the dependency to mockito from the pom.xml . When I then try to add mockito to the required bundles in the manifest mockito isn't listed. I found this post and created a target platform pointing to eclipse indigo. I included the platform specifics so I don't need the eclipse delta pack. Then the first strange

I am trying to build a p2 repository using Tycho and the tycho-p2-repository-plugin in an eclipse-repository packaging type. When I run the build, it is giving me the following exception: Failed to execute goal org.eclipse.tycho:tycho-p2-repository-plugin:0.13.0:assemble-repository (default-assemble-repository) on project com.mycompany: No content specified for p2 repository Can someone point me to the cause of this problem? You need either of the following files in the root of the eclipse-repository project: A category.xml files with at least one feature referenced in it A *.product file