Closed ChristianCiach closed 5 years ago
Ok, you now deserve being featured under the 'Attribution' section of the README...
So after this is fixed do you recommend releasing 1.4.3 or wait for something bigger?
So after this is fixed do you recommend releasing 1.4.3 or wait for something bigger?
I would like to see a 1.4.3 soon after this is fixed, just so that I can remove my current workaround :) As they say: release early, release often. (I don't know if this fits here, but I wanted to say something clever).
Ok I have your back. I used to feel like I use up space on Maven's servers but I shouldn't care much anyway.
That is very considerate of you, and I am the same kind of person. But update4j is auch a tiny library compared to almost anything else, that I agree that you shouldn't care much :)
Have a nice weekend!
Give it a try and report back. Will release tomorrow.
Just by reviewing the code I am sure that the fix is correct. I feel a bit sick, so I probably won't try out the snapshot today or tomorrow.
Thanks for the attribution! It makes me wonder how many people actually use update4j in production. I would have expected for update4j to become very popular, now that Webstart is dead and the alternative libraries are quite lacking.
Metrics are not super high, but I see about 150-200 unique visitors bi-weekly. I'm lacking the proper digital marketing strategies to push this forward. I know at-least one publicly available application that uses it—MuseIDE.
Interesting! Our application is not publicly available. We are using update4j to update the rich-client of our Virtual Power Plant until we've finished the migration to a web application.
Thanks again. I can confirm that the fix works.
Thanks for reporting back!
@ChristianCiach Can you please refer this project to your friends/co-workers? I'd like to see this get more popular.
Well, yeah, all my coworkers already know about update4j because I did an in-depth presentation about how the updater works. Other than that, I don't have contacts to any other Java developers :p
Using update4j 1.4.2, I just got this error message when downloading a jar file:
When looking at the module using jmod, we are seeing this:
The important line here is
requires jdk.jfr static
. As we can see, it is a "static" requirement. According to this article, "requires static" is used for compile-only dependencies:So, I think update4j should not throw an exception in cases like these.