Hi all. How the issue information is send to you, by email, http, soap,etc ?? Can I configure this mechanism if I´m behind a proxy?
Jorge. De: [email protected] [mailto:[email protected]] En nombre de Hasini Yatawatte Enviado el: martes, 29 de marzo de 2011 21:30 Para: [email protected] Asunto: [Carbon-dev] Issue tracker component and the feature is available in the trunk Hi devs, Issue Tracker component is available in the trunk now. I have created a feature and available in the trunk which can be installed in products. In addition to functions provided in the initial mail, following are the additions I have made. Capturing carbon product name and version automatically when an issue is reported. Below is a sample set of environment details captured automatically as the issue is reported to JIRA. Available projects,issue types and priorities are now directly taken from the JIRA rather hard coding at our end since there can be different work flow schemes/work flows etc. Files including images can be attached to issues. In addition can ask the tool to attach bundle.info, log file and a tread dump. Issues reported from each account can be viewed in a paginated manner. As per the automatic issue reporting, I managed to merge the code written by Ajith with the issue tracker component. At the time of adding a new account or editing an existing account, user can enable or disable the automatic issue reporting function. But registering the JIRA appender as a log4j property is yet to be done. Thanks, -- Hasini Randika Yatawatte, Software Engineer. WSO2 Inc. _______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
