Re: [ALL] GitHub is done with Java 8

Thanks for the tip Piotr. For now it works so I don't plan on changing anything until it breaks. Garu On Mon, Apr 29, 2024, 8:46 AM Piotr P. Karwasz wrote: > Hi Gary, > > On Mon, 29 Apr 2024 at 13:58, Gary Gregory wrote: > > To resolve this issue in the least disruptive manner, I updated buil

Re: [ALL] GitHub is done with Java 8

Hi Gary, On Mon, 29 Apr 2024 at 13:58, Gary Gregory wrote: > To resolve this issue in the least disruptive manner, I updated builds > that need Java 8 AND macOS from "macos-lateset" to "macos-13". In Log4j I updated all builds that require Java 8 + another JDK to use `zulu` as distribution if `r

Re: [ALL] GitHub is done with Java 8

To resolve this issue in the least disruptive manner, I updated builds that need Java 8 AND macOS from "macos-lateset" to "macos-13". This is likely only a medium-term solution until GH "macos-13" support goes bye-bye. Gary On Wed, Apr 24, 2024 at 1:43 PM Slawomir Jaranowski wrote: > > Rob your

Re: [ALL] GitHub is done with Java 8

Rob your project use Operating System macOS 12.7.4 21H1123 switching to macos 14 is waiting for your project. GitHub does not switch all project in the same time. śr., 24 kwi 2024 o 19:15 Rob Spoor napisał(a): > I've just tested one of my own projects that has a matrix setup that's > al

Re: [ALL] GitHub is done with Java 8

s, offering a growing collection of tools to simplify your development tasks. - Merge remote-tracking branch 'origin/dev'... github.com From: Rob Spoor Sent: 24 April 2024 18:14 To: dev@commons.apache.org Subject: Re: [ALL] GitHub is done with Java 8

Re: [ALL] GitHub is done with Java 8

I've just tested one of my own projects that has a matrix setup that's almost the same (I haven't included Java 22), and it was successful: https://github.com/robtimus/application-path/actions/runs/8820506010 The main difference is that I use @v4 instead of a specific commit, but those should

Re: [ALL] GitHub is done with Java 8

Yes, the error I included come from a GH build. Gary On Wed, Apr 24, 2024, 10:05 AM Elliotte Rusty Harold wrote: > That's surprising. What's the context for this? Github actions? > > On Wed, Apr 24, 2024 at 9:57 AM Gary D. Gregory > wrote: > > > > Hi All, > > > > I just saw this on GitHub for

Re: [ALL] GitHub is done with Java 8

Really? https://adoptium.net/temurin/releases/?version=8 seems to have recent versions. setup-java seems to be treating it as a bug at this time: https://github.com/actions/setup-java/issues/625 On Wed, Apr 24, 2024 at 4:12 PM Slawomir Jaranowski wrote: > Hi, > > Temurin jdk distribution doesn'

Re: [ALL] GitHub is done with Java 8

Hi, Temurin jdk distribution doesn't support JDK 8. You can try with zulu. śr., 24 kwi 2024 o 15:57 Gary D. Gregory napisał(a): > Hi All, > > I just saw this on GitHub for our Lang component: > > Error: Could not find satisfied version for SemVer '8'. > > Available versions: 22.0.1+8, 22.0.0+36

Re: [ALL] GitHub is done with Java 8

That's surprising. What's the context for this? Github actions? On Wed, Apr 24, 2024 at 9:57 AM Gary D. Gregory wrote: > > Hi All, > > I just saw this on GitHub for our Lang component: > > Error: Could not find satisfied version for SemVer '8'. > > Available versions: 22.0.1+8, 22.0.0+36, 21.0.3+

[ALL] GitHub is done with Java 8

Hi All, I just saw this on GitHub for our Lang component: Error: Could not find satisfied version for SemVer '8'. Available versions: 22.0.1+8, 22.0.0+36, 21.0.3+9.0.LTS, 21.0.2+13.0.LTS, 21.0.1+12.0.LTS, 21.0.0+35.0.LTS, 20.0.2+9, 20.0.1+9, 20.0.0+36, 19.0.2+7, 19.0.1+10, 19.0.0+36, 18.0.2+1

Re: [All] GitHub action for coverage reports

On Sat, 12 Feb 2022 at 13:39, Gary Gregory wrote: > > There is a Coveralls GitHub action, not sure what that requires though. A quick test with this failed. I found that it does not support jacoco execution files. See Coveralls GH action issue 22 [1]. The issue has some suggestions for a replace

Re: [All] GitHub action for coverage reports

There is a Coveralls GitHub action, not sure what that requires though. Gary On Sat, Feb 12, 2022 at 4:36 AM Alex Herbert wrote: > When the migration was done to change most of commons CI from Travis > to GitHub actions the coverage reporting was lost. This may have been > due to lack of suppor

[All] GitHub action for coverage reports

When the migration was done to change most of commons CI from Travis to GitHub actions the coverage reporting was lost. This may have been due to lack of support in GitHub actions at the time. I think we should add back some coverage reporting. This simplifies PR reviews as currently I am having t

Re: [all] github

On 2020-07-26, Melloware wrote: > I know there seems to to be a holy war about the use of GitHub going > on here This has never been my intention. Far from it. And if you believ I've tried to start any kind of war you must have misread my original mail completely. I'm really sorry about thaty. I

Re: [all] github

Hi. Thanks for detailing your POV. However... Le dim. 26 juil. 2020 à 19:08, Melloware a écrit : > > I know there seems to to be a holy war "holy war" certainly not. The notion of "independence" would be appropriate. > about the use of GitHub going on > here but I thought I would just chime i

Re: [all] github

> On Jul 26, 2020, at 2:11 PM, Gilles Sadowski wrote: > > Le dim. 26 juil. 2020 à 19:58, Rob Tompkins a écrit : >> >> I haven’t read all that’s going on here. But in my mind we treat GitHub as a >> first class citizen, right? > > Depends on what that means. > As Matt said, it's our PR man

Re: [all] github

Le dim. 26 juil. 2020 à 19:58, Rob Tompkins a écrit : > > I haven’t read all that’s going on here. But in my mind we treat GitHub as a > first class citizen, right? Depends on what that means. As Matt said, it's our PR manager. > We’re trying quite hard intact to make it our main working repo

Re: [all] github

Hello. Le dim. 26 juil. 2020 à 19:04, Xeno Amess a écrit : > > I thought it was obvious so I didn't do the benchmark. Performance is so *not* obvious that JMH prints a warning in its output. [So even if the numbers don't match your expectation, you might be right anyway, in some use-cases, or i

Re: [all] github

I haven’t read all that’s going on here. But in my mind we treat GitHub as a first class citizen, right? We’re trying quite hard intact to make it our main working repo infrastructure. That said, there is an Apache policy that we maintain workable copies of everything on owned infrastructure.

Re: [all] github

I know there seems to to be a holy war about the use of GitHub going on here but I thought I would just chime in with some thoughts as an open source developer and avid user of GitHub. There have been so many different points I will only discuss a few that I think are important. 1. GitHub is t

Re: [all] github

I thought it was obvious so I didn't do the benchmark. You need it so I've done it now. pinned at https://github.com/apache/commons-lang/pull/565 Gilles Sadowski 于2020年7月26日周日 下午11:48写道： > 2020-07-26 17:34 UTC+02:00, Xeno Amess : > > Thanks for the suggestions about JIRA message and commit style

Re: [all] github

2020-07-26 17:34 UTC+02:00, Xeno Amess : > Thanks for the suggestions about JIRA message and commit style. > Will find some time to refine the texts. > >> ... randomly picking LANG-1576 (sorry if the others don't fit the >> following), I'll stress again that there are more important things >> to do

Re: [all] github

Thanks for the suggestions about JIRA message and commit style. Will find some time to refine the texts. > ... randomly picking LANG-1576 (sorry if the others don't fit the > following), I'll stress again that there are more important things > to do before such (supposed) performance enhancement.

Re: [all] github

Hi Xeno. 2020-07-26 13:10 UTC+02:00, Xeno Amess : >>> For examples about my prs at commons-lang,if my memory is correct, only >>> gary (and sometimes kinow) reviewed my prs, and I don't think we have > only >>> two committers in commons-lang. > >> Are there JIRA reports? > > My log here is: > > LA

Re: [all] github

> On Jul 26, 2020, at 7:17 AM, Xeno Amess wrote: > >  >> >>> For examples about my prs at commons-lang,if my memory is correct, only >>> gary (and sometimes kinow) reviewed my prs, and I don't think we have > only >>> two committers in commons-lang. > >> Are there JIRA reports? > > My log

Re: [all] github

>> For examples about my prs at commons-lang,if my memory is correct, only >> gary (and sometimes kinow) reviewed my prs, and I don't think we have only >> two committers in commons-lang. > Are there JIRA reports? My log here is: LANG-1545 merged by gary LANG-1561 merged by gary LANG-1563 merged

Re: [all] github

2020-07-26 5:00 UTC+02:00, Xeno Amess : >>GitHub is basically our interactive pull request interface. If we didn’t > have that, I bet we’d be running GitLab ourselves or similar. > > Yes, that is what I think gitbox lacks. As Matt says above, the functionality is there. As noted in my previous me

Re: [all] github (was Re: [VOTE] Create additional mailing lists for automated posts)

>GitHub is basically our interactive pull request interface. If we didn’t have that, I bet we’d be running GitLab ourselves or similar. Yes, that is what I think gitbox lacks. Cannot imagine a git-based website having no convenient pr system... >Also, being that the bar to be a committer here is

Re: [all] github (was Re: [VOTE] Create additional mailing lists for automated posts)

GitHub is basically our interactive pull request interface. If we didn’t have that, I bet we’d be running GitLab ourselves or similar. Also, being that the bar to be a committer here is fairly low, getting access to gitbox directly isn’t too difficult. On Fri, Jul 24, 2020 at 12:17 Xeno Amess wr

Re: [all] github (was Re: [VOTE] Create additional mailing lists for automated posts)

Hello. Le ven. 24 juil. 2020 à 17:45, Stefan Bodewig a écrit : > > This is an attempt at answering something raised be Gilles in a > different thread. I'm afraid it is getting longer than I > intended. Something seems to need to get out. Sorry. > > On 2020-07-23, Gilles Sadowski wrote: > > > I mi

Re: [all] github (was Re: [VOTE] Create additional mailing lists for automated posts)

On 2020-07-24, Xeno Amess wrote: >> We respectfully discuss and in the end come to a compromise or a common >> ground where we can agree to disagree. I still see this happen here and >> don't think all of us need to have the same opinion. > So maybe at the end some of commons repos using as new

Re: [all] github (was Re: [VOTE] Create additional mailing lists for automated posts)

> We respectfully discuss and in the end come to a compromise or a common ground where we can agree to disagree. I still see this happen here and don't think all of us need to have the same opinion. So maybe at the end some of commons repos using as new version of dependencies as they can, others

Re: [all] github (was Re: [VOTE] Create additional mailing lists for automated posts)

On 2020-07-24, Xeno Amess wrote: > As for community building, I agree with you that commons seems not a > close community, but I doubt it be github's fault. even there be no > github, sub-repos in commons are not that close to each other. Commons is an old project and it started with a striving

Re: [all] github (was Re: [VOTE] Create additional mailing lists for automated posts)

for example...we become even hard to get an agreement on whether to upgrade dependencies...(sigh) Atleast on this thing I don't think github is the one to blame... Xeno Amess 于 2020年7月25日周六 上午1:21写道： > As for community building, I agree with you that commons seems not a close > community, but I

Re: [all] github (was Re: [VOTE] Create additional mailing lists for automated posts)

As for community building, I agree with you that commons seems not a close community, but I doubt it be github's fault. even there be no github, sub-repos in commons are not that close to each other. Xeno Amess 于 2020年7月25日周六 上午1:16写道： > besides, that is JIRA where we can apply patch, but I thin

Re: [all] github (was Re: [VOTE] Create additional mailing lists for automated posts)

besides, that is JIRA where we can apply patch, but I think it SHOULD be done on gutbox. github, gitlab, all of them have a convienent pr system. so yes our JIRA is good, I like JIRA. But for gitbox, I think it really lack lots of things. Or, there be those things, but not open. Xeno Amess 于 2020

Re: [all] github (was Re: [VOTE] Create additional mailing lists for automated posts)

you know that is really complex and time costing... especially when we want some trigger invoked like travis-ci. Stefan Bodewig 于 2020年7月25日周六 上午1:06写道： > On 2020-07-24, Xeno Amess wrote: > > > I will explain why github come to be center, but not apache gitbox. > > 1.1 > > I have right to regist

Re: [all] github (was Re: [VOTE] Create additional mailing lists for automated posts)

Apologize for being in mood. So my opinion is if github is the only way people where ANY people can create pr, then no wonder it will become center gradually. Gary Gregory 于 2020年7月25日周六 上午12:53写道： > Xeno, > > Your last sentence contains language that is completely inappropriate here. > > Please

Re: [all] github (was Re: [VOTE] Create additional mailing lists for automated posts)

On 2020-07-24, Xeno Amess wrote: > I will explain why github come to be center, but not apache gitbox. > 1.1 > I have right to register an account on github. > 1.2 > I registered an account at github. > 1.3 > I commit then create pr. > 1.4 > pr get reviewed then merged. I am fully aware of how gi

Re: [all] github (was Re: [VOTE] Create additional mailing lists for automated posts)

Xeno, Your last sentence contains language that is completely inappropriate here. Please take a breath. Any point you are trying to make is most likely to get lost by your invective. Gary On Fri, Jul 24, 2020, 12:40 Xeno Amess wrote: > I will explain why github come to be center, but not apac

Re: [all] github (was Re: [VOTE] Create additional mailing lists for automated posts)

I will explain why github come to be center, but not apache gitbox. 1.1 I have right to register an account on github. 1.2 I registered an account at github. 1.3 I commit then create pr. 1.4 pr get reviewed then merged. 2.1 I have no right to register on apache gitbox. 2.2 I can not register on ap

[all] github (was Re: [VOTE] Create additional mailing lists for automated posts)

This is an attempt at answering something raised be Gilles in a different thread. I'm afraid it is getting longer than I intended. Something seems to need to get out. Sorry. On 2020-07-23, Gilles Sadowski wrote: > I missed the turn where this project's PMC decided that we must > be present on GH

Re: [bcel][all] GitHub Actions for Maven builds

I think I replied to the wrong email. On Sun, Sep 1, 2019 at 04:53, Gilles Sadowski wrote: > Hi. > > 2019-09-01 6:08 UTC+02:00, Matt Sicker : > > If you enable the project authorization setting on Jenkins, you can store > > credentials in a specific user who the build runs as. It’s somewhat > >

Re: [bcel][all] GitHub Actions for Maven builds

Hi. 2019-09-01 6:08 UTC+02:00, Matt Sicker : > If you enable the project authorization setting on Jenkins, you can store > credentials in a specific user who the build runs as. It’s somewhat > primitive at the moment, but I’ve been working on related features lately > to improve the situation ther

Re: [bcel][all] GitHub Actions for Maven builds

If you enable the project authorization setting on Jenkins, you can store credentials in a specific user who the build runs as. It’s somewhat primitive at the moment, but I’ve been working on related features lately to improve the situation there for more complex CICD scenarios. Jenkins pipelines a

Re: [bcel][all] GitHub Actions for Maven builds

Le sam. 31 août 2019 à 19:22, Gary Gregory a écrit : > > That is what I thinking, using GitHub actions we can keep builds and > sources in one place. Well two places: sources+builds in Apache and GitHub. > It feels like we can remove Travis. I can see this page https://travis-ci.org/apache/co

RE: [bcel][all] GitHub Actions for Maven builds

][all] GitHub Actions for Maven builds That is what I thinking, using GitHub actions we can keep builds and sources in one place. Well two places: sources+builds in Apache and GitHub. It feels like we can remove Travis. Gary On Sat, Aug 31, 2019, 12:53 Matt Sicker wrote: > GitHub Actions

Re: [bcel][all] GitHub Actions for Maven builds

That is what I thinking, using GitHub actions we can keep builds and sources in one place. Well two places: sources+builds in Apache and GitHub. It feels like we can remove Travis. Gary On Sat, Aug 31, 2019, 12:53 Matt Sicker wrote: > GitHub Actions are more of a replacement for Travis currentl

Re: [bcel][all] GitHub Actions for Maven builds

GitHub Actions are more of a replacement for Travis currently. Provided you’re not doing anything fancy in your pipelines, it might not require Jenkins, either. On Sat, Aug 31, 2019 at 11:17, Stefan Bodewig wrote: > On 2019-08-31, Gary Gregory wrote: > > > On Sat, Aug 31, 2019 at 10:58 AM Gilles

Re: [bcel][all] GitHub Actions for Maven builds

On 2019-08-31, Gary Gregory wrote: > On Sat, Aug 31, 2019 at 10:58 AM Gilles Sadowski > wrote: >> Links returns "404". > Works for me, anyone else? Only works if you are logged in - an probably a member of the apache organization. github returns 404 for links you are not allowed to see. Stefa

Re: [bcel][all] GitHub Actions for Maven builds

Le sam. 31 août 2019 à 17:42, Gilles Sadowski a écrit : > Le sam. 31 août 2019 à 17:30, Romain Manni-Bucau > a écrit : > > > > s/irrelevant/being transformed/ ;), tasks change, human stays > > No, it won't just be a transformation: Fulfilling a mission (at the > service of humans) requires some

Re: [bcel][all] GitHub Actions for Maven builds

Le sam. 31 août 2019 à 17:30, Romain Manni-Bucau a écrit : > > s/irrelevant/being transformed/ ;), tasks change, human stays No, it won't just be a transformation: Fulfilling a mission (at the service of humans) requires some measure of independence. Reliance on an external entity (for services c

Re: [bcel][all] GitHub Actions for Maven builds

s/irrelevant/being transformed/ ;), tasks change, human stays Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn

Re: [bcel][all] GitHub Actions for Maven builds

Le sam. 31 août 2019 à 17:19, Romain Manni-Bucau a écrit : > > Works for me too Maybe another service that requires being logged in (?). > Looks cool, just needs synchro with infra If the above is true, then just another step towards making "infra" (and Apache) irrelevant in the not so far futu

Re: [bcel][all] GitHub Actions for Maven builds

Works for me too Looks cool, just needs synchro with infra probably if we need secrets to deploy on nexus or so Le sam. 31 août 2019 à 17:08, Gary Gregory a écrit : > On Sat, Aug 31, 2019 at 10:58 AM Gilles Sadowski > wrote: > > > Hello. > > > > Le sam. 31 août 2019 à 14:28, Gary Gregory a >

Re: [bcel][all] GitHub Actions for Maven builds

On Sat, Aug 31, 2019 at 10:58 AM Gilles Sadowski wrote: > Hello. > > Le sam. 31 août 2019 à 14:28, Gary Gregory a > écrit : > > > > Hi All: > > > > FYI: I've played a bit with GitHub Actions to run builds. You can see an > > example here for Commons BCEL: > > > > https://github.com/apache/common

Re: [bcel][all] GitHub Actions for Maven builds

Hello. Le sam. 31 août 2019 à 14:28, Gary Gregory a écrit : > > Hi All: > > FYI: I've played a bit with GitHub Actions to run builds. You can see an > example here for Commons BCEL: > > https://github.com/apache/commons-bcel/actions Links returns "404". Gilles > > Gary ---

[bcel][all] GitHub Actions for Maven builds

Hi All: FYI: I've played a bit with GitHub Actions to run builds. You can see an example here for Commons BCEL: https://github.com/apache/commons-bcel/actions Gary

Re: [all] GitHub Release Notes

Quite possibly. I find a bit of overlapping concerns between Incubator and Commons due to the diversity of projects within. On Sun, Mar 17, 2019 at 03:50, Rob Tompkins wrote: > > > > On Mar 15, 2019, at 1:05 PM, Matt Sicker wrote: > > > > Isn't there a related convo at the Incubator about that?

Re: [all] GitHub Release Notes

> On Mar 15, 2019, at 1:05 PM, Matt Sicker wrote: > > Isn't there a related convo at the Incubator about that? I’m not on at the incubatorguess I should subscribe. But wait...didn’t you tell me to do something like that some where else like a month ago :-P -Rob > > Anyways, this would

Re: [all] GitHub Release Notes

Isn't there a related convo at the Incubator about that? Anyways, this would be a neat feature for adding mirrors of official releases. The automatic releases feature for when you make a git tag can look weird, though, since they're not the actual release typically. On Sat, 9 Mar 2019 at 19:16, R

[all] GitHub Release Notes

Now that we have gitbox enabled, committers can “draft releases” in github which includes the ability to upload artifacts and add release notes to tags. I’ll give an example of what’s possible with the upcoming release of the [commons-release-plugin]. At $work I’ve been using this functionality

Re: [All] GitHub partial update

On Tue, 06 Mar 2018 14:31:24 +, Gary Gregory wrote: Yep, INFRA... Gary On Tue, Mar 6, 2018, 07:24 Otto Fowler wrote: You should open an INFRA ticket Done: https://issues.apache.org/jira/projects/INFRA/issues/INFRA-16150 Gilles On March 6, 2018 at 09:12:41, Gilles (gil...@harfan

Re: [All] GitHub partial update

Yep, INFRA... Gary On Tue, Mar 6, 2018, 07:24 Otto Fowler wrote: > You should open an INFRA ticket > > On March 6, 2018 at 09:12:41, Gilles (gil...@harfang.homelinux.org) wrote: > > > Hi. > > > > It seems there are glitches with the mirroring (?). > > > > The current version of this file (on Gi

Re: [All] GitHub partial update

You should open an INFRA ticket On March 6, 2018 at 09:12:41, Gilles (gil...@harfang.homelinux.org) wrote: > Hi. > > It seems there are glitches with the mirroring (?). > > The current version of this file (on GitHub) > > > https://github.com/apache/commons-numbers/blob/master/commons-numbers-com

[All] GitHub partial update

Hi. It seems there are glitches with the mirroring (?). The current version of this file (on GitHub) https://github.com/apache/commons-numbers/blob/master/commons-numbers-complex/src/test/java/org/apache/commons/numbers/complex/CStandardTest.java is not the same as on Apache https://git1-