@Chris Dolan : Thanks for the very useful CAM::PDF ! indeed, the one liner you propose is all what it needs, but a help message and the options you originally put in appendpdf.pl are useful. BTW I proposed the script as new feature on CPAN. Not sure if you want it or not in the distribution.

@Leifbk : just rename the file to catpdf.pl if you want :) But the cat command by default outputs to STDOUT whereas the script outpus to a file (which can be STDOUT if you give it the special "-" name). Anyway that's why I called it mergepdf and not catpdf @rtheb : ah true, I could use ghostscript here, but it's just not installed on my mac right now @Jochen Hayek : I used to use PDFSAM, but as far as I know you have to use it from the Graphical interface, and I need to automate (script) the process. Or can you use it from the command line ?

@Walter : thanks for reposting. The issue with the "pre" tag is that in the Typepad editor, if you are in "rich text" mode, the Editor will escape the pre tags with lt; and gt; stuff... At least it does that for me ! Have you a better working editor ? I'd be interested to see what you get. About the "code" tag : indeed it doesn't look good in Internet Explorer. I'll try to fix it

@Walter : thanks for reposting. The issue with the pre tag is that in the Typepad editor, if you are in "rich text" mode, the Editor will escape the pre tags with lt; and gt; stuff... At least it does that for me ! Have you a better working editor ? I'd be interested to see what you get. About the "code" tag : indeed it doesn't look good in Internet Explorer. I'll try to fix it

@Jeff Lavallee : You are right ! I should probably have mentioned that before expanding the explanation to adding a new Build.PL action. However in my particular need, I needed the command line to be as simple as it could be, as it had to be launched by other people, not familiar with Perl... Thats why I went on with adding a Build.PL rule

@ Graham TerMarsch : First of all, It worked well on Mac OS X. Then I saw that there were no PPM available for windows. Nevertheless, I tried to include TAP::Formatter::JUnit locally to my modules, in an include directory, and have that directory pushed to @INC somehow. It worked well on Mac OS X again (after uninstalling the system version of T::F::JUnit), but I didnt manage to make it work on windows... It complained with Cant load T::H::JUnit (useing the module worked however). Instead of spending more time in what was becoming darker and darker hacking, I tried the other solution, which worked, and I kinda liked the idea of having an additional action for Module::Build dams

@ Michael Peters : The main reason for not using Smolder, is that I didn't have choice about installing and using Hudson :) It was already there, and part of the job was to plug my tests to it, not come with a different continuous integration platform. The other reason may be that I didn't know much about Smolder. I think it would benefit from some kind of public homepage and better introduction, if you want to advertise it. Nevertheless I'll try to give it a go for my personal knowledge :)