The Javapocalypse is Monday

[Jerry James]

I've just been looking through my packager-dashboard page.  A
depressingly large chunk of my packages are going to become
unbuildable on Monday when a bunch of orphaned Java packages are
retired.  I think a lot of us are going to be affected.  In my case,
there are quite a few non-Java packages involved (due to the parser
generators antlr3 and antlr4-project), primarily OCaml and python
packages.  Mikolaj has a huge pile of work on his shoulders, so don't
take this as criticism of him.

Here are some of the pain points:
- log4j will be retired, which will break ant.
- hamcrest2 will be retired, which will break apache-commons-lang3,
which will break bcel, which will also break ant.
- google-gson and javassist will be retired, which will break
reflections, which will break jna, which is used by about a dozen
packages, including bcel.
- maven-install-plugin will be retired, which will break tycho, which
will break eclipse.
- args4j will be retired, which will break jacoco and jgit.
- maven-invoker-plugin and several of its dependencies
(maven-doxia-sitetools, plexus-velocity, maven-reporting-api,
maven-script-interpreter, and maven-reporting-impl) will be retired,
which will break xml-maven-plugin, which is used by eclipse.
- jakarta-el and jakarta-server-pages will be retired, which will break eclipse.
- aopalliance will be retired, which will break maven-native.
- jdependency will be retired, which will break maven-shade-plugin,
which is used by openjfx8, a dependency of java-1.8.0-openjdk.
- apache-ivy will be retired, which will break javapackages-tools.

I have packages that depend directly on the following, so I am willing
to adopt them if nobody more competent shows up (although there is no
point in taking ant-contrib if ant is going to be broken anyway):
- ant-contrib
- jakarta-common-httpclient
- jakarta-ws-rs
- maven-invoker-plugin
- spec-version-maven-plugin

I introduced the jansi1 and jline2 packages so that jansi could be
moved to 2.x and jline to 3.x, but I don't actually maintain any
packages that need the old versions.  I would like to give them away
to someone who needs them, but note that you will need to grab
jansi-native as well, before Monday!

Has anybody already done something about any of these packages (and my
packager-dashboard page just hasn't caught up yet)?  Is anybody
planning to do something about any of these packages before they are
retired on Monday?
-- 
Jerry James
http://www.jamezone.org/

[Bruno Wolff III]

I knew that a bunch of java stuff was going away, but I am not sure what 
the impact of that is going to be. Is there a feature page or similar 
that summarizes what the effect we be?

I have one package that produces a java program using ant that I like to be 
able to keep building somehow. There is also an OCaml package I help 
maintain, that is used in an old game that I doubt gets much use these days 
and I wouldn't be too sad if that went away.

Is there a recommendation to move to maven? Is there anything like the 
old gcc based java compiler that could be used? Is there still going 
to be a java runtime?

I spend a lot of time using the former as a passtime game and would miss it 
if it wasn't in Fedora any more.

[Mikolaj Izdebski]

On Thu, Jun 3, 2021 at 11:46 PM Bruno Wolff III <bruno(a)wolff.to&gt; wrote:
>  I knew that a bunch of java stuff was going away, but I am not sure what
>  the impact of that is going to be. Is there a feature page or similar
>  that summarizes what the effect we be?
>
>  I have one package that produces a java program using ant that I like to be
>  able to keep building somehow. There is also an OCaml package I help
>  maintain, that is used in an old game that I doubt gets much use these days
>  and I wouldn't be too sad if that went away. 
Ant stays in Fedora. I am committed to maintaining it.

>  Is there a recommendation to move to maven? Is there anything like
> the
>  old gcc based java compiler that could be used? Is there still going
>  to be a java runtime? 
No, it is not recommended to switch projects built with Ant to use Maven.
GCJ has been retired from Fedora many years ago, OpenJDK is the only
JDK/JRE that is currently in Fedora and it is expected to stay in
Fedora - it is not expected to be retired.

--
Mikolaj Izdebski

>  I spend a lot of time using the former as a passtime game and would
> miss it
>  if it wasn't in Fedora any more.
>  _______________________________________________
>  devel mailing list -- devel(a)lists.fedoraproject.org
>  To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]
>  Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

[Sérgio Basto]

On Thu, 2021-06-03 at 15:30 -0600, Jerry James wrote:
>  I've just been looking through my packager-dashboard page.  A
>  depressingly large chunk of my packages are going to become
>  unbuildable on Monday when a bunch of orphaned Java packages are
>  retired.  I think a lot of us are going to be affected.  In my case,
>  there are quite a few non-Java packages involved (due to the parser
>  generators antlr3 and antlr4-project), primarily OCaml and python
>  packages.  Mikolaj has a huge pile of work on his shoulders, so don't
>  take this as criticism of him.
>  
>  Here are some of the pain points:
>  - log4j will be retired, which will break ant.
>  - hamcrest2 will be retired, which will break apache-commons-lang3,
>  which will break bcel, which will also break ant.
>  - google-gson and javassist will be retired, which will break
>  reflections, which will break jna, which is used by about a dozen
>  packages, including bcel. 
I may take these 4 

>  - maven-install-plugin will be retired, which will break tycho,
> which
>  will break eclipse. 
Eclipse for me may fall, I already use eclipse installer from
https://www.eclipse.org/downloads/ 


>  - args4j will be retired, which will break jacoco and jgit.
>  - maven-invoker-plugin and several of its dependencies
>  (maven-doxia-sitetools, plexus-velocity, maven-reporting-api,
>  maven-script-interpreter, and maven-reporting-impl) will be retired,
>  which will break xml-maven-plugin, which is used by eclipse.
>  - jakarta-el and jakarta-server-pages will be retired, which will
>  break eclipse.
>  - aopalliance will be retired, which will break maven-native.
>  - jdependency will be retired, which will break maven-shade-plugin,
>  which is used by openjfx8, a dependency of java-1.8.0-openjdk.
>  - apache-ivy will be retired, which will break javapackages-tools.
>   
I can also take these two jdependency and  apache-ivy . 

maybe I should also take maven-invoker-plugin . 

what do you think ? 

>  I have packages that depend directly on the following, so I am
>  willing
>  to adopt them if nobody more competent shows up (although there is no
>  point in taking ant-contrib if ant is going to be broken anyway):
>  - ant-contrib
>  - jakarta-common-httpclient
>  - jakarta-ws-rs
>  - maven-invoker-plugin
>  - spec-version-maven-plugin
>  
>  I introduced the jansi1 and jline2 packages so that jansi could be
>  moved to 2.x and jline to 3.x, but I don't actually maintain any
>  packages that need the old versions.  I would like to give them away
>  to someone who needs them, but note that you will need to grab
>  jansi-native as well, before Monday!
>  
>  Has anybody already done something about any of these packages (and
>  my
>  packager-dashboard page just hasn't caught up yet)?  Is anybody
>  planning to do something about any of these packages before they are
>  retired on Monday?
>  -- 
>  Jerry James
>  http://www.jamezone.org/
>  _______________________________________________
>  devel mailing list -- devel(a)lists.fedoraproject.org
>  To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct:    
>  https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines:    
>  https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:    
>  https://lists.fedoraproject.org/archives/list/[e-mail]
>  Do not reply to spam on the list, report it:    
>  https://pagure.io/fedora-infrastructure 
-- 
Sérgio M. B.

[Orion Poplawski]

On 6/3/21 3:55 PM, Sérgio Basto wrote:
>  On Thu, 2021-06-03 at 15:30 -0600, Jerry James wrote:
> > I've just been looking through my packager-dashboard page.  A
> > depressingly large chunk of my packages are going to become
> > unbuildable on Monday when a bunch of orphaned Java packages are
> > retired.  I think a lot of us are going to be affected.  In my case,
> > there are quite a few non-Java packages involved (due to the parser
> > generators antlr3 and antlr4-project), primarily OCaml and python
> > packages.  Mikolaj has a huge pile of work on his shoulders, so don't
> > take this as criticism of him.
> >
> > Here are some of the pain points:
> > - log4j will be retired, which will break ant.
> > - hamcrest2 will be retired, which will break apache-commons-lang3,
> > which will break bcel, which will also break ant.
> > - google-gson and javassist will be retired, which will break
> > reflections, which will break jna, which is used by about a dozen
> > packages, including bcel.
>  
>  I may take these 4 
Just to be clear - "hamcrest" is now at version "2.2" and so should 
replace "hamcrest2".

-- 
Orion Poplawski
he/him/his - surely the least important thing about me
Manager of NWRA Technical Systems          720-772-5637
NWRA, Boulder/CoRA Office             FAX: [phone]
3380 Mitchell Lane                       orion(a)nwra.com
Boulder, CO 80301                 https://www.nwra.com/

[Coty Sutherland]

On Thu, Jun 3, 2021 at 5:56 PM Sérgio Basto <sergio(a)serjux.com&gt; wrote:

>  On Thu, 2021-06-03 at 15:30 -0600, Jerry James wrote:
>  > I've just been looking through my packager-dashboard page.  A
>  > depressingly large chunk of my packages are going to become
>  > unbuildable on Monday when a bunch of orphaned Java packages are
>  > retired.  I think a lot of us are going to be affected.  In my case,
>  > there are quite a few non-Java packages involved (due to the parser
>  > generators antlr3 and antlr4-project), primarily OCaml and python
>  > packages.  Mikolaj has a huge pile of work on his shoulders, so don't
>  > take this as criticism of him.
>  >
>  > Here are some of the pain points:
>  > - log4j will be retired, which will break ant.
>  > - hamcrest2 will be retired, which will break apache-commons-lang3,
>  > which will break bcel, which will also break ant.
>  > - google-gson and javassist will be retired, which will break
>  > reflections, which will break jna, which is used by about a dozen
>  > packages, including bcel.
>
>  I may take these 4
>  
That would be great :D My package (Tomcat) still uses ant to build, so if
you could save it from retirement that would be great. I don't have
bandwidth to take on any additional packages right now, but I don't mind
being a co-maintainer if you feel you need it.


>  > - maven-install-plugin will be retired, which will break tycho,
> which
>  > will break eclipse.
>
>  Eclipse for me may fall, I already use eclipse installer from
>  https://www.eclipse.org/downloads/
>
>
>  > - args4j will be retired, which will break jacoco and jgit.
>  > - maven-invoker-plugin and several of its dependencies
>  > (maven-doxia-sitetools, plexus-velocity, maven-reporting-api,
>  > maven-script-interpreter, and maven-reporting-impl) will be retired,
>  > which will break xml-maven-plugin, which is used by eclipse.
>  > - jakarta-el and jakarta-server-pages will be retired, which will
>  > break eclipse.
>  > - aopalliance will be retired, which will break maven-native.
>  > - jdependency will be retired, which will break maven-shade-plugin,
>  > which is used by openjfx8, a dependency of java-1.8.0-openjdk.
>  > - apache-ivy will be retired, which will break javapackages-tools.
>  >
>
>  I can also take these two jdependency and  apache-ivy .
>
>  maybe I should also take maven-invoker-plugin .
>
>  what do you think ? 

>  > I have packages that depend directly on the following, so I am
>  > willing
>  > to adopt them if nobody more competent shows up (although there is no
>  > point in taking ant-contrib if ant is going to be broken anyway):
>  > - ant-contrib
>  > - jakarta-common-httpclient
>  > - jakarta-ws-rs
>  > - maven-invoker-plugin
>  > - spec-version-maven-plugin
>  >
>  > I introduced the jansi1 and jline2 packages so that jansi could be
>  > moved to 2.x and jline to 3.x, but I don't actually maintain any
>  > packages that need the old versions.  I would like to give them away
>  > to someone who needs them, but note that you will need to grab
>  > jansi-native as well, before Monday!
>  >
>  > Has anybody already done something about any of these packages (and
>  > my
>  > packager-dashboard page just hasn't caught up yet)?  Is anybody
>  > planning to do something about any of these packages before they are
>  > retired on Monday?
>  
I've dropped all the direct dependencies that I had which were being
orphaned, so the only outstanding problems I have are ant (which may be
addressed by Sérgio) and javapackages-tools, which I'm a bit confused
about. It seems that the latest build relies on java-11, not java-8 so not
sure why it's showing up that way in the dep map. It seems that the map
isn't generated often, so maybe it's just outdated?

>  --
>  > Jerry James
>  > http://www.jamezone.org/
>  > _______________________________________________
>  > devel mailing list -- devel(a)lists.fedoraproject.org
>  > To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>  > Fedora Code of Conduct:
>  > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  > List Guidelines:
>  > https://fedoraproject.org/wiki/Mailing_list_guidelines
>  > List Archives:
>  >
>  https://lists.fedoraproject.org/archives/list/[e-mail]
>  > Do not reply to spam on the list, report it:
>  > https://pagure.io/fedora-infrastructure
>
>  --
>  Sérgio M. B.
>  _______________________________________________
>  devel mailing list -- devel(a)lists.fedoraproject.org
>  To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct:
>  https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
>  https://lists.fedoraproject.org/archives/list/[e-mail]
>  Do not reply to spam on the list, report it:
>  https://pagure.io/fedora-infrastructure
>

[Fabio Valentini]

On Fri, Jun 4, 2021 at 1:35 PM Coty Sutherland
<csutherl(a)fedoraproject.org&gt; wrote:
>  
(snip)

>  
> I've dropped all the direct dependencies that I had
which were being orphaned, so the only outstanding problems I have are ant (which may be
addressed by Sérgio) and javapackages-tools, which I'm a bit confused about. It seems
that the latest build relies on java-11, not java-8 so not sure why it's showing up
that way in the dep map. It seems that the map isn't generated often, so maybe
it's just outdated?

The reports are generated and refreshed every few hours. The limiting
factor in this case is probably the lack of successful rawhide
composes for the last days.
However, javapackages-tools supports both openjdk 11 and openjdk 1.8,
with Java 11 being the default, so your assessment above is not
correct either.

Fabio

[Sérgio Basto]

On Fri, 2021-06-04 at 07:34 -0400, Coty Sutherland wrote:
>  On Thu, Jun 3, 2021 at 5:56 PM Sérgio Basto <sergio(a)serjux.com&gt;
> wrote:
>  > On Thu, 2021-06-03 at 15:30 -0600, Jerry James wrote:
>  > > I've just been looking through my packager-dashboard page.  A
>  > > depressingly large chunk of my packages are going to become
>  > > unbuildable on Monday when a bunch of orphaned Java packages are
>  > > retired.  I think a lot of us are going to be affected.  In my
>  > case,
>  > > there are quite a few non-Java packages involved (due to the parser
>  > > generators antlr3 and antlr4-project), primarily OCaml and python
>  > > packages.  Mikolaj has a huge pile of work on his shoulders, so
>  > don't
>  > > take this as criticism of him.
>  >
> >   
>  > > Here are some of the pain points:
>  > > - log4j will be retired, which will break ant.
>  > > - hamcrest2 will be retired, which will break apache-commons-lang3,
>  > > which will break bcel, which will also break ant.
>  > > - google-gson and javassist will be retired, which will break
>  > > reflections, which will break jna, which is used by about a dozen
>  > > packages, including bcel.
> >   
>  > I may take these 4 
> >   
>  
>  
>  That would be great :D My package (Tomcat) still uses ant to build, so
>  if you could save it from retirement that would be great. I don't have
>  bandwidth to take on any additional packages right now, but I don't
>  mind being a co-maintainer if you feel you need it.
>   
> >   
>  > > - maven-install-plugin will be retired, which will
> break tycho,
>  > which
>  > > will break eclipse.
> >   
>  > Eclipse for me may fall, I already use eclipse installer
> from
>  > https://www.eclipse.org/downloads/ 
> >   
> >   
>  > > - args4j will be
> retired, which will break jacoco and jgit.
>  > > - maven-invoker-plugin and several of its dependencies
>  > > (maven-doxia-sitetools, plexus-velocity, maven-reporting-api,
>  > > maven-script-interpreter, and maven-reporting-impl) will be
>  > retired,
>  > > which will break xml-maven-plugin, which is used by eclipse.
>  > > - jakarta-el and jakarta-server-pages will be retired, which will
>  > > break eclipse.
>  > > - aopalliance will be retired, which will break maven-native.
>  > > - jdependency will be retired, which will break maven-shade-plugin,
>  > > which is used by openjfx8, a dependency of java-1.8.0-openjdk.
>  > > - apache-ivy will be retired, which will break javapackages-tools.
>  >
> >   
> >   
>  > I can also take these two
> jdependency and  apache-ivy . 
> >   
>  > maybe I should also take maven-invoker-plugin . 
> >   
>  > what do you think ?
> >   
> >   
>  > > I have packages that
> depend directly on the following, so I am
>  > > willing
>  > > to adopt them if nobody more competent shows up (although there is
>  > no
>  > > point in taking ant-contrib if ant is going to be broken anyway):
>  > > - ant-contrib
>  > > - jakarta-common-httpclient
>  > > - jakarta-ws-rs
>  > > - maven-invoker-plugin
>  > > - spec-version-maven-plugin
>  >
> >   
>  > > I introduced the jansi1 and jline2 packages so that
> jansi could be
>  > > moved to 2.x and jline to 3.x, but I don't actually maintain any
>  > > packages that need the old versions.  I would like to give them
>  > away
>  > > to someone who needs them, but note that you will need to grab
>  > > jansi-native as well, before Monday!
>  >
> >   
>  > > Has anybody already done something about any of
> these packages (and
>  > > my
>  > > packager-dashboard page just hasn't caught up yet)?  Is anybody
>  > > planning to do something about any of these packages before they
>  > are
>  > > retired on Monday?
> >   
>  
>  
>  I've dropped all the direct dependencies that I had which were being
>  orphaned, so the only outstanding problems I have are ant (which may be
>  addressed by Sérgio) and javapackages-tools, which I'm a bit confused
>  about. It seems that the latest build relies on java-11, not java-8 so
>  not sure why it's showing up that way in the dep map. It seems that the
>  map isn't generated often, so maybe it's just outdated?
>   
For now, I took log4j, apache-ivy and jdependency 

I will evaluate google-gson and javassist (*)

Best regards,

(*)
- google-gson and javassist will be retired, which will break
 reflections, which will break jna, which is used by about a dozen
 packages, including bcel.


>   
-- 
Sérgio M. B.

[Mikolaj Izdebski]

On Fri, Jun 4, 2021 at 1:44 PM Coty Sutherland
<csutherl(a)fedoraproject.org&gt; wrote:
>  On Thu, Jun 3, 2021 at 5:56 PM Sérgio Basto <sergio(a)serjux.com&gt; wrote:
> >
> > On Thu, 2021-06-03 at 15:30 -0600, Jerry James wrote:
> > > I've just been looking through my packager-dashboard page.  A
> > > depressingly large chunk of my packages are going to become
> > > unbuildable on Monday when a bunch of orphaned Java packages are
> > > retired.  I think a lot of us are going to be affected.  In my case,
> > > there are quite a few non-Java packages involved (due to the parser
> > > generators antlr3 and antlr4-project), primarily OCaml and python
> > > packages.  Mikolaj has a huge pile of work on his shoulders, so don't
> > > take this as criticism of him.
> > >
> > > Here are some of the pain points:
> > > - log4j will be retired, which will break ant.
> > > - hamcrest2 will be retired, which will break apache-commons-lang3,
> > > which will break bcel, which will also break ant.
> > > - google-gson and javassist will be retired, which will break
> > > reflections, which will break jna, which is used by about a dozen
> > > packages, including bcel.
> >
> > I may take these 4
>
>
>  That would be great :D My package (Tomcat) still uses ant to build, so if you could save
> it from retirement that would be great. I don't have bandwidth to take on any
> additional packages right now, but I don't mind being a co-maintainer if you feel you
> need it.
>
> >
> > > - maven-install-plugin will be retired, which will break tycho, which
> > > will break eclipse.
> >
> > Eclipse for me may fall, I already use eclipse installer from
> > https://www.eclipse.org/downloads/
> >
> >
> > > - args4j will be retired, which will break jacoco and jgit.
> > > - maven-invoker-plugin and several of its dependencies
> > > (maven-doxia-sitetools, plexus-velocity, maven-reporting-api,
> > > maven-script-interpreter, and maven-reporting-impl) will be retired,
> > > which will break xml-maven-plugin, which is used by eclipse.
> > > - jakarta-el and jakarta-server-pages will be retired, which will
> > > break eclipse.
> > > - aopalliance will be retired, which will break maven-native.
> > > - jdependency will be retired, which will break maven-shade-plugin,
> > > which is used by openjfx8, a dependency of java-1.8.0-openjdk.
> > > - apache-ivy will be retired, which will break javapackages-tools.
> > >
> >
> > I can also take these two jdependency and  apache-ivy .
> >
> > maybe I should also take maven-invoker-plugin .
> >
> > what do you think ?
> >
> >
> > > I have packages that depend directly on the following, so I am
> > > willing
> > > to adopt them if nobody more competent shows up (although there is no
> > > point in taking ant-contrib if ant is going to be broken anyway):
> > > - ant-contrib
> > > - jakarta-common-httpclient
> > > - jakarta-ws-rs
> > > - maven-invoker-plugin
> > > - spec-version-maven-plugin
> > >
> > > I introduced the jansi1 and jline2 packages so that jansi could be
> > > moved to 2.x and jline to 3.x, but I don't actually maintain any
> > > packages that need the old versions.  I would like to give them away
> > > to someone who needs them, but note that you will need to grab
> > > jansi-native as well, before Monday!
> > >
> > > Has anybody already done something about any of these packages (and
> > > my
> > > packager-dashboard page just hasn't caught up yet)?  Is anybody
> > > planning to do something about any of these packages before they are
> > > retired on Monday?
>
>
>  I've dropped all the direct dependencies that I had which were being orphaned, so the
> only outstanding problems I have are ant (which may be addressed by Sérgio) and
> javapackages-tools, which I'm a bit confused about. It seems that the latest build
> relies on java-11, not java-8 so not sure why it's showing up that way in the dep map.
> It seems that the map isn't generated often, so maybe it's just outdated? 
Some subpackages of javapackages-tools depend on OpenJDK 11, some on OpenJDK 8.
That is intentional - it gives packagers an ability to choose which
JDK should be used to build their packages.

--
Mikolaj Izdebski

> > > --
> > > Jerry James
> > > http://www.jamezone.org/
> > > _______________________________________________
> > > devel mailing list -- devel(a)lists.fedoraproject.org
> > > To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
> > > Fedora Code of Conduct:
> > > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > > List Guidelines:
> > > https://fedoraproject.org/wiki/Mailing_list_guidelines
> > > List Archives:
> > > https://lists.fedoraproject.org/archives/list/[e-mail]
> > > Do not reply to spam on the list, report it:
> > > https://pagure.io/fedora-infrastructure
> >
> > --
> > Sérgio M. B.
> > _______________________________________________
> > devel mailing list -- devel(a)lists.fedoraproject.org
> > To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
> > Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]
> > Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
>
>  _______________________________________________
>  devel mailing list -- devel(a)lists.fedoraproject.org
>  To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]
>  Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

[Miro Hrončok]

On 03. 06. 21 23:30, Jerry James wrote:
>  - hamcrest2 will be retired, which will break apache-commons-lang3,
Package "hamcrest" was updated to 2.x, so this should be OK.

https://lists.fedoraproject.org/archives/list/[e-mail].o...

-- 
Miro Hrončok
-- 
Phone: [phone]
IRC: mhroncok

[Fabio Valentini]

On Thu, Jun 3, 2021 at 11:31 PM Jerry James <loganjerry(a)gmail.com&gt; wrote:
>  I've just been looking through my packager-dashboard page.  A
>  depressingly large chunk of my packages are going to become
>  unbuildable on Monday when a bunch of orphaned Java packages are
>  retired.  I think a lot of us are going to be affected.  In my case,
>  there are quite a few non-Java packages involved (due to the parser
>  generators antlr3 and antlr4-project), primarily OCaml and python
>  packages.  Mikolaj has a huge pile of work on his shoulders, so don't
>  take this as criticism of him.
>
>  Here are some of the pain points:
>  - log4j will be retired, which will break ant.
>  - hamcrest2 will be retired, which will break apache-commons-lang3,
>  which will break bcel, which will also break ant.
>  - google-gson and javassist will be retired, which will break
>  reflections, which will break jna, which is used by about a dozen
>  packages, including bcel.
>  - maven-install-plugin will be retired, which will break tycho, which
>  will break eclipse.
>  - args4j will be retired, which will break jacoco and jgit.
>  - maven-invoker-plugin and several of its dependencies
>  (maven-doxia-sitetools, plexus-velocity, maven-reporting-api,
>  maven-script-interpreter, and maven-reporting-impl) will be retired,
>  which will break xml-maven-plugin, which is used by eclipse.
>  - jakarta-el and jakarta-server-pages will be retired, which will break eclipse.
>  - aopalliance will be retired, which will break maven-native.
>  - jdependency will be retired, which will break maven-shade-plugin,
>  which is used by openjfx8, a dependency of java-1.8.0-openjdk.
>  - apache-ivy will be retired, which will break javapackages-tools. 
There's even more problems. Some of those packages are also transitive
dependencies of PKI and FreeIPA (core component of Fedora Server
etc.).
I knew two of the guys who worked on the Fedora packages for this
stack, but both have since left Red Hat, so I have no idea what's
going on there.
In general, despite Red Hat's generally big involvement in the Java
world (with OpenJDK, JBoss, WildFly, Quarkus, etc.), their interest in
actually maintaining packages for those projects (except the JDKs) is
... non-existent, which I find baffling.

Fabio

[Alexander Bokovoy]

On pe, 04 kesä 2021, Fabio Valentini wrote:
> On Thu, Jun 3, 2021 at 11:31 PM Jerry James
> <loganjerry(a)gmail.com&gt; wrote:
> >
> > I've just been looking through my packager-dashboard page.  A
> > depressingly large chunk of my packages are going to become
> > unbuildable on Monday when a bunch of orphaned Java packages are
> > retired.  I think a lot of us are going to be affected.  In my case,
> > there are quite a few non-Java packages involved (due to the parser
> > generators antlr3 and antlr4-project), primarily OCaml and python
> > packages.  Mikolaj has a huge pile of work on his shoulders, so don't
> > take this as criticism of him.
> >
> > Here are some of the pain points:
> > - log4j will be retired, which will break ant.
> > - hamcrest2 will be retired, which will break apache-commons-lang3,
> > which will break bcel, which will also break ant.
> > - google-gson and javassist will be retired, which will break
> > reflections, which will break jna, which is used by about a dozen
> > packages, including bcel.
> > - maven-install-plugin will be retired, which will break tycho, which
> > will break eclipse.
> > - args4j will be retired, which will break jacoco and jgit.
> > - maven-invoker-plugin and several of its dependencies
> > (maven-doxia-sitetools, plexus-velocity, maven-reporting-api,
> > maven-script-interpreter, and maven-reporting-impl) will be retired,
> > which will break xml-maven-plugin, which is used by eclipse.
> > - jakarta-el and jakarta-server-pages will be retired, which will break eclipse.
> > - aopalliance will be retired, which will break maven-native.
> > - jdependency will be retired, which will break maven-shade-plugin,
> > which is used by openjfx8, a dependency of java-1.8.0-openjdk.
> > - apache-ivy will be retired, which will break javapackages-tools.
>
> There's even more problems. Some of those packages are also transitive
> dependencies of PKI and FreeIPA (core component of Fedora Server
> etc.).
> I knew two of the guys who worked on the Fedora packages for this
> stack, but both have since left Red Hat, so I have no idea what's
> going on there. 
Dogtag team includes few more people than those who left the team. They
were working past month with other Java teams at Red Hat to figure out
how to support these dependencies in a longer term. The issue of dropped
dependencies is taken seriously but since it involved internal teams'
responsibilities, the discussiuon is not happening on a public mailing
list.

With the help of Mikalaj and Coty, hopefully, most of the issues would
be solved, though at a cost of most of the depdendencies not used by
Dogtag trimmed down. In addition, Dogtag is dropping some of own
internal dependencies to switch its API from XML to JSON[1]. XML support
in Dogtag's REST API is what forces it to require so many orphaned
dependencies in Fedora.

> In general, despite Red Hat's generally big involvement in the
> Java
> world (with OpenJDK, JBoss, WildFly, Quarkus, etc.), their interest in
> actually maintaining packages for those projects (except the JDKs) is
> ... non-existent, which I find baffling. 
In my discussion with some Java application developers, their primary
point of view is that Maven infrastructure provides them with the required
content. There are point of view clashes with the needs of distributions
like Fedora or RHEL. While for RHEL purposes there are infrastructure
pipelines that allow to rebuild curated Maven content and then
package it automatically in a RHEL-friendly way, Fedora project didn't
accept this concept in past[2] -- I am sharing most of the arguments in
[3] myself.  Red Hat's Java-based product deployments are wider than
targetting RHEL or Fedora, that makes a need for unified delivery
approach prioritized and any deviations are much harder to handle.

[1] https://github.com/dogtagpki/pki/issues/3553
[2] https://fedoraproject.org/wiki/KojiMavenSupport
[3] https://fedoraproject.org/wiki/Talk:KojiMavenSupport



-- 
/ Alexander Bokovoy
Sr. Principal Software Engineer
Security / Identity Management Engineering
Red Hat Limited, Finland

[Hans de Goede]

Hi,

On 6/3/21 11:30 PM, Jerry James wrote:
>  I've just been looking through my packager-dashboard page.  A
>  depressingly large chunk of my packages are going to become
>  unbuildable on Monday when a bunch of orphaned Java packages are
>  retired.  I think a lot of us are going to be affected.  In my case,
>  there are quite a few non-Java packages involved (due to the parser
>  generators antlr3 and antlr4-project), primarily OCaml and python
>  packages.  Mikolaj has a huge pile of work on his shoulders, so don't
>  take this as criticism of him.
>  
>  Here are some of the pain points:
>  - log4j will be retired, which will break ant.
>  - hamcrest2 will be retired, which will break apache-commons-lang3,
>  which will break bcel, which will also break ant.
>  - google-gson and javassist will be retired, which will break
>  reflections, which will break jna, which is used by about a dozen
>  packages, including bcel.
>  - maven-install-plugin will be retired, which will break tycho, which
>  will break eclipse.
>  - args4j will be retired, which will break jacoco and jgit.
>  - maven-invoker-plugin and several of its dependencies
>  (maven-doxia-sitetools, plexus-velocity, maven-reporting-api,
>  maven-script-interpreter, and maven-reporting-impl) will be retired,
>  which will break xml-maven-plugin, which is used by eclipse.
>  - jakarta-el and jakarta-server-pages will be retired, which will break eclipse.
>  - aopalliance will be retired, which will break maven-native.
>  - jdependency will be retired, which will break maven-shade-plugin,
>  which is used by openjfx8, a dependency of java-1.8.0-openjdk.
>  - apache-ivy will be retired, which will break javapackages-tools.
>  
>  I have packages that depend directly on the following, so I am willing
>  to adopt them if nobody more competent shows up (although there is no
>  point in taking ant-contrib if ant is going to be broken anyway):
>  - ant-contrib
>  - jakarta-common-httpclient
>  - jakarta-ws-rs
>  - maven-invoker-plugin
>  - spec-version-maven-plugin
>  
>  I introduced the jansi1 and jline2 packages so that jansi could be
>  moved to 2.x and jline to 3.x, but I don't actually maintain any
>  packages that need the old versions.  I would like to give them away
>  to someone who needs them, but note that you will need to grab
>  jansi-native as well, before Monday! 
I've a couple of packages which depend on jline2, so I've just taken
owner ship of jansi-native. Feel free to give jline2 and jansi1 to me
too (FAS: jwrdegoede) I would very much welcome co-maintainers for these,
if anyone wants co-admin rights, just let me know.

I've also taken javacc ownership as some of my packages depend on that too,
again co-maintainers are very much welcome.

Note I just maintain a couple of games written in java and I don't have
much interest in (nor time for) more generic jave packaging work.
I'm assuming that ant and jpackages-tools are going to get taken care
by people who are more into java then me. If those don't get sorted out
I will probably just orphan the 2 games which I maintain, as well as
a bunch of their java deps like bsh, javacc, cortado, (and now also jline2),
etc.

Regards,

Hans

[Jerry James]

On Fri, Jun 4, 2021 at 11:53 AM Hans de Goede <hdegoede(a)redhat.com&gt; wrote:
>  I've a couple of packages which depend on jline2, so I've
> just taken
>  owner ship of jansi-native. Feel free to give jline2 and jansi1 to me
>  too (FAS: jwrdegoede) I would very much welcome co-maintainers for these,
>  if anyone wants co-admin rights, just let me know. 
Sorry to start this thread and then disappear.  A whole lot of
$REALLIFE has happened in the past few days.  (All good, just very
time consuming.)

I've transferred jansi1 and jline2 to you.  I have taken ant-contrib,
jakarta-commons-httpclient, jakarta-ws-rs, and
spec-version-maven-plugin.  I will try to remove dependencies on these
packages, if possible, with an eye to retiring them later if that can
be done.
-- 
Jerry James
http://www.jamezone.org/

[Mikolaj Izdebski]

On Thu, Jun 3, 2021 at 11:32 PM Jerry James <loganjerry(a)gmail.com&gt; wrote:
>  I've just been looking through my packager-dashboard page.  A
>  depressingly large chunk of my packages are going to become
>  unbuildable on Monday when a bunch of orphaned Java packages are
>  retired.  I think a lot of us are going to be affected.  In my case,
>  there are quite a few non-Java packages involved (due to the parser
>  generators antlr3 and antlr4-project), primarily OCaml and python
>  packages.  Mikolaj has a huge pile of work on his shoulders, so don't
>  take this as criticism of him.
>
>  Here are some of the pain points:
>  - log4j will be retired, which will break ant. 
I will either adopt log4j or unretire log4j12; ant should still be functional.

>  - hamcrest2 will be retired, which will break apache-commons-lang3,
apache-commons-lang3 depends on hamcrest, not hamcrest2.

>  - maven-install-plugin will be retired, which will break tycho,
> which
>  will break eclipse. 
maven-install-plugin depends on maven2 which has been deprecated in
Fedora end EOL upstream for more than 12 years. Therefore I'm not
going to maintain it. It should be fairly easy to patch tycho not to
depend on maven-install-plugin (one liner patch).

>  - apache-ivy will be retired, which will break javapackages-tools.
Dependency on apache-ivy is optional. There is a bcond in
javapackages-tools.spec file which I will toggle in case apache-ivy is
retired.

>  I have packages that depend directly on the following, so I am
> willing
>  to adopt them if nobody more competent shows up (although there is no
>  point in taking ant-contrib if ant is going to be broken anyway):
>  - ant-contrib
>  - jakarta-common-httpclient
>  - jakarta-ws-rs
>  - maven-invoker-plugin
>  - spec-version-maven-plugin 
I will be maintaining ant.
maven-invoker-plugin is typically a test dependency, so alternatively
you can disable tests in your packages.
spec-version-maven-plugin can be easily removed, for example see
jakarta-annotations package.

>  I introduced the jansi1 and jline2 packages so that jansi could be
>  moved to 2.x and jline to 3.x, but I don't actually maintain any
>  packages that need the old versions.  I would like to give them away
>  to someone who needs them, but note that you will need to grab
>  jansi-native as well, before Monday! 
Fedora should ideally ship only a single version of libraries like
jansi and jline. Compat packages are intended to be used transitively
until packages are ready to migrate to the latest version. maven
package is a good example - it used to depend on jansi1, but has
recently been ported to jansi, version 2. If no one is interested in
jansi1 and jline2 then it's natural course of action to orphan and
retire them.

--
Mikolaj Izdebski

>  Has anybody already done something about any of these packages (and
> my
>  packager-dashboard page just hasn't caught up yet)?  Is anybody
>  planning to do something about any of these packages before they are
>  retired on Monday?
>  --
>  Jerry James
>  http://www.jamezone.org/
>  _______________________________________________
>  devel mailing list -- devel(a)lists.fedoraproject.org
>  To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]
>  Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

[Sérgio Basto]

On Fri, 2021-06-04 at 20:36 +0200, Mikolaj Izdebski wrote:
>  On Thu, Jun 3, 2021 at 11:32 PM Jerry James
> <loganjerry(a)gmail.com&gt;
>  wrote:
>  > 
>  > I've just been looking through my packager-dashboard page.  A
>  > depressingly large chunk of my packages are going to become
>  > unbuildable on Monday when a bunch of orphaned Java packages are
>  > retired.  I think a lot of us are going to be affected.  In my case,
>  > there are quite a few non-Java packages involved (due to the parser
>  > generators antlr3 and antlr4-project), primarily OCaml and python
>  > packages.  Mikolaj has a huge pile of work on his shoulders, so don't
>  > take this as criticism of him.
>  > 
>  > Here are some of the pain points:
>  > - log4j will be retired, which will break ant.
>  
>  I will either adopt log4j or unretire log4j12; ant should still be
>  functional.
>  
>  > - hamcrest2 will be retired, which will break apache-commons-lang3,
>  
>  apache-commons-lang3 depends on hamcrest, not hamcrest2.
>  
>  > - maven-install-plugin will be retired, which will break tycho, which
>  > will break eclipse.
>  
>  maven-install-plugin depends on maven2 which has been deprecated in
>  Fedora end EOL upstream for more than 12 years. Therefore I'm not
>  going to maintain it. It should be fairly easy to patch tycho not to
>  depend on maven-install-plugin (one liner patch).
>  
>  > - apache-ivy will be retired, which will break javapackages-tools.
>  
>  Dependency on apache-ivy is optional. There is a bcond in
>  javapackages-tools.spec file which I will toggle in case apache-ivy is
>  retired.
>  
>  > I have packages that depend directly on the following, so I am
>  > willing
>  > to adopt them if nobody more competent shows up (although there is no
>  > point in taking ant-contrib if ant is going to be broken anyway):
>  > - ant-contrib
>  > - jakarta-common-httpclient
>  > - jakarta-ws-rs
>  > - maven-invoker-plugin
>  > - spec-version-maven-plugin
>  
>  I will be maintaining ant.
>  maven-invoker-plugin is typically a test dependency, so alternatively
>  you can disable tests in your packages.
>  spec-version-maven-plugin can be easily removed, for example see
>  jakarta-annotations package.
>  
>  > I introduced the jansi1 and jline2 packages so that jansi could be
>  > moved to 2.x and jline to 3.x, but I don't actually maintain any
>  > packages that need the old versions.  I would like to give them away
>  > to someone who needs them, but note that you will need to grab
>  > jansi-native as well, before Monday!
>  
>  Fedora should ideally ship only a single version of libraries like
>  jansi and jline. Compat packages are intended to be used transitively
>  until packages are ready to migrate to the latest version. maven
>  package is a good example - it used to depend on jansi1, but has
>  recently been ported to jansi, version 2. If no one is interested in
>  jansi1 and jline2 then it's natural course of action to orphan and
>  retire them.
>   
I took log4j, apache-ivy and jdependency 

I now I took google-gson and javassist which have more than 100
dependencies 

@Mikolaj Izdebski  I saw you already admin of log4j , let me know I
should add you or if I adopted any wrong package. 




-- 
Sérgio M. B.

[Markku Korkeala]

On 6/4/21 12:30 AM, Jerry James wrote:
>  I have packages that depend directly on the following, so I am
> willing
>  to adopt them if nobody more competent shows up (although there is no
>  point in taking ant-contrib if ant is going to be broken anyway):
>  - ant-contrib
>  - jakarta-common-httpclient
>  - jakarta-ws-rs
>  - maven-invoker-plugin
>  - spec-version-maven-plugin
>  
>  I introduced the jansi1 and jline2 packages so that jansi could be
>  moved to 2.x and jline to 3.x, but I don't actually maintain any
>  packages that need the old versions.  I would like to give them away
>  to someone who needs them, but note that you will need to grab
>  jansi-native as well, before Monday!
>  
>  Has anybody already done something about any of these packages (and my
>  packager-dashboard page just hasn't caught up yet)?  Is anybody
>  planning to do something about any of these packages before they are
>  retired on Monday? 
Hi,

I looked at the orphaned packages looking for new maintainers​,
which affects Clojure-packages and decided to take these:

korkeala: spice-parent, maven-invoker, maven-invoker-plugin,
plexus-velocity,  maven-script-interpreter, maven-mapping, weld-parent,
aopalliance, jakarta-server-pages, javaparser, jakarta-interceptors

these were already taken by someone else:
apache-ivy, jansi-native

Not really sure in what state these packages are, if I dont
have time to maintain them I'll reorphan them and orphan
the Clojure packages as well.

BR,
Markku

[Sérgio Basto]

On Sat, 2021-06-05 at 12:19 +0300, Markku Korkeala wrote:
>  On 6/4/21 12:30 AM, Jerry James wrote:
>  > I have packages that depend directly on the following, so I am
>  > willing
>  > to adopt them if nobody more competent shows up (although there is no
>  > point in taking ant-contrib if ant is going to be broken anyway):
>  > - ant-contrib
>  > - jakarta-common-httpclient
>  > - jakarta-ws-rs
>  > - maven-invoker-plugin
>  > - spec-version-maven-plugin
>  > 
>  > I introduced the jansi1 and jline2 packages so that jansi could be
>  > moved to 2.x and jline to 3.x, but I don't actually maintain any
>  > packages that need the old versions.  I would like to give them away
>  > to someone who needs them, but note that you will need to grab
>  > jansi-native as well, before Monday!
>  > 
>  > Has anybody already done something about any of these packages (and
>  > my
>  > packager-dashboard page just hasn't caught up yet)?  Is anybody
>  > planning to do something about any of these packages before they are
>  > retired on Monday?
>  
>  Hi,
>  
>  I looked at the orphaned packages looking for new maintainers​,
>  which affects Clojure-packages and decided to take these:
>  
>  korkeala: spice-parent, maven-invoker, maven-invoker-plugin,
>  plexus-velocity,  maven-script-interpreter, maven-mapping, weld-parent,
>  aopalliance, jakarta-server-pages, javaparser, jakarta-interceptors
>  
>  these were already taken by someone else:
>  apache-ivy, jansi-native
>  
>  Not really sure in what state these packages are, if I dont
>  have time to maintain them I'll reorphan them and orphan
>  the Clojure packages as well. 
I also have the same plan (if I dont have time to maintain them I'll
reorphan )

Now log4j-1.2 is required for ant and jboss-logging [1] can't we remove
these dependencies on log4j-1.2 ? 


[1] 
ant (maintained by: akurtakov, java-maint-sig, jcapik, mizdebsk)
		ant-1.10.9-2.fc34.src requires ant = 1.10.9-2.fc34,
ant-junit = 1.10.9-2.fc34, mvn(org.apache.logging.log4j:log4j-1.2-api)
= 2.13.3
		ant-apache-log4j-1.10.9-2.fc34.noarch requires
mvn(org.apache.logging.log4j:log4j-1.2-api) = 2.13.3

jboss-logging (maintained by: cfu, cipherboy, ckelley, dmoluguw,
edewata, jmagne, mharmsen)
		jboss-logging-3.4.1-6.fc34.src requires
mvn(org.apache.logging.log4j:log4j-1.2-api) = 2.13.3,
mvn(org.apache.logging.log4j:log4j-api) = 2.13.3


>  BR,
>  Markku
>  _______________________________________________
>  devel mailing list -- devel(a)lists.fedoraproject.org
>  To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct: 
>  https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: 
>  https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives: 
>  https://lists.fedoraproject.org/archives/list/[e-mail]
>  Do not reply to spam on the list, report it: 
>  https://pagure.io/fedora-infrastructure 
-- 
Sérgio M. B.

[Fabio Valentini]

On Sat, Jun 5, 2021 at 4:11 PM Sérgio Basto <sergio(a)serjux.com&gt; wrote:
>  On Sat, 2021-06-05 at 12:19 +0300, Markku Korkeala wrote:
>  > On 6/4/21 12:30 AM, Jerry James wrote:
>  > > I have packages that depend directly on the following, so I am
>  > > willing
>  > > to adopt them if nobody more competent shows up (although there is no
>  > > point in taking ant-contrib if ant is going to be broken anyway):
>  > > - ant-contrib
>  > > - jakarta-common-httpclient
>  > > - jakarta-ws-rs
>  > > - maven-invoker-plugin
>  > > - spec-version-maven-plugin
>  > >
>  > > I introduced the jansi1 and jline2 packages so that jansi could be
>  > > moved to 2.x and jline to 3.x, but I don't actually maintain any
>  > > packages that need the old versions.  I would like to give them away
>  > > to someone who needs them, but note that you will need to grab
>  > > jansi-native as well, before Monday!
>  > >
>  > > Has anybody already done something about any of these packages (and
>  > > my
>  > > packager-dashboard page just hasn't caught up yet)?  Is anybody
>  > > planning to do something about any of these packages before they are
>  > > retired on Monday?
>  >
>  > Hi,
>  >
>  > I looked at the orphaned packages looking for new maintainers,
>  > which affects Clojure-packages and decided to take these:
>  >
>  > korkeala: spice-parent, maven-invoker, maven-invoker-plugin,
>  > plexus-velocity,  maven-script-interpreter, maven-mapping, weld-parent,
>  > aopalliance, jakarta-server-pages, javaparser, jakarta-interceptors
>  >
>  > these were already taken by someone else:
>  > apache-ivy, jansi-native
>  >
>  > Not really sure in what state these packages are, if I dont
>  > have time to maintain them I'll reorphan them and orphan
>  > the Clojure packages as well.
>
>  I also have the same plan (if I dont have time to maintain them I'll
>  reorphan )
>
>  Now log4j-1.2 is required for ant and jboss-logging [1] can't we remove
>  these dependencies on log4j-1.2 ? 
Those packages both no longer depend on log4j12 (it might only look
that way to you because of the virtual provides; what they depend on
is actually only log4j 2.x). I have months ago ported both ant and
jboss-logging packages to use the log4j 1.2 API shim provided by log4j
instead of the old, deprecated, and security hole-y log4j12 package,
which is now retired in Fedora. Because I'd rather have packages use
the actually maintained, new version of log4j instead of an old and
dusty compat package.

Fabio

[Sérgio Basto]

On Sat, 2021-06-05 at 16:27 +0200, Fabio Valentini wrote:
>  On Sat, Jun 5, 2021 at 4:11 PM Sérgio Basto <sergio(a)serjux.com&gt;
> wrote:
>  > 
>  > On Sat, 2021-06-05 at 12:19 +0300, Markku Korkeala wrote:
>  > > On 6/4/21 12:30 AM, Jerry James wrote:
>  > > > I have packages that depend directly on the following, so I am
>  > > > willing
>  > > > to adopt them if nobody more competent shows up (although there
>  > > > is no
>  > > > point in taking ant-contrib if ant is going to be broken anyway):
>  > > > - ant-contrib
>  > > > - jakarta-common-httpclient
>  > > > - jakarta-ws-rs
>  > > > - maven-invoker-plugin
>  > > > - spec-version-maven-plugin
>  > > > 
>  > > > I introduced the jansi1 and jline2 packages so that jansi could
>  > > > be
>  > > > moved to 2.x and jline to 3.x, but I don't actually maintain any
>  > > > packages that need the old versions.  I would like to give them
>  > > > away
>  > > > to someone who needs them, but note that you will need to grab
>  > > > jansi-native as well, before Monday!
>  > > > 
>  > > > Has anybody already done something about any of these packages
>  > > > (and
>  > > > my
>  > > > packager-dashboard page just hasn't caught up yet)?  Is anybody
>  > > > planning to do something about any of these packages before they
>  > > > are
>  > > > retired on Monday?
>  > > 
>  > > Hi,
>  > > 
>  > > I looked at the orphaned packages looking for new maintainers,
>  > > which affects Clojure-packages and decided to take these:
>  > > 
>  > > korkeala: spice-parent, maven-invoker, maven-invoker-plugin,
>  > > plexus-velocity,  maven-script-interpreter, maven-mapping, weld-
>  > > parent,
>  > > aopalliance, jakarta-server-pages, javaparser, jakarta-interceptors
>  > > 
>  > > these were already taken by someone else:
>  > > apache-ivy, jansi-native
>  > > 
>  > > Not really sure in what state these packages are, if I dont
>  > > have time to maintain them I'll reorphan them and orphan
>  > > the Clojure packages as well.
>  > 
>  > I also have the same plan (if I dont have time to maintain them I'll
>  > reorphan )
>  > 
>  > Now log4j-1.2 is required for ant and jboss-logging [1] can't we
>  > remove
>  > these dependencies on log4j-1.2 ?
>  
>  Those packages both no longer depend on log4j12 (it might only look
>  that way to you because of the virtual provides; what they depend on
>  is actually only log4j 2.x). I have months ago ported both ant and
>  jboss-logging packages to use the log4j 1.2 API shim provided by log4j
>  instead of the old, deprecated, and security hole-y log4j12 package,
>  which is now retired in Fedora.  
Hi,
https://src.fedoraproject.org/rpms/log4j12 was retired 8 months ago. 

and I confused log4j12 package with package log4j which also have 1.2-
api  ! 

I took disruptor package because: "Depending on: disruptor (151),
status change: 2021-04-26 (5 weeks ago)" including ant and log4j

>  Because I'd rather have packages use
>  the actually maintained, new version of log4j instead of an old and
>  dusty compat package.
>  
>  Fabio
>  _______________________________________________
>  devel mailing list -- devel(a)lists.fedoraproject.org
>  To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct: 
>  https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: 
>  https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives: 
>  https://lists.fedoraproject.org/archives/list/[e-mail]
>  Do not reply to spam on the list, report it: 
>  https://pagure.io/fedora-infrastructure 
-- 
Sérgio M. B.

[Sérgio Basto]

On Mon, 2021-06-07 at 00:53 +0100, Sérgio Basto wrote:
>  On Sat, 2021-06-05 at 16:27 +0200, Fabio Valentini wrote:
>  > On Sat, Jun 5, 2021 at 4:11 PM Sérgio Basto <sergio(a)serjux.com&gt;
>  > wrote:
>  > > 
>  > > On Sat, 2021-06-05 at 12:19 +0300, Markku Korkeala wrote:
>  > > > On 6/4/21 12:30 AM, Jerry James wrote:
>  > > > > I have packages that depend directly on the following, so I
>  > > > > am
>  > > > > willing
>  > > > > to adopt them if nobody more competent shows up (although
>  > > > > there
>  > > > > is no
>  > > > > point in taking ant-contrib if ant is going to be broken
>  > > > > anyway):
>  > > > > - ant-contrib
>  > > > > - jakarta-common-httpclient
>  > > > > - jakarta-ws-rs
>  > > > > - maven-invoker-plugin
>  > > > > - spec-version-maven-plugin
>  > > > > 
>  > > > > I introduced the jansi1 and jline2 packages so that jansi
>  > > > > could
>  > > > > be
>  > > > > moved to 2.x and jline to 3.x, but I don't actually maintain
>  > > > > any
>  > > > > packages that need the old versions.  I would like to give
>  > > > > them
>  > > > > away
>  > > > > to someone who needs them, but note that you will need to
>  > > > > grab
>  > > > > jansi-native as well, before Monday!
>  > > > > 
>  > > > > Has anybody already done something about any of these
>  > > > > packages
>  > > > > (and
>  > > > > my
>  > > > > packager-dashboard page just hasn't caught up yet)?  Is
>  > > > > anybody
>  > > > > planning to do something about any of these packages before
>  > > > > they
>  > > > > are
>  > > > > retired on Monday?
>  > > > 
>  > > > Hi,
>  > > > 
>  > > > I looked at the orphaned packages looking for new maintainers,
>  > > > which affects Clojure-packages and decided to take these:
>  > > > 
>  > > > korkeala: spice-parent, maven-invoker, maven-invoker-plugin,
>  > > > plexus-velocity,  maven-script-interpreter, maven-mapping,
>  > > > weld-
>  > > > parent,
>  > > > aopalliance, jakarta-server-pages, javaparser, jakarta-
>  > > > interceptors
>  > > > 
>  > > > these were already taken by someone else:
>  > > > apache-ivy, jansi-native
>  > > > 
>  > > > Not really sure in what state these packages are, if I dont
>  > > > have time to maintain them I'll reorphan them and orphan
>  > > > the Clojure packages as well.
>  > > 
>  > > I also have the same plan (if I dont have time to maintain them
>  > > I'll
>  > > reorphan )
>  > > 
>  > > Now log4j-1.2 is required for ant and jboss-logging [1] can't we
>  > > remove
>  > > these dependencies on log4j-1.2 ?
>  > 
>  > Those packages both no longer depend on log4j12 (it might only look
>  > that way to you because of the virtual provides; what they depend
>  > on
>  > is actually only log4j 2.x). I have months ago ported both ant and
>  > jboss-logging packages to use the log4j 1.2 API shim provided by
>  > log4j
>  > instead of the old, deprecated, and security hole-y log4j12
>  > package,
>  > which is now retired in Fedora. 
>  
>  Hi,
>  https://src.fedoraproject.org/rpms/log4j12 was retired 8 months ago. 
>  
>  and I confused log4j12 package with package log4j which also have
>  1.2-
>  api  ! 
>  
>  I took disruptor package because: "Depending on: disruptor (151),
>  status change: 2021-04-26 (5 weeks ago)" including ant and log4j
>   

I also took 
Depending on: jakarta-saaj (155), status change: 2021-04-26 (5 weeks
ago)
Depending on: jakarta-xml-ws (153), status change: 2021-04-26 (5 weeks
ago)
Depending on: jmock (152), status change: 2021-04-26 (5 weeks ago)



>  > Because I'd rather have packages use
>  > the actually maintained, new version of log4j instead of an old and
>  > dusty compat package.
>  > 
>  > Fabio
>  > _______________________________________________
>  > devel mailing list -- devel(a)lists.fedoraproject.org
>  > To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>  > Fedora Code of Conduct: 
>  > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  > List Guidelines: 
>  > https://fedoraproject.org/wiki/Mailing_list_guidelines
>  > List Archives: 
>  > https://lists.fedoraproject.org/archives/list/[e-mail]
>  > Do not reply to spam on the list, report it: 
>  > https://pagure.io/fedora-infrastructure
>  
>  -- 
>  Sérgio M. B.
>  _______________________________________________
>  devel mailing list -- devel(a)lists.fedoraproject.org
>  To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct: 
>  https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: 
>  https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives: 
>  https://lists.fedoraproject.org/archives/list/[e-mail]
>  Do not reply to spam on the list, report it: 
>  https://pagure.io/fedora-infrastructure 
-- 
Sérgio M. B.

[Sérgio Basto]

On Mon, 2021-06-07 at 10:18 +0100, Sérgio Basto wrote:
>  On Mon, 2021-06-07 at 00:53 +0100, Sérgio Basto wrote:
>  > On Sat, 2021-06-05 at 16:27 +0200, Fabio Valentini wrote:
>  > > On Sat, Jun 5, 2021 at 4:11 PM Sérgio Basto <sergio(a)serjux.com&gt;
>  > > wrote:
>  > > > 
>  > > > On Sat, 2021-06-05 at 12:19 +0300, Markku Korkeala wrote:
>  > > > > On 6/4/21 12:30 AM, Jerry James wrote:
>  > > > > > I have packages that depend directly on the following, so I
>  > > > > > am
>  > > > > > willing
>  > > > > > to adopt them if nobody more competent shows up (although
>  > > > > > there
>  > > > > > is no
>  > > > > > point in taking ant-contrib if ant is going to be broken
>  > > > > > anyway):
>  > > > > > - ant-contrib
>  > > > > > - jakarta-common-httpclient
>  > > > > > - jakarta-ws-rs
>  > > > > > - maven-invoker-plugin
>  > > > > > - spec-version-maven-plugin
>  > > > > > 
>  > > > > > I introduced the jansi1 and jline2 packages so that jansi
>  > > > > > could
>  > > > > > be
>  > > > > > moved to 2.x and jline to 3.x, but I don't actually
> maintain
>  > > > > > any
>  > > > > > packages that need the old versions.  I would like to give
>  > > > > > them
>  > > > > > away
>  > > > > > to someone who needs them, but note that you will need to
>  > > > > > grab
>  > > > > > jansi-native as well, before Monday!
>  > > > > > 
>  > > > > > Has anybody already done something about any of these
>  > > > > > packages
>  > > > > > (and
>  > > > > > my
>  > > > > > packager-dashboard page just hasn't caught up yet)?  Is
>  > > > > > anybody
>  > > > > > planning to do something about any of these packages before
>  > > > > > they
>  > > > > > are
>  > > > > > retired on Monday?
>  > > > > 
>  > > > > Hi,
>  > > > > 
>  > > > > I looked at the orphaned packages looking for new maintainers,
>  > > > > which affects Clojure-packages and decided to take these:
>  > > > > 
>  > > > > korkeala: spice-parent, maven-invoker, maven-invoker-plugin,
>  > > > > plexus-velocity,  maven-script-interpreter, maven-mapping,
>  > > > > weld-
>  > > > > parent,
>  > > > > aopalliance, jakarta-server-pages, javaparser, jakarta-
>  > > > > interceptors
>  > > > > 
>  > > > > these were already taken by someone else:
>  > > > > apache-ivy, jansi-native
>  > > > > 
>  > > > > Not really sure in what state these packages are, if I dont
>  > > > > have time to maintain them I'll reorphan them and orphan
>  > > > > the Clojure packages as well.
>  > > > 
>  > > > I also have the same plan (if I dont have time to maintain them
>  > > > I'll
>  > > > reorphan )
>  > > > 
>  > > > Now log4j-1.2 is required for ant and jboss-logging [1] can't we
>  > > > remove
>  > > > these dependencies on log4j-1.2 ?
>  > > 
>  > > Those packages both no longer depend on log4j12 (it might only look
>  > > that way to you because of the virtual provides; what they depend
>  > > on
>  > > is actually only log4j 2.x). I have months ago ported both ant and
>  > > jboss-logging packages to use the log4j 1.2 API shim provided by
>  > > log4j
>  > > instead of the old, deprecated, and security hole-y log4j12
>  > > package,
>  > > which is now retired in Fedora. 
>  > 
>  > Hi,
>  > https://src.fedoraproject.org/rpms/log4j12 was retired 8 months ago. 
>  > 
>  > and I confused log4j12 package with package log4j which also have
>  > 1.2-
>  > api  ! 
>  > 
>  > I took disruptor package because: "Depending on: disruptor (151),
>  > status change: 2021-04-26 (5 weeks ago)" including ant and log4j
>  > 
>  
>   
In resume, I took log4j, apache-ivy and jdependency, google-gson and
javassist, disruptor, jakarta-saaj, jakarta-xml-ws and jmock and
jctools (1)

Now, I see that shrinkwrap is needed by jboss-modules which is needed
by byteman which is needed by systemtap which is needed by almost
everything. If we can build byteman without jboss-modules, I think we
can drop jboss-modules and shrinkwrap.


(1)
Depending on: jakarta-saaj (155), status change: 2021-04-26 (5 weeks
ago)
Depending on: jakarta-xml-ws (153), status change: 2021-04-26 (5 weeks
ago)
Depending on: jmock (152), status change: 2021-04-26 (5 weeks ago)

Depending on: jctools (151), status change: 2021-04-26 (5 weeks ago)


>  > > Because I'd rather have packages use
>  > > the actually maintained, new version of log4j instead of an old and
>  > > dusty compat package.
>  > > 
>  > > Fabio
>  > > _______________________________________________
>  > > devel mailing list -- devel(a)lists.fedoraproject.org
>  > > To unsubscribe send an email to 
>  > > devel-leave(a)lists.fedoraproject.org
>  > > Fedora Code of Conduct: 
>  > > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  > > List Guidelines: 
>  > > https://fedoraproject.org/wiki/Mailing_list_guidelines
>  > > List Archives: 
>  > > https://lists.fedoraproject.org/archives/list/[e-mail]
>  > > Do not reply to spam on the list, report it: 
>  > > https://pagure.io/fedora-infrastructure
>  > 
>  > -- 
>  > Sérgio M. B.
>  > _______________________________________________
>  > devel mailing list -- devel(a)lists.fedoraproject.org
>  > To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>  > Fedora Code of Conduct: 
>  > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  > List Guidelines: 
>  > https://fedoraproject.org/wiki/Mailing_list_guidelines
>  > List Archives: 
>  > https://lists.fedoraproject.org/archives/list/[e-mail]
>  > Do not reply to spam on the list, report it: 
>  > https://pagure.io/fedora-infrastructure
>  
>  -- 
>  Sérgio M. B.
>  _______________________________________________
>  devel mailing list -- devel(a)lists.fedoraproject.org
>  To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct: 
>  https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: 
>  https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives: 
>  https://lists.fedoraproject.org/archives/list/[e-mail]
>  Do not reply to spam on the list, report it: 
>  https://pagure.io/fedora-infrastructure 
-- 
Sérgio M. B.