Consider making repo read only (archived now)
hazendaz opened this issue · 0 comments
Given last commit in 2020, then in 2022, I started releasing from the fork to take over maintenance, and finally a year or more later still no activity here, I've started more formally doing long overdue automation and don't see my code efforts coming back up to this original repo. Marking it archived makes sense for a number of reasons beyond what I mentioned especially considering original direction here had stated at one point that junit 5 would make this obsolete. It doesn't entirely but focus I'm sure is elsewhere. Most of what I'm doing post today anyways makes it far harder to just accept back up and its already 4 years since release here. Doing so will help those trying to use know where to use it from.
https://github.com/hazendaz/catch-exception is the fork I've been running it from and branch is 'master-fork'. My last efforts to bring code in where on master and never got merged and I closed some time ago. While I know github can shift ownership, that would cause more work so I think this is the right path. As it were, all credit and licensing remains as it were and much appreciated for this great project.