tycho | based interactive simulation of our solar system | Frontend Framework library

I have a multi module project with a plugin and fragment to test this plugin. The build is done through maven/tycho. Maven v.3.8.4 and Tycho v2.6.0.

In the fragment I have 3 Unit and 1 Integration test, in the test folder:

I have two projects:

1. An Eclipse project build with pomless Tycho approach
2. A plain Java project build with plain Maven, no OSGI, no Tycho

I need to use some of the bundles from the 1st project in the 2nd project. I tried to install the jar files from the 1st project into a local maven repository using mvn clean install. And tried to reference them from the 2nd project. But I get the following error:

Failed to execute goal on project ...: Could not resolve dependencies for project ...: Failed to collect dependencies at bpms:bpms.util.jdk:jar:0.1.0-SNAPSHOT: Failed to read artifact descriptor for bpms:bpms.util.jdk:jar:0.1.0-SNAPSHOT: Failure to find bpms:bundles:pom:1.0.0-SNAPSHOT in https://repo.maven.apache.org/maven2 was cached in the local repository, the resolution will not be reattempted until the update interval of central has elapsed or updates are forced -> [Help 1]

The bpms.util.jdk-0.1.0-SNAPSHOT.pom file contains the following:

I thought to have studied enough Maven + Tycho to configure at least a minimal target environment for a headless build, but still I am unable to make this small example work. I have three projects:

• test, that contains
  • sub.ui and
  • sub.target

The test project has just a pom.xml that builds the two subprojects and whose only interesting part is the section:

Recently, it has become possible to Execute unit-tests with eclipse-plugin packaging. And, in addition there is support for resolving JUnit Classpath Containers.

I would like to execute unit-tests with eclipse-plugin packaging, but would like to use the mockito library in addition to JUnit. I have a pomless build and would like to keep it that way. I do not want to add non-PDE files to the build, unless this is unavoidable.

Question: What is the idiomatic/intended/correct way to add this dependency, or any other test-time dependencies?

Note: I am aware of the use of fragments for unit testing. This is not what I am after. I actually want to use the new mechanism, if possible, or hear that this is currently impossible.

For my initial purposes, and given these are intended to be Unit-tests, running non-OSGI would be ok. If there is a means for OSGI as well, that would be great, but I cannot imagine where the platform configuration could be stored.

Using tycho 1.x worked for my target platform definition based RCP application including features with dependencies from different repositories. Because of a bug with tool bars in RCP 4.18, I updated the project to RCP 4.20. With this RCP version, my UI tests does not work anymore with Tycho 1.x. So I updated to Tycho 2.x but get another problem: The dependencies of features from different repositories can not be resolved anymore, but it works, if I add all the repository URLs to features location in my target platform definition (or adding all repositories and units to one location entry). Because of different reasons, these are no options. Is there a possibility to get the old behavior and what is the reason for this change?

I'm running jQAssistant with an external Neo4J database. I want to collect the data of our projects and keep them externally for queries.

To do that, I reset the store just before scanning the projects.

However, since a couple of days, I'm getting this error:

I want to switch my Eclipse Luna based Eclipse RCP project from the "P2 repository in the POM"-approach to the target file approach. (From approach 2 to approach1 in the Tycho Documentation). This seems straightforward but it is not because I need to support multiple environments.

So in my old parent-pom I had:

I have a Tycho build that builds some plugins. I need to configure the build so that it is reproducible - meaning the created artifacts of different build runs have to be identical.

For my build, this is currently not the case. The differentes of 2 build runs artifact's is the meta data of the files in the jar's. The "Modified" timestamp is different for every build.

So my question is: Does Tycho provide a way to set the modified timestamp to a specific value? Or is there another way do do this?

I have been assigned to a project that builds some Eclipse plugins. There is a root pom.xml, and maven builds it successfully. But when I load it into VSCode, with the Java Pack (vscjava.vscode-java-pack) loaded, and load the Java projects, many files produce errors like