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 2007/06/19 23:02:57 UTC
[jira] Created: (WAGON-89) When you use a call that doesn not use
authentication the call should not throw an authentication exception
When you use a call that doesn not use authentication the call should not throw an authentication exception
------------------------------------------------------------------------------------------------------------
Key: WAGON-89
URL: http://jira.codehaus.org/browse/WAGON-89
Project: wagon
Issue Type: Improvement
Components: wagon-provider-api
Affects Versions: 1.0-beta-2
Reporter: Jason van Zyl
A general problem with the way we make requests. We should differentiate between authenticated and non-authenticated requests. To make a call that requires no authentication like a simple file or http retrieval and have to trap an authentication error makes no sense and is confusing to consumers of the API.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (WAGON-89) When you use a call that doesn not use
authentication the call should not throw an authentication exception
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/WAGON-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated WAGON-89:
------------------------------
Comment: was deleted
> When you use a call that doesn not use authentication the call should not throw an authentication exception
> ------------------------------------------------------------------------------------------------------------
>
> Key: WAGON-89
> URL: http://jira.codehaus.org/browse/WAGON-89
> Project: Maven Wagon
> Issue Type: Improvement
> Components: wagon-provider-api
> Affects Versions: 1.0-beta-2
> Reporter: Jason van Zyl
> Assignee: Brett Porter
>
> A general problem with the way we make requests. We should differentiate between authenticated and non-authenticated requests. To make a call that requires no authentication like a simple file or http retrieval and have to trap an authentication error makes no sense and is confusing to consumers of the API.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (WAGON-89) When you use a call that doesn not use
authentication the call should not throw an authentication exception
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/WAGON-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter reopened WAGON-89:
-------------------------------
got it - so it should be removed from the connect methods that don't pass authentication
> When you use a call that doesn not use authentication the call should not throw an authentication exception
> ------------------------------------------------------------------------------------------------------------
>
> Key: WAGON-89
> URL: http://jira.codehaus.org/browse/WAGON-89
> Project: Maven Wagon
> Issue Type: Improvement
> Components: wagon-provider-api
> Affects Versions: 1.0-beta-2
> Reporter: Jason van Zyl
> Assignee: Brett Porter
>
> A general problem with the way we make requests. We should differentiate between authenticated and non-authenticated requests. To make a call that requires no authentication like a simple file or http retrieval and have to trap an authentication error makes no sense and is confusing to consumers of the API.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (WAGON-89) When you use a call that doesn not use
authentication the call should not throw an authentication exception
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/WAGON-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated WAGON-89:
------------------------------
Fix Version/s: 1.0-beta-3
> When you use a call that doesn not use authentication the call should not throw an authentication exception
> ------------------------------------------------------------------------------------------------------------
>
> Key: WAGON-89
> URL: http://jira.codehaus.org/browse/WAGON-89
> Project: Maven Wagon
> Issue Type: Improvement
> Components: wagon-provider-api
> Affects Versions: 1.0-beta-2
> Reporter: Jason van Zyl
> Fix For: 1.0-beta-3
>
>
> A general problem with the way we make requests. We should differentiate between authenticated and non-authenticated requests. To make a call that requires no authentication like a simple file or http retrieval and have to trap an authentication error makes no sense and is confusing to consumers of the API.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (WAGON-89) When you use a call that doesn not
use authentication the call should not throw an authentication exception
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/WAGON-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=136951#action_136951 ]
Jason van Zyl commented on WAGON-89:
------------------------------------
You misunderstand. If someone is doing work that never requires authentication which is a lot of the time then throwing an exception is confusing. It's not expected if you're not authenticating.
> When you use a call that doesn not use authentication the call should not throw an authentication exception
> ------------------------------------------------------------------------------------------------------------
>
> Key: WAGON-89
> URL: http://jira.codehaus.org/browse/WAGON-89
> Project: Maven Wagon
> Issue Type: Improvement
> Components: wagon-provider-api
> Affects Versions: 1.0-beta-2
> Reporter: Jason van Zyl
> Assignee: Brett Porter
>
> A general problem with the way we make requests. We should differentiate between authenticated and non-authenticated requests. To make a call that requires no authentication like a simple file or http retrieval and have to trap an authentication error makes no sense and is confusing to consumers of the API.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (WAGON-89) When you use a call that doesn not use
authentication the call should not throw an authentication exception
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/WAGON-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated WAGON-89:
------------------------------
Fix Version/s: 1.x
yeah, makes sense.
> When you use a call that doesn not use authentication the call should not throw an authentication exception
> ------------------------------------------------------------------------------------------------------------
>
> Key: WAGON-89
> URL: http://jira.codehaus.org/browse/WAGON-89
> Project: Maven Wagon
> Issue Type: Improvement
> Components: wagon-provider-api
> Affects Versions: 1.0-beta-2
> Reporter: Jason van Zyl
> Assignee: Brett Porter
> Fix For: 1.x
>
>
> A general problem with the way we make requests. We should differentiate between authenticated and non-authenticated requests. To make a call that requires no authentication like a simple file or http retrieval and have to trap an authentication error makes no sense and is confusing to consumers of the API.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (WAGON-89) When you use a call that doesn not use
authentication the call should not throw an authentication exception
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/WAGON-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter closed WAGON-89.
-----------------------------
Assignee: Brett Porter
Resolution: Won't Fix
Fix Version/s: (was: 1.0-beta-3)
only "connect" throws an authentication exception (as expected).
get/put, etc all throw authorization exceptions, which is to be expected as certain files may require different permissions
> When you use a call that doesn not use authentication the call should not throw an authentication exception
> ------------------------------------------------------------------------------------------------------------
>
> Key: WAGON-89
> URL: http://jira.codehaus.org/browse/WAGON-89
> Project: Maven Wagon
> Issue Type: Improvement
> Components: wagon-provider-api
> Affects Versions: 1.0-beta-2
> Reporter: Jason van Zyl
> Assignee: Brett Porter
>
> A general problem with the way we make requests. We should differentiate between authenticated and non-authenticated requests. To make a call that requires no authentication like a simple file or http retrieval and have to trap an authentication error makes no sense and is confusing to consumers of the API.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (WAGON-89) When you use a call that doesn not
use authentication the call should not throw an authentication exception
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/WAGON-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=136966#action_136966 ]
Brett Porter commented on WAGON-89:
-----------------------------------
I see what you mean, but any simple http retrieval has a chance of requiring authentication - isn't it fair to throw an AuthenticationException for attempting to connect without credentials when they are required? Or would you prefer to just roll that into a ConnectionException?
> When you use a call that doesn not use authentication the call should not throw an authentication exception
> ------------------------------------------------------------------------------------------------------------
>
> Key: WAGON-89
> URL: http://jira.codehaus.org/browse/WAGON-89
> Project: Maven Wagon
> Issue Type: Improvement
> Components: wagon-provider-api
> Affects Versions: 1.0-beta-2
> Reporter: Jason van Zyl
> Assignee: Brett Porter
>
> A general problem with the way we make requests. We should differentiate between authenticated and non-authenticated requests. To make a call that requires no authentication like a simple file or http retrieval and have to trap an authentication error makes no sense and is confusing to consumers of the API.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (WAGON-89) When you use a call that doesn not
use authentication the call should not throw an authentication exception
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/WAGON-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=136967#action_136967 ]
Jason van Zyl commented on WAGON-89:
------------------------------------
Doesn't need to be fixed now, and it would change the API which is probably a bad thing. I would just imagine connectWithAuthentication( AuthGoop ), or have some request parameter and throw a runtime exception. I haven't thought about it too much, I just raised the issue when I was coding against the API to retrieve a file and I had to throw that exception when I know I was never going to require auth. I don't think you can change it until after the 1.0.
> When you use a call that doesn not use authentication the call should not throw an authentication exception
> ------------------------------------------------------------------------------------------------------------
>
> Key: WAGON-89
> URL: http://jira.codehaus.org/browse/WAGON-89
> Project: Maven Wagon
> Issue Type: Improvement
> Components: wagon-provider-api
> Affects Versions: 1.0-beta-2
> Reporter: Jason van Zyl
> Assignee: Brett Porter
>
> A general problem with the way we make requests. We should differentiate between authenticated and non-authenticated requests. To make a call that requires no authentication like a simple file or http retrieval and have to trap an authentication error makes no sense and is confusing to consumers of the API.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira