Hi Asankha,
The idea was to develop this feature as a COMMONS subproject so that all
the products can make use of it. I created an issue
https://wso2.org/jira/browse/COMMONS-46 to keep track of this.
Thanks
Azeez
Asankha C. Perera wrote:
Azeez
This is definitely a good suggestion.. however I think its better to
keep such a new feature out from the immediate next releases right now,
and bring it in with the upcoming unification instead?
thanks
asankha
Afkham Azeez wrote:
Hi folks,
Will it be a good idea for WSAS to periodically check whether patches
are available and issue an alert? We can host the patches on
OxygenTank, http://wso2.org/wsas/2.2/patches/. This directory can have
a patches.xml file which will give some information regarding the
patch, as well as the relevant patches. If the user decides to apply
the patch, WSAS can itself download this patch to the
$WSO2WSAS_HOME/lib/patches directory, and ask the user to restart the
server.
The advantage of this approach is that the users do not have to
constantly be in touch with the mailing lists etc. to find out about
important patches.
We can follow the same approach for the other products such as WSO2
ESB as well.
Thoughts?
Thanks
Azeez
_______________________________________________
Wsas-java-user mailing list
[EMAIL PROTECTED]
http://wso2.org/cgi-bin/mailman/listinfo/wsas-java-user
_______________________________________________
Esb-java-user mailing list
[EMAIL PROTECTED]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
_______________________________________________
Esb-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
