Re: Compile commands and iProject property file

We have lots of application releases which we group in SVN, our SCM post ACMS, as branches. When we're working on a particular release/branch, we check it out as an iProject, do all the editing, etc then compile. There are utilities that we previously run in iSeries for formatting (for standards compliance), for conversion (multi language) or for packaging (text description changes). To run these utilities, we need to push the sources to the server and run the utilities. Using compile commands cover these aspects as it pushes the source automatically if it sees a change as compared to user actions which need manual pushing of a source. I have yet to encounter an instance wherein I don't need to push the source when I need to run a certain utility over it.

Having said the above, the true source is basically the one in iSeries since it has the updated source. We then need to download the updated sources in our iProject and commit them to SVN our SCM.

The ulitimate goal, I know, is to create RDi plugins or scripts that will accomplish in RDi what the server based utilities do. We are still looking into it but due to time constraints on the migration, we can't wait for it and had to proceed with running them utilities in the server and downloading the sources back to RDi and finally to SVN.

I hope that clears the confusion.


-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Buck Calabro
Sent: Friday, May 15, 2015 10:04 PM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] Compile commands and iProject property file

On 5/15/2015 9:43 AM, Fajardo, Eduardo wrote:
> Yeah, user action would've been okay but the extra step of pushing the source to the iSeries before running the utilities/commands will not appeal to developers. Flimsy excuse, I know but that's a sad fact.

I thought I understood the issue, but now I'm sure I do not.

> Currently, we create our own "compile" commands to run various home
> grown iSeries based utilities such as source formatting, conversion,
> etc.

I'm trying to understand when I wouldn't want to do a push.  Let's say the command is 'source formatting'.  If I ran a command against the source member on the server, it is working against a stale copy of the source - the true copy is in iProjects, yes?  Wouldn't every command running on the server want to use the up-to-date source?

--
  --buck

--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries  (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l.
"Misys" is the trade name of the Misys group of companies. This email and any attachments have been scanned for known viruses using multiple scanners. This email message is intended for the named recipient only. It may be privileged and/or confidential. If you are not the named recipient of this email please notify us immediately and do not copy it or use it for any purpose, nor disclose its contents to any other person. This email does not constitute the commencement of legal relations between you and Misys. Please refer to the executed contract between you and the relevant member of the Misys group for the identity of the contracting party with which you are dealing.