Maven 2 & 3

FileSet needs a toString() method to properly print in debug mode

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.0.8
  • Fix Version/s: 2.0.9, 3.0-alpha-1
  • Component/s: None
  • Labels:
    None
  • Patch Submitted:
    Yes
  • Number of attachments :
    1

Description

It would be nice if FileSet had a toString() method so it would print something intelligent rather than simply a memory location in debug mode.

Before this change, it prints like:
FileSet@129f3b5

With this patch, it prints like (assuming you accept my PatternSet patch):
FileSet {directory: src/main/resources, PatternSet [includes: {}, excludes: {}]}

Issue Links

is related to

Improvement - An improvement or enhancement to an existing feature or task. MNG-3467 PatternSet needs a toString() method to properly print 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.

Improvement - An improvement or enhancement to an existing feature or task. MNG-3469 Resource needs a toString() method to properly print 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
Hide
Permalink
Paul Benedict added a comment -

Please update these 3 related tickets to 2.0.9 so they get on the release notes.

Show
Paul Benedict added a comment - Please update these 3 related tickets to 2.0.9 so they get on the release notes.
Hide
Permalink
Wayne Fay added a comment -

I spoke with Brian about these, and the patches will go into 2.0.10 unless 2.0.9 is re-spun for some reason.

So, unless the fix version indicated in this jira is wrong, I think this will have to wait for 2.0.10's release notes.

Show
Wayne Fay added a comment - I spoke with Brian about these, and the patches will go into 2.0.10 unless 2.0.9 is re-spun for some reason. So, unless the fix version indicated in this jira is wrong, I think this will have to wait for 2.0.10's release notes.

People

  • Assignee:
    Brian Fox
    Reporter:
    Wayne Fay
Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: