RE: MINA build with Java 8

Agreed, I just thought you were looking for an annotation - and this a built-in one, which means that by a simple 'grep' you can find all the place where it exists and handle each of them individually. -Original Message- From: jeffma...@gmail.com [mailto:jeffma...@gmail.com] On Behalf

RE: MINA build with Java 8

I think there is @SuppressWarning("javadoc") available... -Original Message- From: jeffma...@gmail.com [mailto:jeffma...@gmail.com] On Behalf Of Jeff MAURY Sent: Thursday, December 17, 2015 15:17 To: dev Subject: Re: MINA build with Java 8 Given the Java5 minimum

Re: MINA build with Java 8

Given the Java5 minimum requirement for MINA, can't we have an annotation. Jeff On Thu, Dec 17, 2015 at 2:08 PM, Emmanuel Lécharny wrote: > Le 17/12/15 13:49, Jeff MAURY a écrit : > > Agree that we should adopt Java8 standards related to JavaDoc. > > I think we should have

Re: MINA build with Java 8

Agree that we should adopt Java8 standards related to JavaDoc. I think we should have a CI job that does the check from now, even if it fails until we finished what you propose. Jeff On Thu, Dec 17, 2015 at 1:23 PM, Emmanuel Lécharny wrote: > Hi guys, > > Java 8 is pretty

Re: MINA build with Java 8

I was looking for an annotation to replace the javadoc comment specific to Xbean. Jeff On Thu, Dec 17, 2015 at 2:34 PM, Lyor Goldstein wrote: > Agreed, I just thought you were looking for an annotation - and this a > built-in one, which means that by a simple 'grep' you

Re: MINA build with Java 8

Le 17/12/15 13:49, Jeff MAURY a écrit : > Agree that we should adopt Java8 standards related to JavaDoc. > I think we should have a CI job that does the check from now, even if it > fails until we finished what you propose. Actually, the pb is just when we run mvn site (which makes sense, because

Re: MINA build with Java 8

Le 17/12/15 14:17, Jeff MAURY a écrit : > Given the Java5 minimum requirement for MINA, can't we have an annotation. Probably... I have no idea how xbean works...

Re: MINA build with Java 8

On Thu, Dec 17, 2015 at 2:20 PM, Lyor Goldstein wrote: > I think there is @SuppressWarning("javadoc") available... > We don't want that as it will not fix the real problem. Jeff > > -Original Message- > From: jeffma...@gmail.com [mailto:jeffma...@gmail.com] On

Selecting a specific KEX signature at client for server key

Hello, I have a challenge... Let's assume I need to securely reconnect to a server, for that purpose I store its public key. Every time I connect to this server I compare the public key accepted by ServerKeyVerifier with the public key that is approved. This works perfectly and securely, well,

Re: Selecting a specific KEX signature at client for server key

On 17 December 2015 at 18:19, Alon Bar-Lev wrote: > > Hello, > > I have a challenge... > > Let's assume I need to securely reconnect to a server, for that purpose I > store its public key. Every time I connect to this server I compare the > public key accepted by

MINA build with Java 8

Hi guys, Java 8 is pretty picky when it comes to Javadoc. In order to cut the latest release, I had to add this line in the main pom.xml : -Xdoclint:none At this point, I think that we should benefit from the strictness of Java 8 and get the Javadoc fixed for the next release. That