jira.codehaus.org

  • Log In Access more options
    • Online Help
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What?s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
  • Maven Wagon
  • WAGON-295

Provide more debug information in wagon (http request/response/headers)

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Improvement Improvement
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: None
  • Fix Version/s: backlog
  • Component/s: None
  • Labels:
    None

Description

Is there any way to have more debug information concerning wagon with the option -e -X ?
Like commons-httpclient does :

  • http requests
  • http response
  • http headers
    Thanks,
    Olivier

Issue Links

is related to

Bug - A problem which impairs or prevents the functions of the product. MNG-1585 debug logging from wagon not shown in debug mode

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
Brett Porter added a comment - 21/Nov/05 1:04 AM

related, not the same. that is additional logging, this is showing what's there

Show
Brett Porter added a comment - 21/Nov/05 1:04 AM related, not the same. that is additional logging, this is showing what's there
Hide
Permalink
John Casey added a comment - 09/Feb/09 9:35 AM

Consolidating to 2.1.0-M1 so we can then rename to 2.1.0. We can weed out any issues we want to push to a later release from this set once we've done the consolidation.

Show
John Casey added a comment - 09/Feb/09 9:35 AM Consolidating to 2.1.0-M1 so we can then rename to 2.1.0. We can weed out any issues we want to push to a later release from this set once we've done the consolidation.
Hide
Permalink
Chris Dolan added a comment - 01/Jul/11 12:29 PM

In my opinion, the biggest bang-for-buck would be to enhance LightweightHttpWagon.finishPutTransfer() to append the getErrorStream() body to the thrown TransferFailedException in some manner and also to make sure that the TransferListener implementation pulls that message out in debug mode. That would allow the Wagon to remain ignorant of the debug on/off setting. But it would either require 1) an unwieldy exception message, 2) an API change for TransferFailedException or 3) a change/extension to the TransferListener API

Show
Chris Dolan added a comment - 01/Jul/11 12:29 PM In my opinion, the biggest bang-for-buck would be to enhance LightweightHttpWagon.finishPutTransfer() to append the getErrorStream() body to the thrown TransferFailedException in some manner and also to make sure that the TransferListener implementation pulls that message out in debug mode. That would allow the Wagon to remain ignorant of the debug on/off setting. But it would either require 1) an unwieldy exception message, 2) an API change for TransferFailedException or 3) a change/extension to the TransferListener API

People

  • Assignee:
    Unassigned
    Reporter:
    Olivier Lamy
Vote (0)
Watch (1)

Dates

  • Created:
    10/Nov/05 12:07 PM
    Updated:
    22/Sep/11 7:26 AM
  • Atlassian JIRA (v5.0.4#731-sha1:3aa7374)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.