Issue 123893 - Provide a script to deploy libraries to an installed office
Summary: Provide a script to deploy libraries to an installed office
Status: CONFIRMED
Alias: None
Product: Build Tools
Classification: Code
Component: code (show other issues)
Version: 4.1.0-dev
Hardware: All All
: P3 Normal (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact: Andre
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-20 12:51 UTC by Andre
Modified: 2014-02-27 10:32 UTC (History)
1 user (show)

See Also:
Issue Type: TASK
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
new deploy.xml files and script (11.75 KB, patch)
2014-02-27 10:32 UTC, Andre 		no flags Details | Diff
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Andre 2013-12-20 12:51:17 UTC 
In the edit, build, debug cycle there is a manual step of copying newly built libraries, resource files, etc. to an installed office.  This step could be automated.

A new script, say main/solenv/bin/deploy.pl could use to-be-written data files <module/prj/deploy.lst to copy the relevant files to an installed office.  The deploy.lst are necessary because the relevant files can not be determined from the list of delivered files (as defined in <module>/prj/d.lst, which for gbuild modules do not even exist)
Comment 1 Andre 2014-02-27 10:32:31 UTC 
Created attachment 82731 [details]
new deploy.xml files and script

New deploy.xml files and perl script to evaluate them.