RE: [jira] Updated: (LANG-356) Add getStartTime to StopWatch

2007-10-10 Thread Gary Gregory
Works like I charm. I was able to 'Assign' to myself and 'Resolve'. Thank you Henri Gary > -Original Message- > From: Henri Yandell [mailto:[EMAIL PROTECTED] > Sent: Wednesday, October 10, 2007 4:47 PM > To: Jakarta Commons Developers List > Subject: Re: [jira] Updated: (LANG-356) Add get

Re: [jira] Updated: (LANG-356) Add getStartTime to StopWatch

2007-10-10 Thread Henri Yandell
I've added [EMAIL PROTECTED] to Commons Developers (it already had Jakarta Developers). Let me know if you use ggregory instead. Hen On 10/10/07, Rahul Akolkar <[EMAIL PROTECTED]> wrote: > Indeed, then we need a JIRA admin to help with this (theres atleast a > couple on this list). > > -Rahul >

Re: [jira] Updated: (LANG-356) Add getStartTime to StopWatch

2007-10-10 Thread Rahul Akolkar
Indeed, then we need a JIRA admin to help with this (theres atleast a couple on this list). -Rahul On 10/10/07, Gary Gregory <[EMAIL PROTECTED]> wrote: > Nope, this is what I have: > > Attach file to this issue > Attach screenshot to this issue > Clone this issue > Comment on this issue > Create

RE: [jira] Updated: (LANG-356) Add getStartTime to StopWatch

2007-10-10 Thread Gary Gregory
Nope, this is what I have: Attach file to this issue Attach screenshot to this issue Clone this issue Comment on this issue Create sub-task Edit this issue Link this issue to another issue Convert to sub-task Voting: You have not voted for this issue. Vote for it if you wish it to be fixed Watchin

Re: [jira] Updated: (LANG-356) Add getStartTime to StopWatch

2007-10-10 Thread Rahul Akolkar
On 10/10/07, Gary Gregory <[EMAIL PROTECTED]> wrote: > SVN is fine. I am talking about use JIRA to set the state of the ticket as > "Checked in" or "Fixed". At least that's how it works in our company's JIRA > set up. > Do you see Workflow Actions such as "Resolve Issue" or "Close Issue"? -Rah

RE: [jira] Updated: (LANG-356) Add getStartTime to StopWatch

2007-10-10 Thread Gary Gregory
SVN is fine. I am talking about use JIRA to set the state of the ticket as "Checked in" or "Fixed". At least that's how it works in our company's JIRA set up. Thank you, Gary > -Original Message- > From: Rahul Akolkar [mailto:[EMAIL PROTECTED] > Sent: Wednesday, October 10, 2007 1:51 PM

Re: [jira] Updated: (LANG-356) Add getStartTime to StopWatch

2007-10-10 Thread Rahul Akolkar
On 10/10/07, Gary Gregory <[EMAIL PROTECTED]> wrote: > Odd, I just committed for LANG-256 and it seems my account is not set up for > JIRA check-ins. > > Who do I ask for check in rights? > Not sure what you mean. I did notice a lag in the svn commit messages making it to the commits list today

RE: [jira] Updated: (LANG-356) Add getStartTime to StopWatch

2007-10-10 Thread Gary Gregory
Odd, I just committed for LANG-256 and it seems my account is not set up for JIRA check-ins. Who do I ask for check in rights? Thank you, Gary > -Original Message- > From: Gary Gregory (JIRA) [mailto:[EMAIL PROTECTED] > Sent: Wednesday, October 10, 2007 1:30 PM > To: [EMAIL PROTECTED] >

Re: [logging] 1.1.1 release

2007-10-10 Thread simon
Hi Dennis, No it's not in JIRA (slack of me I know). Interesting, it appears to only be a problem on Linux then. I have to face the fact that I'm not likely to find time to investigate further anytime soon. I do think it's just a unit test issue rather than a real problem, and the fact that it w

Re: [jira] Updated: (CODEC-55) make all "business" method implementations of public API thread safe

2007-10-10 Thread sebb
Thanks. I stand corrected. Or rather, I'm still sitting down, trying to take this all in ;-) I had assumed that constructors effectively synchronized the construction process, but obviously not ... S On 10/10/2007, Will Pugh <[EMAIL PROTECTED]> wrote: > Err. I mean JSR-133. > >--Will > > W

Re: [jira] Updated: (CODEC-55) make all "business" method implementations of public API thread safe

2007-10-10 Thread Will Pugh
Err. I mean JSR-133. --Will Will Pugh wrote: Look at JSR 166 section 3.5. sebb wrote: On 10/10/2007, Will Pugh (JIRA) <[EMAIL PROTECTED]> wrote: [ https://issues.apache.org/jira/browse/CODEC-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Will Pugh updat

Re: [jira] Updated: (CODEC-55) make all "business" method implementations of public API thread safe

2007-10-10 Thread Will Pugh
Look at JSR 166 section 3.5. sebb wrote: On 10/10/2007, Will Pugh (JIRA) <[EMAIL PROTECTED]> wrote: [ https://issues.apache.org/jira/browse/CODEC-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Will Pugh updated CODEC-55: --- ...

Re: [jira] Updated: (CODEC-55) make all "business" method implementations of public API thread safe

2007-10-10 Thread sebb
On 10/10/2007, Will Pugh (JIRA) <[EMAIL PROTECTED]> wrote: > > [ > https://issues.apache.org/jira/browse/CODEC-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Will Pugh updated CODEC-55: > --- > ... > The current problem is that the end of

[EMAIL PROTECTED]: Project commons-jelly-tags-jaxme (in module commons-jelly) failed

2007-10-10 Thread commons-jelly-tags-jaxme development
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-jelly-tags-jaxme has an issue affecting its community integration. This

[EMAIL PROTECTED]: Project commons-jelly-tags-jsl-test (in module commons-jelly) failed

2007-10-10 Thread commons-jelly-tags-jsl development
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-jelly-tags-jsl-test has an issue affecting its community integration. Th