|Re: pde build leaves temp folders when using p2.gathering [message #133597 is a reply to message #133534]
||Wed, 24 June 2009 19:16
| Andrew Niefer
Registered: July 2009
Instead of setting buildDirectory=workspace, you can set it to be some |
other folder where you don't mind the extra files.
Then, set "pluginPath=workspace". "pluginPath" is a File.pathSeparator
(: or ; depending on the platform) separated list of extra locations to
look for plugins and features in. Doing this lets build find all your
plugins, but generate most of the scripts elsewhere.
This will take care of the assemble/package scripts. I think you are
stuck cleaning up the build.xml and javaCompiler.*.args manually.
Tom Hofmann wrote:
> Thanks Andrew,
> this solves the problem I was asking about - are there any additional
> properties I can set to keep my workspace even cleaner? Currently I
> manually remove the following generated files:
> - generated build scripts per bundle (build.xml)
> - overall assemble / packaging scripts
> - javaCompiler.*.args
> Andrew Niefer wrote:
>> If your buildDirectory is the same as your workspace, you can get
>> these temporary files generated elsewhere by setting
>> buildTempFolder = /some/other/folder
>> If you have features, you may also want to set "feature.temp.folder"
>> Export from the UI uses these to help avoid polluting the workspace.
>> Tom Hofmann wrote:
>>> thanks michael,
>>> this is of course possible, but I'd rather keep one source tree and
>>> keep it as clean as possible. Removing any stale "@dot" and
>>> "feature.temp" elements is easy, but removing the ever different
>>> subfolders from the bundle is awkhard with ant...
>>> MSacarny wrote:
>>>> I use ant script to copy all projects needed to the buildDirectory
>>>> in advance of the build. This avoids polluting the workspace.
Powered by FUDForum
. Page generated in 0.02412 seconds