Hi Matt,


2. I develop several different projects in my one library but i Projects treats libraries as a single project so I cannot just sync the two environments.
I've never had any problems using the same library for multiple projects, except for the build CL, which I copy and maintain manually anyway after the initial creation. It would be nice if the build script name could be chosen per project.

4. Quick change, compile, test cycles were difficult.
You can still compile objects one at a time (or even multiple sources) in a project that uses a BUILD CL.

5. Source dates are wiped clean and replaced by current value.
For me, using Git pretty much makes this redundant as will the move to IFS source file eventually, but it sounds like you don't have that luxury.

It would be really nice to move away from source physical files completely, but iProjects don't support the IFS in the same way as they do PFs as far as I can tell.

Tim.

________________________________
From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxx> on behalf of Tyler, Matt <matt.tyler@xxxxxxxxxxxxxx>
Sent: 20 April 2017 00:55
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Cc: Rob Cecco
Subject: Re: [WDSCI-L] Feedback on iProjects - good, bad and ugly

It been many years since I actively use i Projects

1. Build command, program option is difficult. I could not just set it how I want it was always recreating the build script.
2. I develop several different projects in my one library but i Projects treats libraries as a single project so I cannot just sync the two environments.
3. I only develop when I am connected to our server so I really don't need remote capabilities.
4. Quick change, compile, test cycles were difficult.
5. Source dates are wiped clean and replaced by current value.
6. Some tools like RPG Tool box are useless because it cannot connect to a server.
7. There may be more but I don't really use it.
8. i Projects does not integrate with our CMS Rocket Aldon.
9. I rarely import OSS projects but I have used i Projects to do so at least for the upload part.

-Matt

-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Edmund Reinhardt
Sent: Wednesday, April 19, 2017 4:21 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Cc: Rob Cecco <cecco@xxxxxxxxxx>
Subject: [WDSCI-L] Feedback on iProjects - good, bad and ugly

As RDi architect, I want to make sure that I don't get out of touch with your experience in using RDi in the trenches.
For example, I might think that i Projects are a perfect way for people to be able to use Git on IBM i and maybe I am missing some reason why people are not adopting i Projects.
So please set me straight.
Who is using i Projects and if so how do you like it?
If you have tried i Projects and abandoned them, let me know why?

I am very thankful to have access to such a vocal group of customers that I can get unfiltered, immediate feedback from.

Thanks
Edmund
--
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.
--
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.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 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.