-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Available as artifact? #22
Comments
Sorry I missed this - wasn't subscribed to notifications on the repo. Not yet, no, although I did kind-of prepare to do so. Would prefer not to maintain a fork though :-/ Which fix/tweak are you looking for? |
In any case, I am in a position where I could release this pretty easily. I'm more motivated to do so if it would be useful to, and trusted by others. |
is there any plan to release? I'd be happy to use fork. |
Hi @bilak - are there particular (unreleased?) fixes you are looking for in particular? |
we are migrating to java 17 and I've seen some issues that should be resolved? So I'd be happy to test it with java upgrade. |
Fair enough. IIRC some of the tweaks made yet not released made it a bit easier to find the place you might be depending on JVM internals (by reducing noise from statics) and resolved a few common ones by adding some more fast cloners to avoid having to do so yourself, but depending on how you are using the Cloner may not resolve all your issues, so temper expectations :) |
Are you planning on releasing 1.11? |
@fatom98 here is published version https://github.com/aem-design/cloning and https://search.maven.org/artifact/design.aem/cloning/1.11.1/jar. |
Cool @brsmxq - thanks for taking this forward further! Hadn't got around to it. I am happy to coalesce around your fork, hope the cleanups and GH actions work I had done was useful! |
Hi. Have you uploaded a release of this fork as an artifact anywhere?
The text was updated successfully, but these errors were encountered: