-
Notifications
You must be signed in to change notification settings - Fork 613
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EBR 1.3.0-SNAPSHOTS has regression issues due to port to Tycho 2.0.0 #1011
Comments
Tycho 2.0.0 is bumping up min requirement to JDK-11. I am open to alternatives and workarounds if anyone has any ideas. |
AFAIK Tycho only requires Java 11 to run. That should not affect the build results. So if you are able to run your build with Java 11 and have the maven-compiler-plugin correctly configured to produce Java 8 compatible code, there should be no issue. Of coures the BREE in the MANIFEST needs to be verified and it should be tested in an environment executed with Java 8. But from my experience this should be ok. |
@fipro78 |
@nikhilnanivadekar Can you run the p2 repo creation in a separate process/step with its own JRE? |
@guw will need a bit of guidance and expertise here. Doesn’t the p2 repo require the EC jars to be available? The EC jars will have to be created using JDK 8 and then p2 repo will have to be created using JDK-11. The second part is where I am not following how it’ll come together? Should we script something in a different repo, where the EC jars can be fetched from maven central and then bundled to a p2 repo? This will separate the project, process for p2 creation and actual jar creation. |
@nikhilnanivadekar
Actually you are not publishing that p2 update site anymore, as it did not contain features. So someone created an additional build that consumes the temporary created p2 update site to create another p2 update site based on features. This build step is AFAIK separated already. And that result is published by you. The question now is, do you still need the p2 repo build based on EBR at the end of the Eclipse Collections build, or would it work that the p2 repo build based on features can be executed by consuming the Eclipse Collections from Maven and not from a locally build artefact. |
@fipro78 I think there might be a disconnect in my understanding. The problem here is this, the first build p2-repository itself is failing, so it is not creating the artifacts. Now if it means that p2-repository does not need any Tycho dependencies, then we should clean up the module. But I am in no way an expert in this integration. |
@nikhilnanivadekar Does the build still fail for you? The SNAPSHOT should be back to the old version as I reverted the Tycho 2.0.0 PR. We'll revisit this one, potentially for a different stream/version of the EBR plug-ins. https://ci.eclipse.org/ebr/job/ebr-maven-plugins/422/console |
@guw triggered our pipelines. It will most likely succeed, as things were fine till the port to 2.0.0 was merged. |
Is EBR still required for building the OSGi MANIFEST.MF or can this be done as part of the jar build? |
@guw I dont know how to create the OSGi MANIFEST.MF any other way. If there are other ways, happy to change it. Would appreciate all the help I can get in this. |
@guw @nikhilnanivadekar the manifest is already generated in the jar build. I did this with my contributions lately. You should see an OSGi manifest now also in the Maven published artifacts |
You can always fall back to using the OSGi bundle manifest with the bnd Maven plug-in directly. The subsequent Tycho build could then work with pom dependencies consider. As these are two reactors, each reactor can use a different JVM. The first Maven build needs to "mvn install" artifacts into the local Maven repository (on the CI machine). The Tycho can then consume those artifacts directly from the build machine. |
@guw @nikhilnanivadekar can confirm the builds that were failing the last 2-3 days are working fine now. |
Bugzilla: https://bugs.eclipse.org/bugs/show_bug.cgi?id=567399
https://pipelines.actions.githubusercontent.com/JkyRYJ2TyKWwyWVC64gcjuCucC48E3LHwbAHn3mhzMN5NnNwUC/_apis/pipelines/1/runs/4476/signedlogcontent/3?urlExpires=2020-09-27T22%3A14%3A37.2435567Z&urlSigningMethod=HMACV1&urlSignature=rcRrLZvPeQxNhzbcoar03niBURjKkqu5zmm11jPRV7c%3D
The text was updated successfully, but these errors were encountered: