[
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
