Bug#814410: RM: plexus-component-metadata -- ROM; no longer used, replaced by plexus-containers1.5

2016-02-11 Thread Emmanuel Bourg 
Package: ftp.debian.org
Severity: normal

Hi,

Could you please remove plexus-component-metadata, this package is no
longer used and a more recent version of the Maven plugin it contains
is now available in plexus-containers1.5.

Thank you,

Emmanuel Bourg

Re: reintroduce jlint Java static analysis tool?

2016-02-11 Thread Emmanuel Bourg 
Le 10/02/2016 23:45, Paul Wise a écrit :

> I tend to think a diversity of static analysis tools is better than
> single tools, since they all inevitably wax and wane in maintenance
> over the years as well as support different checks.

jlint hasn't been updated for years, it looks like it doesn't even
handle the Java 5 syntax. On the other hand Findbugs was updated last
year and can analyze Java 8 code.


> It is the only Java static analysis tool that check-all-the-things
> knows how to run automatically. My last attempt at getting help with
> adding support for findbugs/checkstyle/etc was met with silence.

Sorry for the silence but your last message about check-all-the-things
on this list [1] just invited people to add more TODOs or checks. It
didn't sound like you were struggling with Findbugs and were asking for
help on a specific issue with this tool.

Emmanuel Bourg

[1] https://lists.debian.org/debian-java/2015/11/msg00019.html

[Help]: Bug#808593: htsjdk: FTBFS: [testng] FAILED: testHTTPNotExist

2016-02-11 Thread Andreas Tille 
Hi,

any hint why this test that worked before might fail since end of
December?

Kind regards

 Andreas.

On Mon, Dec 21, 2015 at 10:59:11AM +, Chris Lamb wrote:
> Source: htsjdk
> Version: 1.138+dfsg.1-4
> Severity: serious
> Justification: fails to build from source
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: ftbfs
> X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
> 
> Dear Maintainer,
> 
> htsjdk fails to build from source in unstable/amd64:
> 
>   [..]
> 
>  [testng] PASSED: testReadAndSkipWithMultipleBlocks([null of CHAR, null 
> of CHAR, null of FLOAT])
>  [testng] PASSED: testReadAndSkipWithMultipleBlocks([null of CHAR, null 
> of CHAR, null of CHAR])
>  [testng] FAILED: testHTTPNotExist
>  [testng] java.lang.AssertionError: expected [false] but found [true]
>  [testng] at org.testng.Assert.fail(Assert.java:94)
>  [testng] at org.testng.Assert.failNotEquals(Assert.java:496)
>  [testng] at org.testng.Assert.assertEquals(Assert.java:125)
>  [testng] at org.testng.Assert.assertEquals(Assert.java:288)
>  [testng] at org.testng.Assert.assertEquals(Assert.java:298)
>  [testng] at 
> htsjdk.tribble.util.ParsingUtilsTest.tstExists(ParsingUtilsTest.java:142)
>  [testng] at 
> htsjdk.tribble.util.ParsingUtilsTest.testHTTPNotExist(ParsingUtilsTest.java:137)
>  [testng] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native 
> Method)
>  [testng] at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>  [testng] at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  [testng] at java.lang.reflect.Method.invoke(Method.java:606)
>  [testng] at 
> org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:85)
>  [testng] at 
> org.testng.internal.Invoker.invokeMethod(Invoker.java:639)
>  [testng] at 
> org.testng.internal.Invoker.invokeTestMethod(Invoker.java:821)
>  [testng] at 
> org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1131)
>  [testng] at 
> org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:124)
>  [testng] at 
> org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:108)
>  [testng] at org.testng.TestRunner.privateRun(TestRunner.java:773)
>  [testng] at org.testng.TestRunner.run(TestRunner.java:623)
>  [testng] at org.testng.SuiteRunner.runTest(SuiteRunner.java:357)
>  [testng] at 
> org.testng.SuiteRunner.runSequentially(SuiteRunner.java:352)
>  [testng] at 
> org.testng.SuiteRunner.privateRun(SuiteRunner.java:310)
>  [testng] at org.testng.SuiteRunner.run(SuiteRunner.java:259)
>  [testng] at 
> org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
>  [testng] at 
> org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
>  [testng] at 
> org.testng.TestNG.runSuitesSequentially(TestNG.java:1185)
>  [testng] at org.testng.TestNG.runSuitesLocally(TestNG.java:1110)
>  [testng] at org.testng.TestNG.run(TestNG.java:1018)
>  [testng] at org.testng.TestNG.privateMain(TestNG.java:1325)
>  [testng] at org.testng.TestNG.main(TestNG.java:1294)
>  [testng] 
>  [testng] SKIPPED: basic
>  [testng] org.testng.TestNGException: 
>  [testng] Method public void 
> htsjdk.samtools.util.IupacTest.basic(java.lang.String) throws 
> java.lang.Exception requires a @DataProvider named : basicDataProvider
>  [testng] at 
> org.testng.internal.Parameters.findDataProvider(Parameters.java:262)
>  [testng] at 
> org.testng.internal.Parameters.handleParameters(Parameters.java:418)
>  [testng] at 
> org.testng.internal.Invoker.handleParameters(Invoker.java:1276)
>  [testng] at 
> org.testng.internal.Invoker.createParameters(Invoker.java:992)
>  [testng] at 
> org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1082)
>  [testng] at 
> org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:124)
>  [testng] at 
> org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:108)
>  [testng] at org.testng.TestRunner.privateRun(TestRunner.java:773)
>  [testng] at org.testng.TestRunner.run(TestRunner.java:623)
>  [testng] at org.testng.SuiteRunner.runTest(SuiteRunner.java:357)
>  [testng] at 
> org.testng.SuiteRunner.runSequentially(SuiteRunner.java:352)
>  [testng] at 
> org.testng.SuiteRunner.privateRun(SuiteRunner.java:310)
>  [testng] at org.testng.SuiteRunner.run(SuiteRunner.java:259)
>  [testng] at 
> org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:

Re: [Help]: Bug#808593: htsjdk: FTBFS: [testng] FAILED: testHTTPNotExist

2016-02-11 Thread Emmanuel Bourg 
Le 11/02/2016 21:01, Andreas Tille a écrit :

> any hint why this test that worked before might fail since end of
> December?

I got a quick look and I can't explain this test failure. It doesn't
seem very important though, you could just disable this test.

Emmanuel Bourg

Re: reintroduce jlint Java static analysis tool?

2016-02-11 Thread Paul Wise 
On Thu, Feb 11, 2016 at 11:36 PM, Emmanuel Bourg wrote:

> Sorry for the silence but your last message about check-all-the-things
> on this list [1] just invited people to add more TODOs or checks. It
> didn't sound like you were struggling with Findbugs and were asking for
> help on a specific issue with this tool.

I was asking for help adding support for the Java-specific tools to
check-all-the-things. Sorry, I should have been more specific about
what I needed help with.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise