Bug#745127: tuxguitar: Messages in ~/.xsession-errors

2014-04-18 Thread Torquil Macdonald Sørensen
Package: tuxguitar Version: 1.2-18 Severity: normal After only using tuxguitar a few seconds, I have gotten over 4000 lines of messages in ~/.xsession-errors. This makes it much more difficult to detect real problems from other active programs. Here are a few examples: 58 (TuxGuitar:6145):

Bug#733234: Groovy fails with groovy.lang.MissingMethodException

2014-04-18 Thread Russel Winder
On Fri, 2014-04-18 at 00:44 +0100, Stephen Nelson wrote: […] I'm looking at this too, as it stops work on building Spring using Gradle. I updated groovy to 1.8.9, and still gradle fails. So I thought about including the required dependencies to enable the groovy tests. This will prove the

Bug#733234: Groovy fails with groovy.lang.MissingMethodException

2014-04-18 Thread Eric L.
Hi, On 18/04/14 17:18, Russel Winder wrote: The core problem here with the Java and Groovy support on Debian is the policy of one and only one version, and no use of Maven Central or Bintray/jCentre for build. I am not aware of any such policy as one and only one version: one could have a

Bug#733234: Groovy fails with groovy.lang.MissingMethodException

2014-04-18 Thread Russel Winder
On Fri, 2014-04-18 at 17:54 +0200, Emmanuel Bourg wrote: Thank you for stepping in Russel. No problem, glad to help. Just to clarify the unique version policy isn't an absolute requirement. If it's necessary multiple versions of an application or library can be packaged (for example JUnit 3

Bug#733234: Groovy fails with groovy.lang.MissingMethodException

2014-04-18 Thread Emmanuel Bourg
Thank you for stepping in Russel. Just to clarify the unique version policy isn't an absolute requirement. If it's necessary multiple versions of an application or library can be packaged (for example JUnit 3 and 4, Maven 2 and 3, Tomcat 678, ASM 3 and 4, etc). Thanks to your explanations it