Re: [Carbon-dev] Issue tracker component and the feature is available in the trunk
If your Carbon server has no way of connecting to the Internet, and the JIRA is external, then this won't work. However, if your Carbon server is behind a proxy, and you connect to the Internet via that proxy, you can connect to the external JIRA. In the case where you have setup your own internal JIRA server, there will be no issues. Azeez On Thu, Mar 31, 2011 at 10:17 AM, Jorge Infante Osorio wrote: > In my case I´m behind a http proxy also my carbon server , but in any of my > development maybe the carbon server will be behind a reverse proxy or http > proxy, not directly to internet. > > Jorge. > > De: carbon-dev-boun...@wso2.org [mailto:carbon-dev-boun...@wso2.org] En > nombre de Afkham Azeez > Enviado el: jueves, 31 de marzo de 2011 0:21 > Para: carbon-dev@wso2.org > Asunto: Re: [Carbon-dev] Issue tracker component and the feature is > available in the trunk > > We use the jira soap API. What do you mean by I here? The jira server, > carbon server or web browser? In any case, we could set the proxy at system > level. Also, did you mean HTTP proxy or any other type of proxy? > On Mar 31, 2011 6:47 AM, "Jorge Infante Osorio" wrote: > > 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: carbon-dev-boun...@wso2.org [mailto:carbon-dev-boun...@wso2.org] En > > nombre de Hasini Yatawatte > > Enviado el: martes, 29 de marzo de 2011 21:30 > > Para: carbon-dev@wso2.org > > 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 > > Carbon-dev@wso2.org > > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- *Afkham Azeez* Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com, * * *Member; Apache Software Foundation; **http://www.apache.org/*<http://www.apache.org/> * email: **az...@wso2.com* * cell: +94 77 3320919 blog: **http://blog.afkham.org* <http://blog.afkham.org>* twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Issue tracker component and the feature is available in the trunk
On Thu, Mar 31, 2011 at 6:46 AM, Jorge Infante Osorio wrote: > Hi all. > How the issue information is send to you, by email, http, soap,etc…?? > Basically remote access to JIRA can be enabled via RPC plugin [1]. In that case, remote access is available through SOAP and XML_RPC interfaces. As per the Issue Tracker, we are connecting to JIRA via a SOAP client and issue information are taken using JIRA's SOAP API [2]. > Can I configure this mechanism if I´m behind a proxy? > > Jorge. > > De: carbon-dev-boun...@wso2.org [mailto:carbon-dev-boun...@wso2.org] En > nombre de Hasini Yatawatte > Enviado el: martes, 29 de marzo de 2011 21:30 > Para: carbon-dev@wso2.org > 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 > Carbon-dev@wso2.org > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > [1] http://confluence.atlassian.com/display/JIRAEXT/JIRA+RPC+plugin [2] http://docs.atlassian.com/software/jira/docs/api/rpc-jira-plugin/latest/com/atlassian/jira/rpc/soap/JiraSoapService.html -- Hasini Randika Yatawatte, Software Engineer. WSO2 Inc. ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Issue tracker component and the feature is available in the trunk
In my case I´m behind a http proxy also my carbon server , but in any of my development maybe the carbon server will be behind a reverse proxy or http proxy, not directly to internet. Jorge. De: carbon-dev-boun...@wso2.org [mailto:carbon-dev-boun...@wso2.org] En nombre de Afkham Azeez Enviado el: jueves, 31 de marzo de 2011 0:21 Para: carbon-dev@wso2.org Asunto: Re: [Carbon-dev] Issue tracker component and the feature is available in the trunk We use the jira soap API. What do you mean by I here? The jira server, carbon server or web browser? In any case, we could set the proxy at system level. Also, did you mean HTTP proxy or any other type of proxy? On Mar 31, 2011 6:47 AM, "Jorge Infante Osorio" wrote: > 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: carbon-dev-boun...@wso2.org [mailto:carbon-dev-boun...@wso2.org] En > nombre de Hasini Yatawatte > Enviado el: martes, 29 de marzo de 2011 21:30 > Para: carbon-dev@wso2.org > 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 > Carbon-dev@wso2.org > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Issue tracker component and the feature is available in the trunk
We use the jira soap API. What do you mean by I here? The jira server, carbon server or web browser? In any case, we could set the proxy at system level. Also, did you mean HTTP proxy or any other type of proxy? On Mar 31, 2011 6:47 AM, "Jorge Infante Osorio" wrote: > 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: carbon-dev-boun...@wso2.org [mailto:carbon-dev-boun...@wso2.org] En > nombre de Hasini Yatawatte > Enviado el: martes, 29 de marzo de 2011 21:30 > Para: carbon-dev@wso2.org > 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 > Carbon-dev@wso2.org > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Issue tracker component and the feature is available in the trunk
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: carbon-dev-boun...@wso2.org [mailto:carbon-dev-boun...@wso2.org] En nombre de Hasini Yatawatte Enviado el: martes, 29 de marzo de 2011 21:30 Para: carbon-dev@wso2.org 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 Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[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. [image: environment.png] - 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. [image: attachments.png] - 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 Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
