Guillaume Nodet created SSHD-233:
Summary: Provide better error messages instead of Unable to
negociate key exchange for item 2
Key: SSHD-233
URL: https://issues.apache.org/jira/browse/SSHD-233
[
https://issues.apache.org/jira/browse/SSHD-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13710760#comment-13710760
]
Guillaume Nodet commented on SSHD-228:
--
This is a configuration problem.
The key
[
https://issues.apache.org/jira/browse/SSHD-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet resolved SSHD-228.
--
Resolution: Not A Problem
Assignee: Guillaume Nodet
java.lang.IllegalStateException:
[
https://issues.apache.org/jira/browse/SSHD-232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13710771#comment-13710771
]
Guillaume Nodet commented on SSHD-232:
--
Could you check with 0.8 ? I can see the
Le 7/17/13 1:11 AM, sebb a écrit :
On 16 July 2013 23:09, Emmanuel Lécharny elecha...@gmail.com wrote:
Le 7/16/13 11:34 PM, sebb a écrit :
On 16 July 2013 18:34, Emmanuel Lécharny elecha...@gmail.com wrote:
The NL files only depend on what is in the archives.
It's just a question of checking
Le 7/17/13 1:19 AM, sebb a écrit :
On 16 July 2013 23:18, Julien Vermillard jvermill...@gmail.com wrote:
On Tue, Jul 16, 2013 at 11:18 PM, sebb seb...@gmail.com wrote:
On 16 July 2013 19:59, Julien Vermillard jvermill...@gmail.com wrote:
Hi !
After some NOTICE and LICENSE file fixes (thanks
Guillaume Nodet created SSHD-234:
Summary: Support partial authentication
Key: SSHD-234
URL: https://issues.apache.org/jira/browse/SSHD-234
Project: MINA SSHD
Issue Type: New Feature
On 17 July 2013 10:56, elecha...@apache.org wrote:
Updated Branches:
refs/heads/trunk 0d04eba45 - 84b2003fc
Revert [maven-release-plugin] prepare for next development iteration
This reverts commit 0d04eba4525ca85886c4a03acc20b444ff69a52d.
However trunk is now in an incorrect state, as
Le 7/17/13 2:21 PM, sebb a écrit :
On 17 July 2013 10:56, elecha...@apache.org wrote:
Updated Branches:
refs/heads/trunk 0d04eba45 - 84b2003fc
Revert [maven-release-plugin] prepare for next development iteration
This reverts commit 0d04eba4525ca85886c4a03acc20b444ff69a52d.
However
What about the rest of the POM versions - they have all lost their
-SNAPSHOT suffices.
Trunk should never be left in a non-SNAPSHOT state for long periods.
Ideally it should never lose the -SNAPSHOT suffix, but the Maven
release plugin has not been designed to avoid this.
On 17 July 2013 11:16,
[
https://issues.apache.org/jira/browse/SSHD-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13711022#comment-13711022
]
Sebb commented on SSHD-233:
---
BTW, in UK English it is: negotiate
Provide better
Hi,
3rd attempt to cut a release. The binary package now contains just what is
needed, and the Nexus repository now contains the release.
A temporary tag has been created (it can be removed if the vote is not
approved):
- GIT tag : mina-parent-3.0.0-M1 SHA-1 :
Le 7/17/13 2:27 PM, sebb a écrit :
What about the rest of the POM versions - they have all lost their
-SNAPSHOT suffices.
They have also been moved to SNAPSHOT.
The process does a SNAPSHOT - tag - SNAPSHOT, but it's not immediat.
Especially when the guy cutting the release is having lunch
On 17 July 2013 09:09, Emmanuel Lécharny elecha...@gmail.com wrote:
Le 7/17/13 1:11 AM, sebb a écrit :
On 16 July 2013 23:09, Emmanuel Lécharny elecha...@gmail.com wrote:
Le 7/16/13 11:34 PM, sebb a écrit :
On 16 July 2013 18:34, Emmanuel Lécharny elecha...@gmail.com wrote:
The NL files only
On 17 July 2013 13:26, Emmanuel Lécharny elecha...@gmail.com wrote:
Le 7/17/13 2:21 PM, sebb a écrit :
On 17 July 2013 10:56, elecha...@apache.org wrote:
Updated Branches:
refs/heads/trunk 0d04eba45 - 84b2003fc
Revert [maven-release-plugin] prepare for next development iteration
This
On 17 July 2013 13:41, Emmanuel Lécharny elecha...@gmail.com wrote:
Le 7/17/13 2:27 PM, sebb a écrit :
What about the rest of the POM versions - they have all lost their
-SNAPSHOT suffices.
They have also been moved to SNAPSHOT.
The process does a SNAPSHOT - tag - SNAPSHOT, but it's not
Le 7/17/13 3:00 PM, sebb a écrit :
On 17 July 2013 13:26, Emmanuel Lécharny elecha...@gmail.com wrote:
Le 7/17/13 2:21 PM, sebb a écrit :
On 17 July 2013 10:56, elecha...@apache.org wrote:
Updated Branches:
refs/heads/trunk 0d04eba45 - 84b2003fc
Revert [maven-release-plugin] prepare for
[
https://issues.apache.org/jira/browse/SSHD-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet resolved SSHD-231.
--
Resolution: Fixed
Fix Version/s: 0.9.0
Assignee: Guillaume Nodet
Resolved as
Guillaume Nodet created SSHD-235:
Summary: Refactor client side authentication
Key: SSHD-235
URL: https://issues.apache.org/jira/browse/SSHD-235
Project: MINA SSHD
Issue Type: New Feature
[
https://issues.apache.org/jira/browse/SSHD-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet resolved SSHD-234.
--
Resolution: Fixed
Fix Version/s: 0.9.0
Assignee: Guillaume Nodet
Fixed by
[
https://issues.apache.org/jira/browse/SSHD-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet resolved SSHD-233.
--
Resolution: Fixed
Fix Version/s: 0.9.0
Assignee: Guillaume Nodet
Provide
On 17 July 2013 16:02, gno...@apache.org wrote:
[SSHD-233] Provide better error messages instead of Unable to negociate key
exchange for item 2
Project: http://git-wip-us.apache.org/repos/asf/mina-sshd/repo
Commit: http://git-wip-us.apache.org/repos/asf/mina-sshd/commit/0bc4246a
Tree:
On 17 July 2013 15:32, gno...@apache.org wrote:
[SSHD-195] Client side welcome banner support
Project: http://git-wip-us.apache.org/repos/asf/mina-sshd/repo
Commit: http://git-wip-us.apache.org/repos/asf/mina-sshd/commit/1937ee8e
Tree:
On 17 July 2013 15:19, Emmanuel Lécharny elecha...@gmail.com wrote:
Le 7/17/13 3:00 PM, sebb a écrit :
On 17 July 2013 13:26, Emmanuel Lécharny elecha...@gmail.com wrote:
Le 7/17/13 2:21 PM, sebb a écrit :
On 17 July 2013 10:56, elecha...@apache.org wrote:
Updated Branches:
Esko Luontola created DIRMINA-949:
-
Summary: Fixed IoBuffer.Pointer.setPosition to work in O(1)
instead of O(n) in the common case
Key: DIRMINA-949
URL: https://issues.apache.org/jira/browse/DIRMINA-949
GitHub user orfjackal opened a pull request:
https://github.com/apache/mina/pull/3
Fixed IoBuffer.Pointer.setPosition to work in O(1) instead of O(n) in the
common case
IoBuffer.Pointer.setPosition used to always iterate through the singly
linked list starting from the very
Le 7/17/13 5:53 PM, sebb a écrit :
On 17 July 2013 15:19, Emmanuel Lécharny elecha...@gmail.com wrote:
Le 7/17/13 3:00 PM, sebb a écrit :
On 17 July 2013 13:26, Emmanuel Lécharny elecha...@gmail.com wrote:
Le 7/17/13 2:21 PM, sebb a écrit :
On 17 July 2013 10:56, elecha...@apache.org wrote:
Esko Luontola created DIRMINA-950:
-
Summary: org.apache.mina.codec.IoBuffer#mark is untested and broken
Key: DIRMINA-950
URL: https://issues.apache.org/jira/browse/DIRMINA-950
Project: MINA
[
https://issues.apache.org/jira/browse/DIRMINA-950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Esko Luontola updated DIRMINA-950:
--
Description:
Currently the org.apache.mina.codec.IoBuffer#mark method sets the limit instead
[
https://issues.apache.org/jira/browse/DIRMINA-950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Esko Luontola updated DIRMINA-950:
--
Description:
Currently the org.apache.mina.codec.IoBuffer#mark method sets the limit instead
On 17 July 2013 17:00, Emmanuel Lécharny elecha...@gmail.com wrote:
Le 7/17/13 5:53 PM, sebb a écrit :
On 17 July 2013 15:19, Emmanuel Lécharny elecha...@gmail.com wrote:
Le 7/17/13 3:00 PM, sebb a écrit :
On 17 July 2013 13:26, Emmanuel Lécharny elecha...@gmail.com wrote:
Le 7/17/13 2:21 PM,
Le 7/17/13 6:15 PM, sebb a écrit :
On 17 July 2013 17:00, Emmanuel Lécharny elecha...@gmail.com wrote:
Le 7/17/13 5:53 PM, sebb a écrit :
On 17 July 2013 15:19, Emmanuel Lécharny elecha...@gmail.com wrote:
With SVN the way I do it is:
We don't use SVN anymore.
I realise that.
Maybe Git
[
https://issues.apache.org/jira/browse/SSHD-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet resolved SSHD-230.
--
Resolution: Fixed
Fix Version/s: 0.9.0
Assignee: Guillaume Nodet
Improved sftp
[
https://issues.apache.org/jira/browse/SSHD-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13711339#comment-13711339
]
Eli Collins commented on SSHD-230:
--
Really? I'm running the sftp server via ./bin/sshd.sh
[
https://issues.apache.org/jira/browse/SSHD-221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet resolved SSHD-221.
--
Resolution: Fixed
Fix Version/s: 0.9.0
Assignee: Guillaume Nodet
Don't
[
https://issues.apache.org/jira/browse/SSHD-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet resolved SSHD-229.
--
Resolution: Fixed
Fix Version/s: (was: 1.0.0)
Assignee: Guillaume Nodet
[
https://issues.apache.org/jira/browse/SSHD-226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet resolved SSHD-226.
--
Resolution: Fixed
Fix Version/s: 0.9.0
Assignee: Guillaume Nodet
Thx for the
[
https://issues.apache.org/jira/browse/SSHD-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet updated SSHD-225:
-
Fix Version/s: 0.9.0
Assignee: Guillaume Nodet
Summary: InvertedShellWrapper
[
https://issues.apache.org/jira/browse/SSHD-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet resolved SSHD-225.
--
Resolution: Fixed
InvertedShellWrapper does not shutdown its executor, preventing graceful
Build like a charm and NL looks correct for me (even if I'm not a layer :) .
+1
--
Julien Vermillard http://people.apache.org/~jvermillard/
On Wed, Jul 17, 2013 at 2:33 PM, Emmanuel Lécharny elecha...@gmail.com wrote:
Hi,
3rd attempt to cut a release. The binary package now contains
Build also except if the benchmarks profile is activated: build fails
because it seems the benchmarks pom is still on 3.0.0-M1-SNAPSHOT
For the next release, we should put the JDK 7 requirement in the parent POM
as a requirement : I think Maven will be more explicit
Jeff
On Wed, Jul 17, 2013
On 17 July 2013 23:19, Julien Vermillard jvermill...@gmail.com wrote:
I think the main problem is maven release is pushing your modification
when it could do all the work locally.
It's not possible to do it all locally. It must at least commit the
tag to be used for the release vote.
perhaps
The release plugin has a pushChanges flag for git which is true by default
for preserving compatibility but could be useful.
Jeff
On Thu, Jul 18, 2013 at 12:26 AM, sebb seb...@gmail.com wrote:
On 17 July 2013 23:19, Julien Vermillard jvermill...@gmail.com wrote:
I think the main problem is
On 17 July 2013 23:21, Jeff MAURY jeffma...@jeffmaury.com wrote:
Build also except if the benchmarks profile is activated: build fails
because it seems the benchmarks pom is still on 3.0.0-M1-SNAPSHOT
Both of these files still refer to the SNAPSHOT release:
benchmarks/pom.xml
On 17 July 2013 23:41, Emmanuel Lécharny elecha...@gmail.com wrote:
Le 7/18/13 12:21 AM, Jeff MAURY a écrit :
Build also except if the benchmarks profile is activated: build fails
because it seems the benchmarks pom is still on 3.0.0-M1-SNAPSHOT
Ahhh, my bad ! I cut the release without the
On Thu, Jul 18, 2013 at 12:42 AM, sebb seb...@gmail.com wrote:
On 17 July 2013 23:21, Jeff MAURY jeffma...@jeffmaury.com wrote:
Build also except if the benchmarks profile is activated: build fails
because it seems the benchmarks pom is still on 3.0.0-M1-SNAPSHOT
Both of these files still
I don't get your point. What is the problem is Java8 is used as soon as the
1.7 target is specified ?
Jeff
On Thu, Jul 18, 2013 at 12:57 AM, sebb seb...@gmail.com wrote:
On 17 July 2013 23:49, Jeff MAURY jeffma...@jeffmaury.com wrote:
On Thu, Jul 18, 2013 at 12:42 AM, sebb seb...@gmail.com
Le 7/18/13 12:42 AM, sebb a écrit :
On 17 July 2013 23:21, Jeff MAURY jeffma...@jeffmaury.com wrote:
Build also except if the benchmarks profile is activated: build fails
because it seems the benchmarks pom is still on 3.0.0-M1-SNAPSHOT
Both of these files still refer to the SNAPSHOT release:
On 18 July 2013 00:01, Jeff MAURY jeffma...@jeffmaury.com wrote:
I don't get your point. What is the problem is Java8 is used as soon as the
1.7 target is specified ?
You cannot use Java 1.6 to compile source=1.7; the compiler must be 1.7+
The only problem using 1.8 is that it provides
On 18 July 2013 00:10, Emmanuel Lécharny elecha...@gmail.com wrote:
Le 7/18/13 12:42 AM, sebb a écrit :
On 17 July 2013 23:21, Jeff MAURY jeffma...@jeffmaury.com wrote:
Build also except if the benchmarks profile is activated: build fails
because it seems the benchmarks pom is still on
What are you refering to ? The enforcer rule ?
The problem you mentioned about 1.8 should be managed by the animal sniffer
plugin
Jeff
On Thu, Jul 18, 2013 at 1:12 AM, sebb seb...@gmail.com wrote:
On 18 July 2013 00:10, Emmanuel Lécharny elecha...@gmail.com wrote:
Le 7/18/13 12:42 AM, sebb
So what is the enforcer needed for?
On 18 July 2013 00:15, Jeff MAURY jeffma...@jeffmaury.com wrote:
What are you refering to ? The enforcer rule ?
The problem you mentioned about 1.8 should be managed by the animal sniffer
plugin
Jeff
On Thu, Jul 18, 2013 at 1:12 AM, sebb
To make sure the build is run with a 1.7+ JDK
Jeff
On Thu, Jul 18, 2013 at 1:18 AM, sebb seb...@gmail.com wrote:
So what is the enforcer needed for?
On 18 July 2013 00:15, Jeff MAURY jeffma...@jeffmaury.com wrote:
What are you refering to ? The enforcer rule ?
The problem you mentioned
On 17 July 2013 22:16, Emmanuel Lécharny elecha...@gmail.com wrote:
Le 7/17/13 2:33 PM, Emmanuel Lécharny a écrit :
Hi,
3rd attempt to cut a release. The binary package now contains just what is
needed, and the Nexus repository now contains the release.
A temporary tag has been created
On Thu, Jul 18, 2013 at 1:40 AM, sebb seb...@gmail.com wrote:
On 18 July 2013 00:21, Jeff MAURY jeffma...@jeffmaury.com wrote:
To make sure the build is run with a 1.7+ JDK
As I already wrote, the compilation will fail unless it is.
The advantage of the enforcer plugin is that you have a
Le 7/18/13 1:12 AM, sebb a écrit :
On 18 July 2013 00:10, Emmanuel Lécharny elecha...@gmail.com wrote:
Le 7/18/13 12:42 AM, sebb a écrit :
On 17 July 2013 23:21, Jeff MAURY jeffma...@jeffmaury.com wrote:
Build also except if the benchmarks profile is activated: build fails
because it seems
Le 7/18/13 1:44 AM, sebb a écrit :
On 17 July 2013 22:16, Emmanuel Lécharny elecha...@gmail.com wrote:
Le 7/17/13 2:33 PM, Emmanuel Lécharny a écrit :
Hi,
3rd attempt to cut a release. The binary package now contains just what is
needed, and the Nexus repository now contains the release.
Le 7/18/13 2:39 AM, Emmanuel Lécharny a écrit :
Le 7/18/13 1:44 AM, sebb a écrit :
This is the third thing to fix for the next release.
And the forth one is the Java 7 enforcer that need to be added.
And the fifth one is the Benchmark module that have to be included into
the source tarball.
On 18 July 2013 01:42, Emmanuel Lécharny elecha...@gmail.com wrote:
Le 7/18/13 2:39 AM, Emmanuel Lécharny a écrit :
Le 7/18/13 1:44 AM, sebb a écrit :
This is the third thing to fix for the next release.
And the forth one is the Java 7 enforcer that need to be added.
And the fifth one is
Also the NOTICE files in the jars are wrong.
For example, coap starts:
Apache MINA CoAP (constrained application protocol) 3.0.0-M1
The leading blank line is wrong, and the version should not be appended.
Ideally the jar Manifests should have some more info; have a look for
example at any
Le 7/18/13 3:04 AM, sebb a écrit :
Also the NOTICE files in the jars are wrong.
For example, coap starts:
Apache MINA CoAP (constrained application protocol) 3.0.0-M1
The leading blank line is wrong, and the version should not be appended.
Not sure I grk what you say here...
Can you
On 18 July 2013 02:10, Emmanuel Lécharny elecha...@gmail.com wrote:
Le 7/18/13 3:04 AM, sebb a écrit :
Also the NOTICE files in the jars are wrong.
For example, coap starts:
Apache MINA CoAP (constrained application protocol) 3.0.0-M1
The leading blank line is wrong, and the version
Le 7/18/13 3:20 AM, sebb a écrit :
On 18 July 2013 02:10, Emmanuel Lécharny elecha...@gmail.com wrote:
Le 7/18/13 3:04 AM, sebb a écrit :
Also the NOTICE files in the jars are wrong.
For example, coap starts:
Apache MINA CoAP (constrained application protocol) 3.0.0-M1
The leading blank
63 matches
Mail list logo
