Re: [cross-project-issues-dev] Jetty 1.0.11 needs java.lang.module

[Ed Willink <ed.willink@xxxxxxxxx>]

Hi

Thanks. Yes a more recent Tycho fixed it.

Sorry for the slow acknowledgement. Initially changing Tycho provoked 
some magic failures that mysteriously went away.

Echoing a similar problem on the winsigner improvement thread...

Is it possible for the platform to define a stable compatible e.g. 
eclipse-tycho-version to allow in pom.xml

<tycho-version>${eclipse-tycho-version}</tycho-version>
<tycho-extras-version>${tycho-version}</tycho-extras-version>

so that 'lazy' developers do not have to keep diagnosing breakages?

    Regards

        Ed Willink

On 18/09/2022 18:38, Christoph Läubrich wrote:
> This is not a bug in jetty but normal behavior.
>
> You should update your toolchain, Tycho 2.1.0 is outdated, it was 
> release about two years ago...
>
> Am 18.09.22 um 19:29 schrieb Ed Willink:
> > Hi
> >
> > My build 
> > (https://ci.eclipse.org/ocl/job/ocl-codegen-tests/127/console) has 
> > started to fail with
> >
> > [ERROR] Cannot resolve target definition: [ERROR] Software being 
> > installed: org.eclipse.sdk.feature.group 4.25.0.v20220831-1800 
> > [ERROR] Missing requirement: org.eclipse.jetty.util 10.0.11 requires 
> > 'java.package; java.lang.module 0.0.0' but it could not be found 
> > [ERROR] Cannot satisfy dependency: org.eclipse.help.feature.group 
> > 2.3.1100.v20220831-1800 depends on: org.eclipse.equinox.p2.iu; 
> > org.eclipse.jetty.util [10.0.11,10.0.11] [ERROR] Cannot satisfy 
> > dependency: org.eclipse.platform.feature.group 4.25.0.v20220831-1800 
> > depends on: org.eclipse.equinox.p2.iu; org.eclipse.help.feature.group 
> > [2.3.1100.v20220831-1800,2.3.1100.v20220831-1800] [ERROR] Cannot 
> > satisfy dependency: org.eclipse.sdk.feature.group 
> > 4.25.0.v20220831-1800 depends on: org.eclipse.equinox.p2.iu; 
> > org.eclipse.platform.feature.group 
> > [4.25.0.v20220831-1800,4.25.0.v20220831-1800]
> >
> > Java modules is something I have never got to grips with.
> >
> > Is this a Jetty bug in introducing a new mandatory dependency in a 
> > maintenance release, or is it something where some more platform 
> > modules visibility magic is required?
> >
> >      Regards
> >
> >          Ed Willink
> >
> >
> > _______________________________________________
> > 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