You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jason van Zyl (JIRA)" <ji...@codehaus.org> on 2012/06/06 13:16:21 UTC
[jira] (MNG-5295) Review compatibility of default transport in
Maven
Jason van Zyl created MNG-5295:
----------------------------------
Summary: Review compatibility of default transport in Maven
Key: MNG-5295
URL: https://jira.codehaus.org/browse/MNG-5295
Project: Maven 2 & 3
Issue Type: Task
Reporter: Jason van Zyl
I've seen issues reported with pre-emptive auth, client side certs, and NTLM with the new transport. I think we might have been too hasty in quickly flipping over to a new transport which is so fundamental to Maven. That it might make sense to roll back to the light weight transport in the short/medium term.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5295) Review compatibility of default transport in
Maven
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MNG-5295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason van Zyl updated MNG-5295:
-------------------------------
Description:
I've seen issues reported with pre-emptive auth, client side certs, and NTLM with the new transport. I think we might have been too hasty in quickly flipping over to a new transport which is so fundamental to Maven. That it might make sense to roll back to the light weight transport in the short/medium term.
MNG-5237
MNG-5293
was:
I've seen issues reported with pre-emptive auth, client side certs, and NTLM with the new transport. I think we might have been too hasty in quickly flipping over to a new transport which is so fundamental to Maven. That it might make sense to roll back to the light weight transport in the short/medium term.
MNG-5293
> Review compatibility of default transport in Maven
> --------------------------------------------------
>
> Key: MNG-5295
> URL: https://jira.codehaus.org/browse/MNG-5295
> Project: Maven 2 & 3
> Issue Type: Task
> Reporter: Jason van Zyl
> Assignee: Jason van Zyl
>
> I've seen issues reported with pre-emptive auth, client side certs, and NTLM with the new transport. I think we might have been too hasty in quickly flipping over to a new transport which is so fundamental to Maven. That it might make sense to roll back to the light weight transport in the short/medium term.
> MNG-5237
> MNG-5293
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5295) Review compatibility of default transport in
Maven
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MNG-5295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason van Zyl updated MNG-5295:
-------------------------------
Description:
I've seen issues reported with pre-emptive auth, client side certs, and NTLM with the new transport. I think we might have been too hasty in quickly flipping over to a new transport which is so fundamental to Maven. That it might make sense to roll back to the light weight transport in the short/medium term.
MNG-5293
was:I've seen issues reported with pre-emptive auth, client side certs, and NTLM with the new transport. I think we might have been too hasty in quickly flipping over to a new transport which is so fundamental to Maven. That it might make sense to roll back to the light weight transport in the short/medium term.
> Review compatibility of default transport in Maven
> --------------------------------------------------
>
> Key: MNG-5295
> URL: https://jira.codehaus.org/browse/MNG-5295
> Project: Maven 2 & 3
> Issue Type: Task
> Reporter: Jason van Zyl
> Assignee: Jason van Zyl
>
> I've seen issues reported with pre-emptive auth, client side certs, and NTLM with the new transport. I think we might have been too hasty in quickly flipping over to a new transport which is so fundamental to Maven. That it might make sense to roll back to the light weight transport in the short/medium term.
> MNG-5293
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5295) Review compatibility of default transport in
Maven
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MNG-5295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason van Zyl reassigned MNG-5295:
----------------------------------
Assignee: Jason van Zyl
> Review compatibility of default transport in Maven
> --------------------------------------------------
>
> Key: MNG-5295
> URL: https://jira.codehaus.org/browse/MNG-5295
> Project: Maven 2 & 3
> Issue Type: Task
> Reporter: Jason van Zyl
> Assignee: Jason van Zyl
>
> I've seen issues reported with pre-emptive auth, client side certs, and NTLM with the new transport. I think we might have been too hasty in quickly flipping over to a new transport which is so fundamental to Maven. That it might make sense to roll back to the light weight transport in the short/medium term.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira