You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2005/09/28 18:15:11 UTC

[jira] Updated: (MNG-1032) artifact error reporting has regressed

     [ http://jira.codehaus.org/browse/MNG-1032?page=all ]

John Casey updated MNG-1032:
----------------------------

            Complexity: Expert  (was: Intermediate)
    Remaining Estimate: 1 hour
     Original Estimate: 3600

for the first case, it's just a matter of injecting the WagonManager into the artifact error diagnoser to we can check for offline mode, then appending the offline warning conditionally.

for the second issue, I'm not sure what's missing or how this error diagnoser may have affected it...need more details.

> artifact error reporting has regressed
> --------------------------------------
>
>          Key: MNG-1032
>          URL: http://jira.codehaus.org/browse/MNG-1032
>      Project: Maven 2
>         Type: Bug
>   Components: maven-artifact
>     Reporter: Brett Porter
>     Assignee: John Casey
>      Fix For: 2.0-beta-3

>
> Original Estimate: 1 hour
>         Remaining: 1 hour
>
> a couple of issues I've noted recently:
> - the exception always talks about offline mode. this should only be added in offline mode
> - the old install:install-file information seems to have gone missing

-- 
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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org