To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=64558


User bei changed the following:

                What    |Old value                 |New value
================================================================================
                  Status|REOPENED                  |NEW
--------------------------------------------------------------------------------




------- Additional comments from [EMAIL PROTECTED] Wed Feb 20 16:59:49 +0000 
2008 -------
bei->hr: This cannot be solved by EIS it must be solved by new cwsadd
commandline tool support for it if it is doable at all. The EIS SOAP interface
for adding a new module will already add the new module to it´s database if it
is not already known and add it to the ChildWorkspace than. Problem is that
information of what modules are KNOW to a MasterWorkspace is not a matter of the
EIS database but of build environment configuration files such as the stand.lst
file. I think there is at least the need for a new feature of cwsadd to add a
new module which updates these configuration files than calls the EIS SOAP
interface which is also called for existing modules and probably even
additionally sends an email to Release Engineering. Wether we can also add
support to cwsquery for asking which modules are new must be seen. I don´t know
the glory details of those configuration files and the perl module to access
them. Please have a look. As a quick solution for the main part of the problem
we could maybe just start with just calling the EIS SOAP interface for adding
modules also for new modules so that they are know to exist on the CWS which
might eventually already make the tinderboxes happy.


---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to