Re: Closing as "Won't Fix" and "Fix Version" combo

Thank, Paul. On Jan 29, 2014, at 5:05 PM, Paul Benedict wrote: > Done. There were a few tickets also "Incomplete" and "Not a Bug" and > "Cannot Reproduce" statuses. Those are all conceptually the same thing as > "Won't Fix" in regards to not taking any development action. So 7 tickets > got move

Re: Closing as "Won't Fix" and "Fix Version" combo

Done. There were a few tickets also "Incomplete" and "Not a Bug" and "Cannot Reproduce" statuses. Those are all conceptually the same thing as "Won't Fix" in regards to not taking any development action. So 7 tickets got moved out of the 3.2 report list, which will greatly help our users on what wo

Re: [jira] (s) relative local repository settings

On Jan 29, 2014, at 3:39 PM, Pyeron, Jason J CTR (US) wrote: >> -Original Message- >> From: Jason van Zyl >> Sent: Wednesday, January 29, 2014 12:59 PM >> >> High value is a matter of perspective. I'm personally not interested in > > Yes it is a matter of perspective, but to evidence

Re: Closing as "Won't Fix" and "Fix Version" combo

Okay, I can go through the 3.2 tickets and do that unless someone objects. On Wed, Jan 29, 2014 at 1:55 PM, Anders Hammar wrote: > I agree. > > /Anders (mobile) > Den 29 jan 2014 18:24 skrev "Paul Benedict" : > > > At times, we close issues as "Won't Fix" but leave the version number on > > it.

RE: [jira] (s) relative local repository settings

> -Original Message- > From: Jason van Zyl > Sent: Wednesday, January 29, 2014 12:59 PM > > High value is a matter of perspective. I'm personally not interested in Yes it is a matter of perspective, but to evidence the value we have created a patch and forked. > any feature that encour

Re: Closing as "Won't Fix" and "Fix Version" combo

I agree. /Anders (mobile) Den 29 jan 2014 18:24 skrev "Paul Benedict" : > At times, we close issues as "Won't Fix" but leave the version number on > it. I can understand why someone might do that, but I think it creates more > confusion than good. For example, we publish the JIRA ticket on the Ma

Re: [jira] (s) relative local repository settings

High value is a matter of perspective. I'm personally not interested in any feature that encourages or promotes putting binaries in your SCM. This is an outmoded definition of reproducibility IMO. I'm also not interested in adjusting the whole system to support this. If adhering to CMMI is a re

Re: Closing as "Won't Fix" and "Fix Version" combo

Sure, makes sense to remove the version. On Jan 29, 2014, at 12:23 PM, Paul Benedict wrote: > At times, we close issues as "Won't Fix" but leave the version number on > it. I can understand why someone might do that, but I think it creates more > confusion than good. For example, we publish the

Closing as "Won't Fix" and "Fix Version" combo

At times, we close issues as "Won't Fix" but leave the version number on it. I can understand why someone might do that, but I think it creates more confusion than good. For example, we publish the JIRA ticket on the Maven site for each new version -- but without status, I think it's normal for peo

Re: [PATCH] Allow spaces in javadoc exclude list

* Baptiste Mathus [2014-01-28 15:51]: > Hi, > It was possible historically, but I think it was disabled due to spamming > issue. > Anyway, the best way to create an account on codehaus is by using xircles: > http://xircles.codehaus.org/signup > > This will help you have only one account for jira

RE: [jira] (MNG-5167) relative local repository settings

This was closed as won't fix. This is still something that is of high value. Can the close comment be more substantiated and it be migrated to apache? Respectfully, Jason Pyeron -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- -

Re: [PATCH] Allow spaces in javadoc exclude list

Found this: https://confluence.atlassian.com/display/JIRAKB/How+to+Customise+the+Login+Gadget Seems as with 6.0 you alter /atlassian-jira/includes/loginform.jsp Possibly needs to be re-applied when upgrading though. /Anders On Wed, Jan 29, 2014 at 12:50 PM, Stephen Connolly < stephen.alan.conn

Re: [PATCH] Allow spaces in javadoc exclude list

Ben seems confident he can use jquery to fix it... On 29 January 2014 09:55, Anders Hammar wrote: > I think this also calls for an request for improvement to Atlassian. That > text should be configurable. > > /Anders > > > On Wed, Jan 29, 2014 at 10:51 AM, Stephen Connolly < > stephen.alan.conn

maven-scm pull request: Upgrade the dependency on JUnit (4.11) and Hamcrest...

GitHub user ebourg opened a pull request: https://github.com/apache/maven-scm/pull/7 Upgrade the dependency on JUnit (4.11) and Hamcrest (1.3) Hi, The maven-scm-provider-accurev tests do not compile with the latest version of JUnit and Hamcrest. Here is a patch fixing it.

Re: [PATCH] Allow spaces in javadoc exclude list

I think this also calls for an request for improvement to Atlassian. That text should be configurable. /Anders On Wed, Jan 29, 2014 at 10:51 AM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > FYI, when you go to jira.codehaus.org, the System Dashboard has two boxes > at the top...

Re: [PATCH] Allow spaces in javadoc exclude list

FYI, when you go to jira.codehaus.org, the System Dashboard has two boxes at the top... On the Right Hand Side: Login... with the text "Not a member? To request an account, please contact your JIRA administrators" On the Left Hand Side: Introduction... with the text "Sign-up for a JIRA account Yo

Re: [PATCH] Allow spaces in javadoc exclude list

You go to xircles.codehaus.org to get an account... I'll ask Ben@codehausto see if the JIRA signup message can be changed to point people at xircles... On 28 January 2014 20:52, Paul Benedict wrote: > Good point. It seems JIRA is setup not to allow public signup. Who in Maven > Land can help hi