|
»
»
[jira] Created: (JMOCK-213) Make jMock thread-safe
|
View:
New views
7 Messages
—
Rating Filter:
Alert me
|
 |
[jira] Created: (JMOCK-213) Make jMock thread-safe
by JIRA jira@codehaus.org
::
Rate this Message:
Make jMock thread-safe
---------------------- Key: JMOCK-213 URL: http://jira.codehaus.org/browse/JMOCK-213 Project: jMock Issue Type: Improvement Components: Library Affects Versions: 2.5.1, 2.5.0, 2.5.0-RC2, 2.5.0-RC1, 2.4.0, 2.4.0-RC1, 2.3.0, 2.3.0-RC2, 2.3.0-RC1, 2.2.0, 2.2.0-RC1, 2.1.0, 2.1.0-RC5, 2.1.0-RC4, 2.1.0-RC3, 2.1.0-RC2, 2.1.0-RC1, 2.0.0, 2.0.0-RC1, 1.2.0, 1.1.0, 1.1.0-RC2, 1.1.0-RC1, 1.0.1, 1.0 Reporter: Nat Pryce Fix For: 2.7.0 The Mockery is not thread safe but people often use jMock with multithreaded code. Thread-safety can be easily implemented as a decorator that wraps the imposteriser. It can then be plugged into the Mockery when needed. The only other issue to address is that expectation failures are swallowed by background threads. Issue JMOCK-183 will address this issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
[jira] Work started: (JMOCK-213) Make jMock thread-safe
by JIRA jira@codehaus.org
::
Rate this Message:
[ http://jira.codehaus.org/browse/JMOCK-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JMOCK-213 started by Nat Pryce. > Make jMock thread-safe > ---------------------- > > Key: JMOCK-213 > URL: http://jira.codehaus.org/browse/JMOCK-213 > Project: jMock > Issue Type: Improvement > Components: Library > Affects Versions: 1.0, 1.0.1, 1.1.0-RC1, 1.1.0-RC2, 1.1.0, 1.2.0, 2.0.0-RC1, 2.0.0, 2.1.0-RC1, 2.1.0-RC2, 2.1.0-RC3, 2.1.0-RC4, 2.1.0-RC5, 2.1.0, 2.2.0-RC1, 2.2.0, 2.3.0-RC1, 2.3.0-RC2, 2.3.0, 2.4.0-RC1, 2.4.0, 2.5.0-RC1, 2.5.0-RC2, 2.5.0, 2.5.1 > Reporter: Nat Pryce > Assignee: Nat Pryce > Fix For: 2.7.0 > > > The Mockery is not thread safe but people often use jMock with multithreaded code. > Thread-safety can be easily implemented as a decorator that wraps the imposteriser. It can then be plugged into the Mockery when needed. > The only other issue to address is that expectation failures are swallowed by background threads. Issue JMOCK-183 will address this issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
[jira] Assigned: (JMOCK-213) Make jMock thread-safe
by JIRA jira@codehaus.org
::
Rate this Message:
[ http://jira.codehaus.org/browse/JMOCK-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nat Pryce reassigned JMOCK-213: ------------------------------- Assignee: Nat Pryce > Make jMock thread-safe > ---------------------- > > Key: JMOCK-213 > URL: http://jira.codehaus.org/browse/JMOCK-213 > Project: jMock > Issue Type: Improvement > Components: Library > Affects Versions: 1.0, 1.0.1, 1.1.0-RC1, 1.1.0-RC2, 1.1.0, 1.2.0, 2.0.0-RC1, 2.0.0, 2.1.0-RC1, 2.1.0-RC2, 2.1.0-RC3, 2.1.0-RC4, 2.1.0-RC5, 2.1.0, 2.2.0-RC1, 2.2.0, 2.3.0-RC1, 2.3.0-RC2, 2.3.0, 2.4.0-RC1, 2.4.0, 2.5.0-RC1, 2.5.0-RC2, 2.5.0, 2.5.1 > Reporter: Nat Pryce > Assignee: Nat Pryce > Fix For: 2.7.0 > > > The Mockery is not thread safe but people often use jMock with multithreaded code. > Thread-safety can be easily implemented as a decorator that wraps the imposteriser. It can then be plugged into the Mockery when needed. > The only other issue to address is that expectation failures are swallowed by background threads. Issue JMOCK-183 will address this issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
[jira] Work stopped: (JMOCK-213) Make jMock thread-safe
by JIRA jira@codehaus.org
::
Rate this Message:
[ http://jira.codehaus.org/browse/JMOCK-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JMOCK-213 stopped by Nat Pryce. > Make jMock thread-safe > ---------------------- > > Key: JMOCK-213 > URL: http://jira.codehaus.org/browse/JMOCK-213 > Project: jMock > Issue Type: Improvement > Components: Library > Affects Versions: 1.0, 1.0.1, 1.1.0-RC1, 1.1.0-RC2, 1.1.0, 1.2.0, 2.0.0-RC1, 2.0.0, 2.1.0-RC1, 2.1.0-RC2, 2.1.0-RC3, 2.1.0-RC4, 2.1.0-RC5, 2.1.0, 2.2.0-RC1, 2.2.0, 2.3.0-RC1, 2.3.0-RC2, 2.3.0, 2.4.0-RC1, 2.4.0, 2.5.0-RC1, 2.5.0-RC2, 2.5.0, 2.5.1 > Reporter: Nat Pryce > Assignee: Nat Pryce > Fix For: 2.7.0 > > > The Mockery is not thread safe but people often use jMock with multithreaded code. > Thread-safety can be easily implemented as a decorator that wraps the imposteriser. It can then be plugged into the Mockery when needed. > The only other issue to address is that expectation failures are swallowed by background threads. Issue JMOCK-183 will address this issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
[jira] Commented: (JMOCK-213) Make jMock thread-safe
by JIRA jira@codehaus.org
::
Rate this Message:
[ http://jira.codehaus.org/browse/JMOCK-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=167034#action_167034 ] Nat Pryce commented on JMOCK-213: --------------------------------- The Imposteriser decorator is checked into SVN. Blocked on implementation of JMOCK-183. > Make jMock thread-safe > ---------------------- > > Key: JMOCK-213 > URL: http://jira.codehaus.org/browse/JMOCK-213 > Project: jMock > Issue Type: Improvement > Components: Library > Affects Versions: 1.0, 1.0.1, 1.1.0-RC1, 1.1.0-RC2, 1.1.0, 1.2.0, 2.0.0-RC1, 2.0.0, 2.1.0-RC1, 2.1.0-RC2, 2.1.0-RC3, 2.1.0-RC4, 2.1.0-RC5, 2.1.0, 2.2.0-RC1, 2.2.0, 2.3.0-RC1, 2.3.0-RC2, 2.3.0, 2.4.0-RC1, 2.4.0, 2.5.0-RC1, 2.5.0-RC2, 2.5.0, 2.5.1 > Reporter: Nat Pryce > Assignee: Nat Pryce > Fix For: 2.7.0 > > > The Mockery is not thread safe but people often use jMock with multithreaded code. > Thread-safety can be easily implemented as a decorator that wraps the imposteriser. It can then be plugged into the Mockery when needed. > The only other issue to address is that expectation failures are swallowed by background threads. Issue JMOCK-183 will address this issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
[jira] Issue Comment Edited: (JMOCK-213) Make jMock thread-safe
by JIRA jira@codehaus.org
::
Rate this Message:
[ http://jira.codehaus.org/browse/JMOCK-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=167034#action_167034 ] Nat Pryce edited comment on JMOCK-213 at 2/25/09 2:14 PM: ---------------------------------------------------------- The Imposteriser decorator is checked into SVN. Resolution of this issue is waiting on the implementation of JMOCK-183. was (Author: npryce): The Imposteriser decorator is checked into SVN. Blocked on implementation of JMOCK-183. > Make jMock thread-safe > ---------------------- > > Key: JMOCK-213 > URL: http://jira.codehaus.org/browse/JMOCK-213 > Project: jMock > Issue Type: Improvement > Components: Library > Affects Versions: 1.0, 1.0.1, 1.1.0-RC1, 1.1.0-RC2, 1.1.0, 1.2.0, 2.0.0-RC1, 2.0.0, 2.1.0-RC1, 2.1.0-RC2, 2.1.0-RC3, 2.1.0-RC4, 2.1.0-RC5, 2.1.0, 2.2.0-RC1, 2.2.0, 2.3.0-RC1, 2.3.0-RC2, 2.3.0, 2.4.0-RC1, 2.4.0, 2.5.0-RC1, 2.5.0-RC2, 2.5.0, 2.5.1 > Reporter: Nat Pryce > Assignee: Nat Pryce > Fix For: 2.7.0 > > > The Mockery is not thread safe but people often use jMock with multithreaded code. > Thread-safety can be easily implemented as a decorator that wraps the imposteriser. It can then be plugged into the Mockery when needed. > The only other issue to address is that expectation failures are swallowed by background threads. Issue JMOCK-183 will address this issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
[jira] Resolved: (JMOCK-213) Make jMock thread-safe
by JIRA jira@codehaus.org
::
Rate this Message:
[ http://jira.codehaus.org/browse/JMOCK-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nat Pryce resolved JMOCK-213. ----------------------------- Resolution: Fixed Implemented in SVN trunk > Make jMock thread-safe > ---------------------- > > Key: JMOCK-213 > URL: http://jira.codehaus.org/browse/JMOCK-213 > Project: jMock > Issue Type: Improvement > Components: Library > Affects Versions: 1.0, 1.0.1, 1.1.0-RC1, 1.1.0-RC2, 1.1.0, 1.2.0, 2.0.0-RC1, 2.0.0, 2.1.0-RC1, 2.1.0-RC2, 2.1.0-RC3, 2.1.0-RC4, 2.1.0-RC5, 2.1.0, 2.2.0-RC1, 2.2.0, 2.3.0-RC1, 2.3.0-RC2, 2.3.0, 2.4.0-RC1, 2.4.0, 2.5.0-RC1, 2.5.0-RC2, 2.5.0, 2.5.1 > Reporter: Nat Pryce > Assignee: Nat Pryce > Fix For: 2.7.0 > > > The Mockery is not thread safe but people often use jMock with multithreaded code. > Thread-safety can be easily implemented as a decorator that wraps the imposteriser. It can then be plugged into the Mockery when needed. > The only other issue to address is that expectation failures are swallowed by background threads. Issue JMOCK-183 will address this issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
| Free embeddable forum powered by Nabble | Forum Help |
