#2257 Change default stream for maven module
Closed: Rejected 4 years ago by zbyszek. Opened 4 years ago by mizdebsk.

Please allow changing default stream of "maven" module from "3.5" to "3.6" in Fedora 32.

The list of SRPM components in the module:

  • aopalliance
  • apache-commons-cli
  • apache-commons-codec
  • apache-commons-io
  • apache-commons-lang3
  • atinject
  • cdi-api
  • geronimo-annotation
  • google-guice
  • guava
  • hawtjni
  • httpcomponents-client
  • httpcomponents-core
  • jansi
  • jansi-native
  • jsoup
  • jsr-305
  • maven
  • maven-resolver
  • maven-shared-utils
  • maven-wagon
  • plexus-cipher
  • plexus-classworlds
  • plexus-containers
  • plexus-interpolation
  • plexus-sec-dispatcher
  • plexus-utils
  • sisu
  • slf4j

Whether the contents of this module will obsolete and replace non-modular RPMs:

  • yes

Which releases of Fedora will this new default apply to

  • Fedora 32

Whether the contents of this module will obsolete and replace non-modular RPMs: yes

How exactly?

Anyway, FESCo approval is AFAIK not required when changing one default for another. Is the existing default stream to be kept in Fedora 32 as an alternate stream?

Whether the contents of this module will obsolete and replace non-modular RPMs: yes

How exactly?

For now contents of maven:3.6 module will keep shadowing corresponding ursine packages, just like maven:3.5 module contents are shadowing them. There is ongoing work to have Maven modules parallel-installable with ursine packages, but this work is blocked on infrastructure changes.

Anyway, FESCo approval is AFAIK not required when changing one default for another.

According to modularity docs changing default stream requires FESCo approval, hence this ticket.

Is the existing default stream to be kept in Fedora 32 as an alternate stream?

Yes, maven:3.5 stream will still be available and it will follow lifecycle of corresponding module in Red Hat Enterprise Linux 8 - it will be maintained until May 2022.

+1 for this change. maven was updated in rawhide to 3.6 anyway.

Assuming the main difference between 3.5 and 3.6 maven stream is indeed the maven version and not some hidden surprise, like the OpenJDK version.

Assuming the main difference between 3.5 and 3.6 maven stream is indeed the maven version and not some hidden surprise, like the OpenJDK version.

The main difference is of course different minor Maven version, however there are other differences too, notably:

  • maven:3.6 will be built using OpenJDK 11 while maven:3.5 is built with OpenJDK 8 and
  • maven:3.6 is planned to be parallel-installable with ursine packages, if required infrastructure changes are applied in time
  • some libraries included in maven:3.6 will have different versions from maven:3.5

maven:3.6 will be built using OpenJDK 11 while maven:3.5 is built with OpenJDK 8 and

I don't understand all the implications here. See also https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/UVNYMUZPA3XC3TZRDUUGFXQBC4ZHUHOC/

Could you please elaborate on that?

I am not sure if this really requires voting since there is already a default stream. I must note that we have a problem with switching defaults (hello libgit2), but nevertheless I'm +1 on this.

I'm putting this on the meeting agenda for next week.

Metadata Update from @sgallagh:
- Issue tagged with: meeting

4 years ago

Technically, this will be approved in 4 days. Do we want to postpone that for the next meeting?

I'm going to be -1 on any new default streams right now while we sort out how we're moving forward in issue #2255

  • AGREED: Change default stream for maven module: defer the decision
    until we sort out the default modular streams strategy (+8,0,-0)
    (jforbes, 15:11:11)

Metadata Update from @jforbes:
- Issue untagged with: meeting

4 years ago

FTR, Eclipse would like 3.6 to be the default maven in future Fedora releases too.

FTR2, maven 3.6 is already available in non-modular fedora 32.

FTR, Eclipse would like 3.6 to be the default maven in future Fedora releases too.

What do you mean by that? Maven releases maybe once yearly or so. Are we supposed to block the version update in the future more then we do usually (i.e. to give a heads ups and coordinate any required fixes)?

FTR, Eclipse would like 3.6 to be the default maven in future Fedora releases too.

What do you mean by that? Maven releases maybe once yearly or so. Are we supposed to block the version update in the future more then we do usually (i.e. to give a heads ups and coordinate any required fixes)?

No, I'm not proposing anything other than simply switching Eclipse's requirement from 3.5 to 3.6 (The dependency exists solely to allow Eclipse users to work on maven-based projects. I obviously want my users to have access to the current release of maven.)

It is my understanding that default streams cannot depend on non-default streams, or do I misunderstand?

FTR2, maven 3.6 is already available in non-modular fedora 32.

Since maven is a default module, modular version is what users will get when they install it, no?

FTR2, maven 3.6 is already available in non-modular fedora 32.

Since maven is a default module, modular version is what users will get when they install it, no?

Correct (except for users like me, who disable the modular repos).
Maybe maven should not have a default stream on fedora 32?

Metadata Update from @churchyard:
- Issue tagged with: F32

4 years ago

Metadata Update from @churchyard:
- Issue tagged with: stalled

4 years ago

With #2341, this become moot. No default stream => no default stream change.

Metadata Update from @zbyszek:
- Issue close_status updated to: Rejected
- Issue status updated to: Closed (was: Open)

4 years ago

Metadata Update from @zbyszek:
- Issue untagged with: stalled

4 years ago

Metadata Update from @bcotton:
- Issue untagged with: F32
- Issue set to the milestone: Fedora 32

3 years ago

Log in to comment on this ticket.

Metadata