Hi Kedar,
Sounds great!
Maybe the subject you listen for is better to be "new bug" (not to
accidently file bug report in case someone starts his subject with "bug".)
Then we could mail them here with subject "new bug : [bug issue]".
The reply sent to the list by Tb/java.net could then have as subject : bug
[bug nr] : [bug issue],
effectively adding all Re's : [bug nr] : [bug issue], to the same bug
report.
Just and idea, but thanks a lot for considering this,
Wim
-----Original Message-----
From: Kedar.Mhaswade_at_Sun.COM [mailto:Kedar.Mhaswade_at_Sun.COM]
Sent: donderdag 21 augustus 2008 20:40
To: quality_at_glassfish.dev.java.net
Subject: Re: First bugs ? & how to file bugs
Wim Verreycken wrote:
> Hi Jerome,
>
> Adam Bien wrote:
>> Should we file the bugs somewhere else, or posting to this list is
>> sufficient?
>
> I'd love if it where sufficient to just post them here.
> Just an idea, but maybe you guys could write some service monitorring this
> list like :
> If (subject startswith "bug")
> File new bug report;
> Reply to quality@... with bug report;
>
> Imho it would speed things up tremendously.
> Or am I the only one who doesn't like web interface bug report filing?
>
> Sorry for my lazy attitude. But it'll never change :)
I like this attitude ;).
Let me see if I can write a Thunderbird addon to achieve what
you want. It's an excellent idea. It will be a combo of Tb addon
and java.net gimmicks. (I will go to Kohsuke for help).
The only problem is defaulting the values for various fields on a bug
report. As a bug reporter, I guess, you need to do some due diligence
in the "follow-up", which probably can't be automated.
-Kedar
>
> Wim
> -----Original Message-----
> From: Jerome.Dochez_at_Sun.COM [mailto:Jerome.Dochez_at_Sun.COM]
> Sent: donderdag 21 augustus 2008 18:17
> To: quality_at_glassfish.dev.java.net
> Subject: Re: First bugs ?
>
> Hi Wim
>
> Thanks for taking the time to write issues, find my answers inline
>
> jerome
>
> Wim Verreycken wrote:
>> Found two bugs in v3tp2.
>>
>> 1) Grizzlyproxy bug?
>>
>> When starting v3tp2 there no check if the ports specified in server.xml
> are
>> already in use. Server starts with no errors being thrown (whereas v2ur2
>> will correctly state " Domain domain1 failed to startup. There is a
> conflict
>> on port 8080. Please check the server log for more details.)
>> While updating might wanna check also if there are no port conflict on
any
>> of the other ports - v2ur2 only complains about port 8080, while actually
>> all ports needed (4848, 8181 and 8686 are in already in use)
>>
> yes, we have changed this, now the server will shutdown if ports cannot
> be opened successfully.
>> 2) context root on port 4848?
>>
>> context root for admin console should be / on port 4848, whereas in v3tp2
>> one would have to specify /admin in the url.
>>
> I believe Kedar will have that supported in b21.
>> As I said these exist in v3tp2. Will only file bug report if exists in
>> nightly build / build from trunk. No time today though. Maybe someone
else
>> cares to check already ? (-> survivant , your build should be finished by
>> now? ;)
>>
>> Wim
>>
>> -----Original Message-----
>> From: Survivant 00 [mailto:survivant00_at_gmail.com]
>> Sent: donderdag 21 augustus 2008 15:45
>> To: quality_at_glassfish.dev.java.net
>> Subject: Re: where are the v3 prelude nightly builds ?
>>
>> good question.
>>
>> now I'm building it myself from the trunk. take 15 min to build.
>>
>> mvn -U -cpu clean install
>> 2008/8/21 Wim Verreycken <wim_at_pizzastop.be>
>> Thanks,
>>
>>
>> Wim
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: quality-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: quality-help_at_glassfish.dev.java.net
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: quality-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: quality-help_at_glassfish.dev.java.net
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: quality-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: quality-help_at_glassfish.dev.java.net
>
---------------------------------------------------------------------
To unsubscribe, e-mail: quality-unsubscribe_at_glassfish.dev.java.net
For additional commands, e-mail: quality-help_at_glassfish.dev.java.net