[
https://issues.apache.org/jira/browse/DIRMINA-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17404747#comment-17404747
]
Sebb commented on DIRMINA-1144:
-------------------------------
Note that a SNAPSHOT is only used if the user POM is updated to reference a
snapshot version, e.g. replace
<version>2.1.4</version>
with
<version>2.2.0-SNAPSHOT</version>
If a new 2.2.0 snapshot is uploaded Maven downloads it when it next checks
Maven Central.
But if you are referring to a new formal release, then reverting to the normal
POM should pick it up.
To pick up the next release version, use the following in the POM:
<version>2.2.0</version>
> Deadlock with SSL + Proxy
> -------------------------
>
> Key: DIRMINA-1144
> URL: https://issues.apache.org/jira/browse/DIRMINA-1144
> Project: MINA
> Issue Type: Bug
> Components: SSL
> Affects Versions: 2.1.3, 2.1.4
> Reporter: Giuseppe Persico
> Assignee: Jonathan Valliere
> Priority: Critical
> Fix For: 2.2.0
>
> Attachments: thread-dump-clean.txt
>
>
> You will find the thread dump attached. This seems to be a problem that
> occurs using SSL in combination with proxy. I found the problem in the 2.1.4
> and 2.1.3 versions. The 2.0.20, instead, seems to work,
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
