[jbossws-dev] [Design of JBoss Web Services] - Re: JBossWS Test Approach

[richard.opalka@jboss.com]

"alessio.soldano at jboss.com" wrote : 
  | ... we're evaluating this still a bit early ...
  |  I don't think so. We were talking about this problem a year ago for the first time. I'm afraid we'll be talking about it next years :(
"alessio.soldano at jboss.com" wrote : 
  | ... AS is not completely mavenized yet ...
  |  and won't be next few years ;) Note that AS mavenization process runs already more than 1 year and it's still at its beginnings.
"alessio.soldano at jboss.com" wrote : 
  | ...Once the process will be completed I think we will be pretty sure we're testing against the right artifacts.
  | Almost true, but not absolute ;)

"alessio.soldano at jboss.com" wrote : 
  | This said, the specific failures that made us to stop and think about our testing approach were caused by some mistakes we actually did in the webservice module pom.xml in the AS. IOW it didn't have the right dependencies which were instead specified in the container integration pom.xml files. Of course this caused the trunk and 5_x branch only to fail, but I fixed that. The whole "exclusion game" in the stacks' testsuite pom.xml is not required anymore, there're few dependencies still specified there and they're quite straightforward.
  | Thanks for the hotfix Alessio, but it didn't solve the problem I'm discussing here. It just hotfixed the result of the problem. I'd like to fix the reason of all these problems instead. I'll explain this argument in next post following this one.

"alessio.soldano at jboss.com" wrote : 
  | Finally, considering we're using maven for the project, I think it's important to run tests using surefire. IOW my point of view is that either we use this tool (maven) completely or we don't use it (which currently is not an option given the direction taken 1 year ago by the whole AS development).
  | Basing the tests on maven dependencies was the most natural solution when the mavenization took place, what would you suggest instead of that? I don't like that much the idea of specifying the surefire additionalClasspath with a list of jar from the curent AS... any other idea?

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4216117#4216117

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4216117