axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Malinda Kaushalye Kapuruge (JIRA)" <>
Subject [jira] Commented: (AXIS2C-412) after installing rampart module, it does not copy into modules directory
Date Fri, 24 Nov 2006 05:51:02 GMT
    [ ] 
Malinda Kaushalye Kapuruge commented on AXIS2C-412:

I think along with this we need to copy sample axis2.xml file to the deploy directory. Otherwise
rampart would not get engaged.
But then the existing file would be overridden.:(
And further user might need to configure the axis2.xml to suit the environment. So simply
copying the rampart module to the deploy/module wouldn't work.

BTW, If we stick to the current "U have to copy and configure" policy, I'd like to remove
that unnecessary level  in rampart installation directory. Right now it is
         |- rampart (module)

Instead we can have a structure similar to
    |-rampart (module)
    |-samples(axis2.xml + binaries)


> after installing rampart module, it does not copy into modules directory
> ------------------------------------------------------------------------
>                 Key: AXIS2C-412
>                 URL:
>             Project: Axis2-C
>          Issue Type: Bug
>          Components: build system (Unix/Linux)
>    Affects Versions: Current (Nightly)
>            Reporter: Dinesh Premalal
>             Fix For: 0.96
> After installing rampart module it doesn't copy into modules directory. It is in rampart/rampart
directory. User happen to copy it into modules directory. If we don't have special reason
to locate in rampart/rampart better to copy it into modules directory when installing.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message