> And commons-lang3 uses different packages than commons-lang (version2) so we need both plugins
It's normal for major semver-sioned libraries to be incompatible in some way (e.g. in the package name). Usually, when new major release is released, the child projects should move to that version gradually and in case a bugfix is needed, it's just released from the same repository under respective verison. Just making sure, if that was a conscious decision to support 2 (and 3 if I create lang4) major releases instead of having them in one commons-lang that would just publish respective sem versions? Am I guessing correctly that this is in order to simplify the plugin release process (even though not following normal semver repository practices)? On the other hand, I see that https://github.com/jenkinsci/commons-lang-api-plugin has no activity at all, so I'm wondering if that should not be archived in favor of commons-lang3-api-plugin? I see that only lang3 is used in the bom <https://github.com/jenkinsci/bom/blob/master/bom-weekly/pom.xml#L278>. On Friday, 23 May 2025 at 14:56:43 UTC+2 m.wi...@sap.com wrote: > What you link is commons-collections4 that is not related to commons-lang3 > And commons-lang3 uses different packages than commons-lang (version2) so > we need both plugins > > Feel free to create a wrapper plugin for commons.collections4, there are a > few plugins that use commons.collections4 so they could benefit as well > > > ------------------------------ > *From:* jenkin...@googlegroups.com <jenkin...@googlegroups.com> on behalf > of Radek Antoniuk <radek.a...@gmail.com> > *Sent:* Friday, May 23, 2025 11:21 AM > *To:* Jenkins Developers <jenkin...@googlegroups.com> > *Subject:* commons 4 api plugin > > Hi, > > Jenkins currently has > https://github.com/jenkinsci/commons-lang3-api-plugin but there are some > useful > methods added in 4.x that I'd like to use > <https://commons.apache.org/proper/commons-collections/javadocs/api-4.2/org/apache/commons/collections4/ListUtils.html> > . > Is there any plan to create a new plugin version of this or should I go > ahead..? > Was there any reason the current plugin was called lang3 instead of just > lang and following the semver accordingly? > > Cheers, > Radek > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-de...@googlegroups.com. > To view this discussion visit > https://groups.google.com/d/msgid/jenkinsci-dev/4203a578-8cf5-4aec-9890-22f03fd6eeabn%40googlegroups.com > > <https://groups.google.com/d/msgid/jenkinsci-dev/4203a578-8cf5-4aec-9890-22f03fd6eeabn%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/jenkinsci-dev/5f09669c-c2a2-4685-aa86-aa7276e4938an%40googlegroups.com.