Re: Regression after jpackage+1-49 update

2019-10-08 Thread Brent Christian
On 10/7/19 1:12 AM, Alan Bateman wrote: On 7/10/2019 4:43 pm, Alan Bateman wrote: On 07/10/2019 04:35, David Holmes wrote: You can temporarily workaround with -XX:+ClassForNameDeferLinking, but your code needs to be updated to deal with LinkageErrors from Class.forName. >>> I suspect

Re: Regression after jpackage+1-49 update

2019-10-08 Thread Alexey Semenyuk
On 10/8/2019 1:53 PM, Sverre Moe wrote: tir. 8. okt. 2019 kl. 19:19 skrev Alexey Semenyuk mailto:alexey.semen...@oracle.com>>: On 10/8/2019 12:43 PM, Sverre Moe wrote: > Some comments about the jpackage+1-49 update. > > 1) It has become a lot more verbose since

Re: Regression after jpackage+1-49 update

2019-10-08 Thread Sverre Moe
tir. 8. okt. 2019 kl. 19:19 skrev Alexey Semenyuk < alexey.semen...@oracle.com>: > > > On 10/8/2019 12:43 PM, Sverre Moe wrote: > > Some comments about the jpackage+1-49 update. > > > > 1) It has become a lot more verbose since jpackage+1-35. Makes using the > > verbose argument difficult to

Re: Regression after jpackage+1-49 update

2019-10-08 Thread Alexey Semenyuk
On 10/8/2019 12:43 PM, Sverre Moe wrote: Some comments about the jpackage+1-49 update. 1) It has become a lot more verbose since jpackage+1-35. Makes using the verbose argument difficult to actually see relevant output, like the actual rpmbuild/dpkg command output. It seems to be running

Re: Regression after jpackage+1-49 update

2019-10-08 Thread Sverre Moe
Some comments about the jpackage+1-49 update. 1) It has become a lot more verbose since jpackage+1-35. Makes using the verbose argument difficult to actually see relevant output, like the actual rpmbuild/dpkg command output. It seems to be running rpmbuild --version twice Running [rpmbuild

Re: Regression after jpackage+1-49 update

2019-10-07 Thread Alan Bateman
On 07/10/2019 08:00, David Holmes wrote: On 7/10/2019 4:43 pm, Alan Bateman wrote: On 07/10/2019 04:35, David Holmes wrote: Nothing to do with jpackage but a fix to Class.forName to ensure classes are linked as per the specification of forName. You can temporarily workaround with

Re: Regression after jpackage+1-49 update

2019-10-07 Thread David Holmes
On 7/10/2019 4:43 pm, Alan Bateman wrote: On 07/10/2019 04:35, David Holmes wrote: Nothing to do with jpackage but a fix to Class.forName to ensure classes are linked as per the specification of forName. You can temporarily workaround with -XX:+ClassForNameDeferLinking, but your code needs

Re: Regression after jpackage+1-49 update

2019-10-07 Thread Alan Bateman
On 07/10/2019 04:35, David Holmes wrote: Nothing to do with jpackage but a fix to Class.forName to ensure classes are linked as per the specification of forName. You can temporarily workaround with -XX:+ClassForNameDeferLinking, but your code needs to be updated to deal with LinkageErrors

Re: Regression after jpackage+1-49 update

2019-10-06 Thread David Holmes
Hi, On 7/10/2019 1:21 am, Tornai András wrote: Hello, After I updated my project from jpackage+1-35 to the latest jpackage+1-49 I noticed that Java now throws NoClassDefFoundError while this was not the case before. Nothing to do with jpackage but a fix to Class.forName to ensure classes

Regression after jpackage+1-49 update

2019-10-06 Thread Tornai András
Hello, After I updated my project from jpackage+1-35 to the latest jpackage+1-49 I noticed that Java now throws NoClassDefFoundError while this was not the case before. Repro case: import java.lang.reflect.Field; import java.util.Optional; public class Main { private Optional service;