incubator-yoko-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <j...@apache.org>
Subject [jira] Commented: (YOKO-33) RMI/IIOP implementation
Date Sat, 14 Oct 2006 02:49:17 GMT
    [ http://issues.apache.org/jira/browse/YOKO-33?page=comments#action_12442171 ] 
            
Daniel Kulp commented on YOKO-33:
---------------------------------


   [[ Old comment, sent by email on Tue, 11 Jul 2006 07:52:41 -0400 ]]

Umm.... should a jira issue be marked closed if there are no unit tests?   
Without tests, how do you know the jira is really fixed/closed?

At the very least, a new jira issue should be opened to track the fact that 
tests are completely missing.   However, I would say the original jira issue 
remains open until test coverage is "satisfactory".  (definition open to 
interpretation)    Basically, add a comment saying "source patch applied, 
unit tests required" or similar.

Dan



-- 
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727    C: 508-380-7194   F:781-902-8001
daniel.kulp@iona.com


> RMI/IIOP implementation
> -----------------------
>
>                 Key: YOKO-33
>                 URL: http://issues.apache.org/jira/browse/YOKO-33
>             Project: Yoko - CORBA Server
>          Issue Type: Bug
>            Reporter: Kresten Krab Thorup
>         Assigned To: Anders Hessellund Jensen
>         Attachments: trifork-rmiiiop.tgz
>
>
> The attached tgz includes Triforks rmi/iiop implementation, which may be used as a starting
point for the Yoko projects's implementation hereof.  The code doesn't compile as it is ripped
right out of the Trifork T4 application server.  (follow up email coming up)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message