Hi Felipe, > -----Original Message----- > From: Felipe Leme (JIRA) [mailto:[EMAIL PROTECTED] > Sent: mardi 9 novembre 2004 00:22 > To: [EMAIL PROTECTED] > Subject: [jira] Commented: (CACTUS-70) junit report should include the > server names > > [ http://nagoya.apache.org/jira/browse/CACTUS- > 70?page=comments#action_55223 ] > > Felipe Leme commented on CACTUS-70: > ----------------------------------- > > Vincent, > > Regarding the Ant task you proposed in the devs list (which would extends > junitreport): would it handle multiple servers or would it a task for each > server (and then we would glue all together with Jelly)? >
As I mentioned I have not thought about it more than 2 minutes and we need to come up with a proper architecture/design. Also, I have never used the junitreport task from Java so I don't know if it is made to be extensible or not but if not, it can be encapsulated. I don't think we need to have the same API than the junitreport task. I think it's a good idea to make it support aggregating several XML tests representing several containers. If you're interested in following this up, I thin the best is to come up with an example of how this task would be used. Imagine you replace existing code in plugin.jelly by this task. How would it look like in the plugin.jelly? Again, I'm not saying this Ant task is the best possible solution as I haven't thought more about it. The only thing I know is that we have way too much Jelly code (more than 1000 lines I think!!) which is a design smell. Code in Jelly should remain minimal. Thanks -Vincent --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
