[
http://jira.jboss.com/jira/browse/JBAS-4811?page=comments#action_12383672 ]
Dimitris Andreadis commented on JBAS-4811:
------------------------------------------
C'mon guys, this really looks like a non-issue to me.
Since the 'all' configuration of jboss contains an unexploded juddi-service.sar
with scout.jar inside, the test classpath should be changed to look there for the
libraries. Or even look for scout.jar in the client libraries directory, it is there,
too.
So either make this modification and re-tag jbossws-2.0.1.SP2, or hack the hudson build
(like Rajesh has done already AFAIK) and fix it later in jbossws.
Integrate the JBossWS core testsuite in the release QA
------------------------------------------------------
Key: JBAS-4811
URL:
http://jira.jboss.com/jira/browse/JBAS-4811
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Thomas Diesler
Assigned To: Rajesh Rajasekaran
Fix For: JBossAS-4.2.2.GA
Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely
will not get discovered through the existing JAX-WS test coverage in the AS test suite.
The jbossws core tests should be run (automated) as part of every AS community release.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira