maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Bentmann (JIRA)" <>
Subject [jira] Commented: (MASSEMBLY-382) Review IT failure on Windows
Date Fri, 01 May 2009 16:55:44 GMT


Benjamin Bentmann commented on MASSEMBLY-382:

While the IT is now passing on Windows, too, I feel there's still something wrong with the
SimpleAggregatingDescriptorHandler whose purpose seems to be to replace one or more files
with a single file holding their concatenated contents.

It seems essential that {{isSelected()}} gets called before {{finalizeArchiveCreation()}}.
However, in {{AbstractArchiver.createArchive()}} the control flow (basically) is

-  validate()
-  runArchiveFinalizers()
-  execute()
-  close()
-  cleanUp()

Due to lack of interest I haven't investigated further but sponteneously it seems {{runArchiveFinalizers()}}
and {{execute()}} are executed in the wrong order for the {{SimpleAggregatingDescriptorHandler}}
to work. Indeed, the aggregated file {{custom-containerDescriptorHandler/assembly/target/assembly-1-bin/file.txt}}
is empty [0].

This discrepancy is not checked by the corresponding {{verify.bsh}} because it has some broken
  start with result=true
  read the lines of the aggregated file
    if contents matches, set result=true
but if the contents does not match, the test still passes because result was already initialized
with true.


> Review IT failure on Windows
> ----------------------------
>                 Key: MASSEMBLY-382
>                 URL:
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: Task
>    Affects Versions: 2.2-beta-3
>            Reporter: Benjamin Bentmann
>            Priority: Minor
>         Attachments: build.log
> I observe the following IT failure on my WinXP box as well as on [Hudson's Vista box|,label=windows/53/console]:
> {noformat}
> [INFO] Building: container-descriptors\custom-containerDescriptorHandler\pom.xml
> [INFO] ...FAILED. The post-build script returned false.
> {noformat}
> Attached is the {{build.log}} of this IT.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message