[jbossws-issues] [JBoss JIRA] Commented: (JBWS-1924) Verify installation script for jboss-4.2.1.GA

[Alessio Soldano (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBWS-1924?page=comments#action_12393792 ] 
            
Alessio Soldano commented on JBWS-1924:
---------------------------------------

This was due to the jbossws-jboss421.jar not being included in the lib dir of the binary release. The macro performing the jboss421 deploy was OK, thus compiling and deploying from svn source worked. According to me this was also the reason why Hudson wasn't failing (even the distro jobs, because when they're executed at least another deploy has already been done on that application server, thus the required lib is available).
I also fixed the undeploy macro to delete the jbossws-jboss421.jar (the same way as we do for jboss40).

> Verify installation script for jboss-4.2.1.GA
> ---------------------------------------------
>
>                 Key: JBWS-1924
>                 URL: http://jira.jboss.com/jira/browse/JBWS-1924
>             Project: JBoss Web Services
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions:  jbossws-2.0.2
>            Reporter: Alessio Soldano
>         Assigned To: Alessio Soldano
>             Fix For:  jbossws-2.0.3
>
>
> Installing JBossWS 2.0.2.GA on JBoss 4.2.1.GA without having a JBossWS 2.0.1.GA installed result in a broken installation due to jbossws-jboss42.jar/jbossws-jboss421.jar missing in client libs.
> The 2.0.2 installation script does not remove that lib, thus installing 2.0.1 and then 2.0.2 seems to be a workaround. This has to be verified as well as the 2.0.2 installation script / hudson conf for the 4.2.1. 

-- 
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