Re: Removing the "Question" type from JIRA

2010-08-09 Thread Asankha C. Perera
Hi Oleg It worked for me. No idea why. Ah cool.. I guess you have JIRA instance administration privileges in addition to administration privileges on the project. Please note, though, I chose to delete the existing issues of type Question instead of converting them to bugs. I think this

Re: Removing the "Question" type from JIRA

2010-08-09 Thread Oleg Kalnichevski
On Mon, 2010-08-09 at 21:56 +0530, Asankha C. Perera wrote: > Hi Oleg, Sebastian > > Issue Type Scheme: Apache Default Issue Type Scheme > > > > whereas HC uses > > > > Issue Type Scheme: Default Issue Type Scheme > > > > I tried to change this, but was not able to .. I even added myself as

Re: Removing the "Question" type from JIRA

2010-08-09 Thread Asankha C. Perera
Hi Oleg, Sebastian Issue Type Scheme: Apache Default Issue Type Scheme whereas HC uses Issue Type Scheme: Default Issue Type Scheme I tried to change this, but was not able to .. I even added myself as an admin, and even temporarily the project lead - but still it didn't allow me.. I

Re: Removing the "Question" type from JIRA

2010-08-09 Thread sebb
On 9 August 2010 15:19, Oleg Kalnichevski wrote: > On Mon, 2010-08-09 at 19:28 +0530, Asankha C. Perera wrote: >> Hi All >> >> Eric has informed me that the JIRA issue type "Question" seems to be >> misleading some of our users to ask questions using the JIRA. Almost all >> of these [1] have been

Re: Removing the "Question" type from JIRA

2010-08-09 Thread Oleg Kalnichevski
On Mon, 2010-08-09 at 19:28 +0530, Asankha C. Perera wrote: > Hi All > > Eric has informed me that the JIRA issue type "Question" seems to be > misleading some of our users to ask questions using the JIRA. Almost all > of these [1] have been then marked as Invalid, and the users requested > to

Removing the "Question" type from JIRA

2010-08-09 Thread Asankha C. Perera
Hi All Eric has informed me that the JIRA issue type "Question" seems to be misleading some of our users to ask questions using the JIRA. Almost all of these [1] have been then marked as Invalid, and the users requested to use the forums.. Shall I disable this type of issues from JIRA - if po

Re: Release new parent POM 4.1

2010-08-09 Thread sebb
On 9 August 2010 14:46, Oleg Kalnichevski wrote: > On Mon, 2010-08-09 at 14:42 +0100, sebb wrote: >> On 9 August 2010 14:32, Oleg Kalnichevski wrote: >> > ... >> > >> >> >> > >> >> >> > Sebastian >> >> >> > >> >> >> > I finally got around to finalizing the release process. I was able to >> >> >>

Re: Release new parent POM 4.1

2010-08-09 Thread Oleg Kalnichevski
On Mon, 2010-08-09 at 14:42 +0100, sebb wrote: > On 9 August 2010 14:32, Oleg Kalnichevski wrote: > > ... > > > >> >> > > >> >> > Sebastian > >> >> > > >> >> > I finally got around to finalizing the release process. I was able to > >> >> > delete .asc.md5 and .asc.sha1 but for some reason I was un

Re: Release new parent POM 4.1

2010-08-09 Thread sebb
On 9 August 2010 14:32, Oleg Kalnichevski wrote: > ... > >> >> > >> >> > Sebastian >> >> > >> >> > I finally got around to finalizing the release process. I was able to >> >> > delete .asc.md5 and .asc.sha1 but for some reason I was unable to >> >> > promote the release. The Promote button always

Re: Release new parent POM 4.1

2010-08-09 Thread Oleg Kalnichevski
... > >> > > >> > Sebastian > >> > > >> > I finally got around to finalizing the release process. I was able to > >> > delete .asc.md5 and .asc.sha1 but for some reason I was unable to > >> > promote the release. The Promote button always stays grayed out for me. > >> > What could be the reason? A

Re: Release new parent POM 4.1

2010-08-09 Thread sebb
On 27 July 2010 20:16, Oleg Kalnichevski wrote: > On Tue, 2010-07-27 at 19:38 +0100, ant elder wrote: >> On Tue, Jul 27, 2010 at 12:26 PM, Oleg Kalnichevski wrote: >> > On Thu, 2010-07-15 at 22:35 +0100, sebb wrote: >> >> On 15 July 2010 21:51, Oleg Kalnichevski wrote: >> >> > ... >> >> > >> >>

[jira] Resolved: (HTTPCLIENT-976) (v3.x) Deadlock in case of concurrent calls to MultiThreadedHttpConnectionManager.shutdown and shutdownAll

2010-08-09 Thread Oleg Kalnichevski (JIRA)
[ https://issues.apache.org/jira/browse/HTTPCLIENT-976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Kalnichevski resolved HTTPCLIENT-976. -- Fix Version/s: (was: 3.1.1) Resolution: Won't Fix 3.x code line

[jira] Created: (HTTPCLIENT-976) (v3.x) Deadlock in case of concurrent calls to MultiThreadedHttpConnectionManager.shutdown and shutdownAll

2010-08-09 Thread Sylvain Laurent (JIRA)
(v3.x) Deadlock in case of concurrent calls to MultiThreadedHttpConnectionManager.shutdown and shutdownAll -- Key: HTTPCLIENT-976 URL: https://issues.apache.or