Issue 11547 - Command line support enhancement for any Runtime
Summary: Command line support enhancement for any Runtime
Status: CLOSED FIXED
Alias: None
Product: General
Classification: Code
Component: scripting (show other issues)
Version: current
Hardware: All All
: P3 Trivial (vote)
Target Milestone: OOo 2.0
Assignee: tomaisoc
QA Contact: issues@framework
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-02-17 08:28 UTC by Unknown
Modified: 2003-06-13 11:34 UTC (History)
1 user (show)

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

Attachments
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 Unknown 2003-02-17 08:28:21 UTC 
Need to enhance command line support so any Runtime can use it, not just Java
and Beanshell.

Propose the following to enable the creation of a parcel descriptor and it's
deployment for any Runtime.

Command line flags to be added:
-n <logical name - required>
-l <Optional language - defaults to Java>
-f <Optional function name - defaults to logical name if not specified>
-p <Optional language specific properties, needed to run the script, one or more
name=value pairs, separated by ; >
-t <Optional target = User, Share or office document, if not specified
parcel_descriptor will be created but the script will NOT be deployed>
Comment 1 tomaisoc 2003-02-17 16:56:14 UTC 
Went through the current options for the CommandLineTools class and
the new requirements with John and the following are the enhancements
to the options we are going to support: 

Generation of Script Parcels
======================

-g [parcel dir]

If the parcel dir is not specified will try the current directory.

[-l lang[=extension[;extension2]]]

Add possibility to specify the extension supported for this language to be
used by the ExtensionFinder implementation of the MethodFinder
interface

[-p name=value[;name2=value2]]

Allows you to specify a list of name value pairs which will be added to
the languagedepprops element in the parcel-descriptor.xml file

-v

Allows you to request verbose feedback on the generation process.

Parcel Deployment
===============
java CommandLineTools -d <parcel> <target>
Same as before

The automatic generation of the parcel-descriptor.xml file will be changed
as follows:


     -l specified?     parcel-descriptor.xml           result
                                      exists?

          none                        no                    Error message
          none                        yes              Generate parcel.sxp
        -l language                 no               Generate parcel
descriptor + sxp
        -l language                 yes             Generate parcel
descriptor + sxp
These changes will need to be documented so adding the
requires_documentation flag.
Comment 2 Unknown 2003-02-18 07:26:56 UTC 
Clarification on table:

The automatic generation of the parcel-descriptor.xml file will be
changed as follows:


-l specified?     parcel-descriptor.xml           result
                  exists?

none                        no                    Error message

none                        yes                   Generate .sxp
                                                  using existing 
                                                  parcel descriptor

-l language                 no                    Generate parcel
                                                  descriptor + .sxp

-l language                 yes                   Overwrite existing
                                                  parcel descriptor +   
                                                  Generate .sxp

These changes will need to be documented so adding the
requires_documentation flag.
Comment 3 tomaisoc 2003-02-24 12:59:03 UTC 
This is now fixed as per comments.
Comment 4 robert.kinsella 2003-06-13 11:34:37 UTC 
verified fixed, can deploy beanshell, javascript and java scripts to
OpenOffice.org and StarOffice. SFrameworkInstall ed0.3 rc4.
Closing issue