Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Eclipse Platform to prefer use of dependencies from Maven Central rather than Orbit

Christoph,

Comments below.

On 06.04.2022 06:55, Christoph Läubrich wrote:
> Might this approach be a problem for projects with very
> low Java target level?

Is this relevant given that platform already requires Java 11?

This is similar to asking if JDT's compiler stopped supporting Java 11 is relevant?   Yes, because not everyone is building with the latest platform.  I have builds like this:

  https://ci.eclipse.org/emf/job/all-target-platforms/

This thing tests really old crap and uses Tycho do the builds and run the tests.

To generalize, of course it's relevant that a build system is able to respect the compiler levels and BREEs of the projects being compiled.  The current Platform is not the center of the universe.


> would be required to use a recent version of Tycho, but that might not
> support building the old Java EE levels anymore.

New features require new version correct, but it should not be an issue see above, anyways I'm currently working in fixing a bug [1] for compiling java 8 with and tycho has a integration-test for compiling with an java 8 jdk so if 'old Java EE levels' not means JSE1.4 or something...

> Also everyone using the Target Platform Definition language *.tpd
> might be out, since that tooling cannot generate the new syntax
> I believe.

There is an open issue  [2]for that but it has not gotten much attention yet.

> but if you have ever managed targets with 1500 plugins you really
> don't want to go back from such a component based approach, towards
> a single file

From 2022-03 on PDE supports references of other target files [3], so you could either use this directly, or have one "main" target with maven deps, that includes another that is generated by the TPD files.


[1] https://github.com/eclipse/tycho/issues/51
[2] https://github.com/eclipse-cbi/targetplatform-dsl/issues/115
[3] https://www.eclipse.org/eclipse/news/4.23/pde.php#pde-editor-include


Am 05.04.22 um 20:46 schrieb Michael Keppler:
Might this approach be a problem for projects with very low Java target
level? From my understanding, to be able to use that mechanism they
would be required to use a recent version of Tycho, but that might not
support building the old Java EE levels anymore.

Also everyone using the Target Platform Definition language *.tpd might
be out, since that tooling cannot generate the new syntax I believe.
https://github.com/eclipse-cbi/targetplatform-dsl. Of course everyone
using TPD can just maintain .target files instead, but if you have ever
managed targets with 1500 plugins, you really don't want to go back from
such a component based approach, towards a single file, without comments
etc.

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev


Back to the top