Hello,

I'm asking for some help on implementing / improving this feature commonly used 
in my enterprise builds.
Objective is to generate a specific traceability file, for modules generating 
tar.gz assembly, with the list of files contained in the tar.gz along with 
their checksum.
Constraints are : solution must be implemented in only one module, and easy to 
customize/understand. Tar.gz assembly can come from predefined assembly 
(packaged in jar) or assembly.xml in module sources.

Idea already in place to implement this is as follow (simplified) :

-       Assembly:directory-single: generates tar.gz exploded as a folder

-       Antrun:run: generates file with list of checksums against exploded 
folder

-       Assembly:single: generates tar.gz included checksum file

Problems are that :

-       Use of directory-single is deprecated, to avoid it I would need to 
either :

o   Use 2 formats in assemblies (dir + tar.gz) and execute them twice (using 
dir the first time and tar.gz the second time) --> performance issue ... ?

o   Create 2 distinct assemblies with a different format --> duplication issue, 
not user-friendly

-       It leads to quite complex plugins configurations where order is 
supremely important, and difficult to understand, and any subtle variation can 
make the whole thing fail ...

Questions are :

-       Is there an easier and more maven-style way to achieve this need ?

-       I'd like to make this feature a plugin, but as it would need to be 
executed other more than one phase, I don't know how to proceed or where to 
start ...

Thanks,
Jeremie B.


Reply via email to