Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PCTCompile / PCTCompileEx - display program name to be compiled #5

Closed
GoogleCodeExporter opened this issue Mar 28, 2015 · 4 comments
Closed

Comments

@GoogleCodeExporter
Copy link

Hi,

I'd like to propose an enhancement to PCTCompile / PCTCompilExt to print out 
the program name to be compiled, just like the PROGRESS Compiler does.

Maybe this could be controller by a new attribute verbose="true" or displayed 
all the time, I don't care really as long as it gets displayed.

Thanks,
Dan

pctBgCompile.p
line 275:
RUN logInfo IN ipSrcProc (SUBSTITUTE("Compiling &1", inputFile)).


Buildfile: C:\Temp\pct-test\build.xml

test:
[PCTCompileExt] PCTCompile - Progress Code Compiler
[PCTCompileExt] Compiling c:\temp\pct-test\test.p
[PCTCompileExt] Compiling c:\temp\pct-test\test2.p
[PCTCompileExt] 2 file(s) compiled

BUILD SUCCESSFUL
Total time: 2 seconds

Original issue reported on code.google.com by dan.dra...@gmail.com on 30 Jul 2011 at 8:49

@GoogleCodeExporter
Copy link
Author

Just wondering if it's better to use RUN logVerbose and so be able to display 
using ant -v, or add a verbose flag in PCTCompileExt and display this 
information with INFO log level. I'm more inclined on logVerbose.

Original comment by g.quer...@gmail.com on 1 Aug 2011 at 6:36

  • Changed state: Accepted
  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

I pushed the logVerbose patch. Can you try Hudson build #148 ?

Original comment by g.quer...@gmail.com on 3 Aug 2011 at 9:59

  • Changed state: Fixed
  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

Thanks Gilles,

I've just setup Jenkins yesterday - I'll take down your changes and try them on.

I had more suggestions for verbose on the compile task like printing the 
PROPATH and PROGRESS versions, things that I've done through Ant code but I'd 
rather see them done by the PCTCompile task itself.

I'll come back with more details.

Thanks,
Dan

Original comment by dan.dra...@gmail.com on 4 Aug 2011 at 8:26

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

Hi,

I think -v outputs a bit too much technical information from Ant - I might make 
a change in my clone to introduce a verbose property and see how that goes and 
propose it for review later.

I've got other things that I'd like to display in verbose mode, like PROPATH 
used and db connection parameter (DB-PARAMS) and maybe other things.

Thanks,
Dan

Original comment by dan.dra...@gmail.com on 13 Aug 2011 at 8:52

  • Added labels: ****
  • Removed labels: ****

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant