This causes several troubles so +1 and thanks for driving it.

G


On Mon, Dec 15, 2025 at 3:53 PM Ferenc Csaky <[email protected]> wrote:

> Now that I checked around a bit in the flink-connector-shared-utils repo,
> I see
> there is already a ticket for this [1].
>
> Although the open change sets the parent version to 1.2.0 instead of 2.0.0,
> which seems problematic IMO, cause this will be a breaking change.
>
> Anyways, I'll check if Tom can still work on this and wrap this change up.
>
> Best,
> Ferenc
>
> [1] https://issues.apache.org/jira/browse/FLINK-38048
>
>
>
> On Monday, December 15th, 2025 at 15:16, Martijn Visser <
> [email protected]> wrote:
>
> >
> >
> > +1 for bumping this. Thanks for raising it Ferenc!
> >
> > On Mon, Dec 15, 2025 at 2:44 PM Ferenc Csaky [email protected] wrote:
> >
> > > Hello devs,
> > >
> > > I'd like to start a discussion about releasing flink-connector-parent
> 2.0,
> > > which
> > > would drop JDK8 support. With core Flink dropping JDK8 support starting
> > > with
> > > 2.0, I think it makes sense to follow this up on the connector front.
> > >
> > > Currently, the default java version is set to JDK8 here [1].
> Technically
> > > it is
> > > still possible to override that behavior using the dedicated Maven
> > > profile, e.g.
> > > "java11-target", but that is not too intuitive and can lead to
> mistakes,
> > > cause
> > > IDEs (IntelliJ) might generate Maven configs to override the target
> level,
> > > leading to unnecessary or faulty Maven compiler configs.
> > >
> > > I believe providing a version that has a more recent JDK as default
> would
> > > be
> > > easier on the connector code if they would like to utilize some JDK8+
> > > features.
> > >
> > > In case a connector still requires JDK8, the 1.1.0 parent version does
> not
> > > go
> > > anywhere.
> > >
> > > I am happy to make the change and driving the release.
> > >
> > > WDYT?
> > >
> > > Best,
> > > Ferenc
> > >
> > > [1]
> > >
> https://github.com/apache/flink-connector-shared-utils/blob/d719c95235db17f5932d1bb5d917f7d6e195c371/pom.xml#L63
>

Reply via email to