|
Hi Michael, Peter, 1) Its not a good idea to use user actions instead of compile commands, as user actions will not retrieve the events file and populate the error list. Also there are preferences for Command execution which only affect compile commands. 2) I believe if you share connections (ie use team profiles), then the user actions and compile commands are also shared. If you don't want to use team connections, then you may just want to try copying over the contents of following folder to other team members' workspaces (I haven't tried this, but I don't see why it wouldn't work) workspace\RemoteSystemsConnections\profileName\CompileCommands It appears that the compile commands are stored in an XML file, so copying it over will cause any previously compile command settings to be lost. I have opened a requirement for easier import/export of user actions. thanks, Violaine Batthish WebSphere Development Studio Client, IBM Toronto Lab wdsci-l-bounces@xxxxxxxxxxxx wrote on 12/14/2006 06:46:18 AM:
<Peter.Colpaert@xxxxxxxxx> wrote in message news:mailman.2579.1166095972.1743.wdsci-l@xxxxxxxxxxxxxxxWe put our custom compile commands under "User actions" instead of "Compile". Maybe that can be a work-around.Peter, That sounds like a good idea. We are going to use the iSeries Project perspective to leverage all the benefits it provides. To compile a member
in
one of the source-files in the project, what I have been doing is to right-click, choose Remote actions, then compile and then the compile command I want. I don't see an option for "user actions". How do I get to
that from the project perspective? -- Regards, Michael Rosinger Systems Programmer / DBA Computer Credit, Inc. 640 West Fourth Street Winston-Salem, NC 27101 336-761-1524 m rosinger at cciws dot com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.