On Fri, 2023-06-02 at 15:28 +0200, Konrad Windszus wrote:
> Thanks, but I would rename the page. The failures are not specific to
> Jenkins or CI but rather generic Maven build with Java 17 issues.
> Konrad
Sure, feel free to rename as you see fit.
Thanks,
Robert
Thanks, but I would rename the page. The failures are not specific to Jenkins
or CI but rather generic Maven build with Java 17 issues.
Konrad
> Am 02.06.2023 um 13:40 schrieb Robert Munteanu :
>
> Hi,
>
>> On Fri, 2023-05-12 at 14:24 +0200, Konrad Windszus wrote:
>> All other failing
Hi,
On Fri, 2023-05-12 at 14:24 +0200, Konrad Windszus wrote:
> All other failing modules either need to be fixes accordingly or
> deprecated.
I created a wiki page [1] which tracks failures that are often seen
when updating to a new Java version. Feel free to use it as a reference
for known
Hi,
Given Robert stated
> If I'm the only one concerned, then we should not spend more time
> talking about it and "just do it" instead :-)
And no one else raised any concern I will go ahead and merge the PR connected
with https://issues.apache.org/jira/browse/SLING-11843.
Hopefully that
On Mon, 2023-05-15 at 16:51 +0200, Konrad Windszus wrote:
>
>
> > Is a Jenkins rebuild
> > going to happen once the
> > https://github.com/apache/sling-tooling-jenkins/pull/16 is merged
> > or
> > will the potential failures be exposed once a new CI job runs?
> >
> No, not automatically. But
> Is a Jenkins rebuild
> going to happen once the
> https://github.com/apache/sling-tooling-jenkins/pull/16 is merged or
> will the potential failures be exposed once a new CI job runs?
>
No, not automatically. But either through a dedicated build (due to some
commits in the affected module
On Mon, 2023-05-15 at 13:31 +, Stefan Seifert wrote:
>
> > -Original Message-
> > From: Robert Munteanu
> > Sent: Monday, May 15, 2023 2:57 PM
> > To: dev@sling.apache.org
> > Subject: Re: Automatically build on ASF Jenkins with Java 11/17 on
> > Linux/Windows
> >
> > I was thinking
> -Original Message-
> From: Robert Munteanu
> Sent: Monday, May 15, 2023 2:57 PM
> To: dev@sling.apache.org
> Subject: Re: Automatically build on ASF Jenkins with Java 11/17 on
> Linux/Windows
>
> I was thinking of a set of gradual changes:
>
> 1. Add Windows alongside Linux
> 2. Add
On Mon, 2023-05-15 at 12:51 +, Stefan Seifert wrote:
>
> > The concern I raised was on making it hard to fix a module because
> > we
> > introduce multiple changes
> >
> > - Java 8 → Java 11, Java 17
> > - Linux → Linux, Windows
> >
> > That will make it more difficult to get the module
> The concern I raised was on making it hard to fix a module because we
> introduce multiple changes
>
> - Java 8 → Java 11, Java 17
> - Linux → Linux, Windows
>
> That will make it more difficult to get the module building again. I am
> not _that_ worried about Windows, I am more thinking
Hi,
On Fri, 2023-05-12 at 14:24 +0200, Konrad Windszus wrote:
> Hi,
> Currently we still build by default all our modules with Java 8 on
> Linux only [1].
> In SLING-11843 I proposed to change the default to Java 11 and 17
> with Linux and Windows.
> The default build (i.e. the one which deploys
robert detected a bigger number of builds failing with those new defaults (~90)
- but after looking on the list of failures it seems to me that most of them
affect modules not touched for some years, and likely on completely outdated
sling-parent pom. only a few current ones have issues with
Hi,
Currently we still build by default all our modules with Java 8 on Linux only
[1].
In SLING-11843 I proposed to change the default to Java 11 and 17 with Linux
and Windows.
The default build (i.e. the one which deploys the Snapshot) would be Java 11 on
Linux.
As there were some concerns
13 matches
Mail list logo
