[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openjdk-openjfx-dev
Subject:    Reporting javafx bugs while working on commercial app
From:       steve.x.northover () oracle ! com (steve ! x ! northover at oracle ! com)
Date:       2012-06-25 21:15:13
Message-ID: 4FE8D4E1.4010707 () oracle ! com
[Download RAW message or body]

This is common practice.  A simpler case will often find the bug for you 
when it happen to be in your code.

Steve

On 25/06/2012 3:43 PM, John Hendrikx wrote:
> I think you expect too much.  Reduce your bug to a simple test program 
> like everybody else is doing, and post that.  This saves time for the 
> JFX developers which they'll need to actually get bugs fixed.  Remote 
> debugging some big commercial app should be a last resort -- chances 
> are it is not even a JFX bug.
>
> On 25/06/2012 20:40, Pedro Duque Vieira wrote:
>> Hi,
>>
>> I have a problem reporting javafx bugs, the problem is I'm working on a
>> commercial app so I can't post the code out to the public on Jira. Is 
>> there
>> a way for me to post my code to the javafx team and be certain it will
>> remain private and won't be re-used by anyone?
>>
>> Recently I posted a bug on jira but the small code snipped I posted 
>> didn't
>> seem to trigger the bug. I suggested to the javafx developer that I 
>> could
>> send him the jar file and he could remote debug the app, I also asked 
>> what
>> else could I do, but after that I got no answer back and the bug was 
>> simply
>> closed. The point is, is there some other way/procedure to report a bug
>> when dealing with commercial apps?
>>
>> Thanks, best regards,
>>
>

[prev in list] [next in list] [prev in thread] [next in thread]