packagePublisher Patch to consider

[Cedric]

Chaps,

I have reworked the packagePublisher to be a bit more flexible. It now
supports folder and file. You can also rename files, save to different
folders within the package, save a folder hierachy with a file filter.

This is a sample of the configuration file xml:-
<package>
<name>$(solutionName)</name>
<compression>9</compression>
<manifest type="defaultManifestGenerator" />
<packageList>
<file sourceFile="myAsm.dll"/>
<file sourceFile="myPlugin.dll" targetFileName="yourPlugin.dll"/>
<file sourceFile="myProject\bin\release\myAsm.dll"
targetFolder="\"/>
<file sourceFile="myProject\bin\release\myAsm.dll"
targetFileName="myAsm2.dll" targetFolder="\myProject2\bin\release"/>
<folder sourceFolder="myProject\bin" fileFilter="*.xml"
includeSubFolders="true" flatten="true"/>
<folder sourceFolder="myProject\bin" fileFilter="*.pdb"
includeSubFolders="true" targetFolder="\debugfiles/>
</packageList>
</package>

I had originally developed this as a plugin (which i can supply to you
if you prefer) so that we could have a bit more control over the
packaging process.

** PLEASE NOTE ** if you do decide to include this in ccnet is IS A
BREAKING change to the configuration file.

Regards,

Cedric

[Craig & Sammi Sutherland]

I've had a quick look at this and tried to integrate it, but it breaks
several of the unit tests! I'll see if I can figure out what is not
working...


Craig

--
To unsubscribe, reply using "remove me" as the subject.

[Craig Sutherland]

I've had to change a couple of things to get it working with the unit tests,
but it is basically the same. The main difference is we can't use file and
folder for the element names (this breaks other places) - so I have changed
them to packageFile and packageFolder.

So the patch has been committed and the unit tests are now all fixed.