jaxen

Jeff Thompson

unread,

Mar 7, 2019, 5:36:43 PM3/7/19

to JenkinsCI Developers

Recently while looking to clean up something else I ran across a Jenkins specific fork of the jaxen library. The fork is at https://github.com/jenkinsci/jaxen

I haven’t been able to detect any changes in the Jenkins fork. Indeed, the last commit in the fork seems to match perfectly to this commit in the official repository: https://github.com/jaxen-xpath/jaxen/commit/b08dc0a896a3712f636202e020bfcfa98ece4fb7

I also cannot find any uses of the fork in Jenkins. The version in the fork is the same as the latest standard published one. Most dependency references in the Jenkins ecosystem are actually to older versions. (That’s another issue.)

I propose to archive or delete the fork from the Jenkins organization to clean things up.

Any concerns or agreement?

Jeff Thompson

R. Tyler Croy

unread,

Mar 7, 2019, 6:58:29 PM3/7/19

to Jeff Thompson, JenkinsCI Developers

Archival in GitHub sounds reasonable to me, I presume we won't do anything in
Artifactory?

If everybody's fine with this, either an Infra ticket, or one of the other
github admins can take care of this easily.

--
GitHub: https://github.com/rtyler

GPG Key ID: 0F2298A980EE31ACCA0A7825E5C92681BEF6CEA2

signature.asc

Jeff Thompson

unread,

Mar 7, 2019, 7:03:58 PM3/7/19

to JenkinsCI Developers

Yes, that’s my proposal.

Jeff

Daniel Beck

unread,

Mar 8, 2019, 4:08:53 AM3/8/19

to jenkin...@googlegroups.com

Done.

> --
> 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 on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/4BF6F506-DEAC-4BA3-9407-A8CBBD76F426%40cloudbees.com.
> For more options, visit https://groups.google.com/d/optout.

Reply all

Reply to author

Forward