Maven Shared Components

NLP IF no fileset directory specified.

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Won't Fix
  • Affects Version/s: file-management-1.2
  • Fix Version/s: None
  • Component/s: file-management
  • Labels:
    None
  • Environment:
    all
  • Patch Submitted:
    Yes
  • Number of attachments :
    3

Description

Hi guys I have created a patch for the MASSEMBLY-342 that should be applied to FileSetManager. This patch fixes a but that can arise if you make assemblies and in your assembly-descriptor you have filesets that don't specify directory.
For further info please look here:
http://jira.codehaus.org/browse/MASSEMBLY-342

  1. Text File
    massembly-342.txt
    25/Aug/08 2:54 PM
    1 kB
    Petar Tahchiev
  2. Text File
    mshared55-ver.1.txt
    26/Aug/08 4:26 AM
    1 kB
    Petar Tahchiev
  3. Text File
    mshared55-ver1-testcase.txt
    26/Aug/08 4:27 AM
    2 kB
    Petar Tahchiev

Issue Links

is depended upon by

Bug - A problem which impairs or prevents the functions of the product. MASSEMBLY-297 Assembly broke on GNU/Linux - NullPointerException

  • Critical - Crashes, loss of data, severe memory leak.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
is related to

Bug - A problem which impairs or prevents the functions of the product. MASSEMBLY-342 NPE when filtering fileSet

  • Critical - Crashes, loss of data, severe memory leak.
  • 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
Petar Tahchiev added a comment -

I have made a new version of the patch, because I noticed a few problems with the old one. Please use MSHARED-55-ver1 patch.

Show
Petar Tahchiev added a comment - I have made a new version of the patch, because I noticed a few problems with the old one. Please use MSHARED-55 -ver1 patch.
Hide
Permalink
Petar Tahchiev added a comment -

Here is a junit test-case that tests if we specify a fileset with no directory that we get nothing included.

Show
Petar Tahchiev added a comment - Here is a junit test-case that tests if we specify a fileset with no directory that we get nothing included.
Hide
Permalink
Benjamin Bentmann added a comment -

Petar, I am not sure whether your patch really solves MASSEMBLY-342. You are simply avoiding the NPE in the FileSetManager but as far as I understand, the NPE is adequate: A required parameter is missing and I wouldn't consider a FileSet without base directory a valid object. The Assembly Plugin is responsible to properly configure the FileSet before passing it down to the FileSetManager, so that needs fixing. In particular, consider the POM snippet given over at the MASSEMBLY-342

<fileSet>
  <filtered>true</filtered>
  <includes>
    <include>INSTALL*</include>
    <include>README*</include>
    <include>LICENSE*</include>
    <include>NOTICE*</include>
  </includes>
</fileSet>

which suggests that the user wants the FileSet to use the project's base directory. This is a completely different semantics than just returning an empty result list.

To summarize: I think this issue itself should be closed as "Won't fix". To real work is over in the Assembly Plugin.

Show
Benjamin Bentmann added a comment - Petar, I am not sure whether your patch really solves MASSEMBLY-342 . You are simply avoiding the NPE in the FileSetManager but as far as I understand, the NPE is adequate: A required parameter is missing and I wouldn't consider a FileSet without base directory a valid object. The Assembly Plugin is responsible to properly configure the FileSet before passing it down to the FileSetManager, so that needs fixing. In particular, consider the POM snippet given over at the MASSEMBLY-342 <fileSet> <filtered> true </filtered> <includes> <include> INSTALL* </include> <include> README* </include> <include> LICENSE* </include> <include> NOTICE* </include> </includes> </fileSet> which suggests that the user wants the FileSet to use the project's base directory. This is a completely different semantics than just returning an empty result list. To summarize: I think this issue itself should be closed as "Won't fix". To real work is over in the Assembly Plugin.

People

  • Assignee:
    Benjamin Bentmann
    Reporter:
    Petar Tahchiev
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: