Re: [oi-dev] What to do with #4075?
Hi Small fact about these cases in Java. It is actually quite common for Javabindings to distribute their shared object files for multiple platforms within the jar. I know OpenGL bindings do so. So if you leave them out the jar would just unpack them again and maybe even fail with permission denied or worse when launching (Depending how intelligent the libraries unpack routine is.) At it would result in leftover files after deinstallation. I favour leaving them in. Greetings Toast On 9/10/18 9:29 AM, Carsten Grzemba wrote: > > > On 08.09.18 20:22, *Andreas Wacknitz * wrote: >> >> Hi, >> >> #4075 is stalled for some time now. It won't publish in its current >> state because of the jansi-native files from other OS's. >> I don't know whether removing them will be enough and the jansi plugin >> will be sufficient. As I don't use maven I don't >> have that much knowledge. Maybe we should update to the latest version >> in the 3.2 branch which does not use jansi-native I guess. >> As Olaf doesn't seem to be interested anymore I am willing to close >> this PR. What do you think? >> > Shortly I used mavem on Joyents Java VM image which also provide the > linux, freebsd and OSX libs only. I guess these are useless, but I > havn't seen any issuses. > So, simply remove libjansi.so files, keep the README.txt only.? > The native code is packaged in the jansi.jar file anyway. > > Carsten > > ___ > oi-dev mailing list > oi-dev@openindiana.org > https://openindiana.org/mailman/listinfo/oi-dev > ___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] What to do with #4075?
On 08.09.18 20:22, Andreas Wacknitz wrote: > > > > > > > Hi, > > #4075 is stalled for some time now. It won't publish in its current state > because of the jansi-native files from other OS's. > I don't know whether removing them will be enough and the jansi plugin will > be sufficient. As I don't use maven I don't > have that much knowledge. Maybe we should update to the latest version in > the 3.2 branch which does not use jansi-native I guess. > As Olaf doesn't seem to be interested anymore I am willing to close this PR. > What do you think? > > > Shortly I used mavem on Joyents Java VM image which also provide the linux, freebsd and OSX libs only. I guess these are useless, but I havn't seen any issuses. So, simply remove libjansi.so files, keep the README.txt only.? The native code is packaged in the jansi.jar file anyway. Carsten ___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev
[oi-dev] What to do with #4075?
Hi, #4075 is stalled for some time now. It won't publish in its current state because of the jansi-native files from other OS's. I don't know whether removing them will be enough and the jansi plugin will be sufficient. As I don't use maven I don't have that much knowledge. Maybe we should update to the latest version in the 3.2 branch which does not use jansi-native I guess. As Olaf doesn't seem to be interested anymore I am willing to close this PR. What do you think? Regards Andreas ___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev
