Well, I'm planning to develop a software similar to 7zip. Common Compress
is the best choice for all foundations, but not all places satisfy me, so
it's necessary to maintain my own fork.
Of course, now I want it to be an attempt at the same time. After I finish
it further, and get some user
> Oh, sorry, I don't have that idea. In the plan, I will maintain
> this fork for a long time.
Just from a users perspective: Such projects often tend to slowly dying
over the time even if single developers are enthusiastic at first place.
So you should really consider if it would be more
Thank you for your reply.
My original idea was that I, as its user, encountered problems and tried to
solve them myself. I wanted to find other users with the same problems to
communicate.
Since I didn't want to give it directly to the upstream as a PR, I didn't
bother the developer mailing list.
Le sam. 12 févr. 2022 à 16:01, Glavo a écrit :
>
> >
> > Then, what's the purpose of your message to this ML?
> >
>
> My objective is to see if anyone else wants Common Compress to work with
> JPMS.
A worthy objective IMHO, and indispensable in the mid-term AFAIK.
>
> If this is not the right
>
> Then, what's the purpose of your message to this ML?
>
My objective is to see if anyone else wants Common Compress to work with
JPMS.
If this is not the right place to talk about this, I apologize for it.
Gilles Sadowski 于2022年2月12日周六 22:50写道：
> Le sam. 12 févr. 2022 à 15:27, Glavo a
Le sam. 12 févr. 2022 à 15:27, Glavo a écrit :
>
> Oh, sorry, I don't have that idea.
Then, what's the purpose of your message to this ML?
> In the plan, I will maintain this fork
> for a long time.
>
> The reason for branching it is, on the one hand, to modularize, and on the
> other hand, to
Oh, sorry, I don't have that idea. In the plan, I will maintain this fork
for a long time.
The reason for branching it is, on the one hand, to modularize, and on the
other hand, to abandon some compatibility baggage, so that it is easier to
use in the new version of JDK.
For example, I deleted
Hello.
Le sam. 12 févr. 2022 à 10:08, Glavo a écrit :
>
> I maintained a fork based on Common Compress, fully adapted to JPMS, and
> improved the support for NIO2 path API.
> All the archivers and compressors are split into separate modules. Its core
> module is less than 90KB, and you can
I maintained a fork based on Common Compress, fully adapted to JPMS, and
improved the support for NIO2 path API.
All the archivers and compressors are split into separate modules. Its core
module is less than 90KB, and you can choose to add optional components
freely.
Because some APIs are not
