[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-dev] Making Save Build Console more straightforward
|
+1 from me
That workflow sounds much more usable.
===========================
Chris Recoskie
Team Lead, IBM CDT and RDT
IBM Toronto
![Inactive hide details for Andrew Gvozdev ---05/18/2010 10:22:31 PM---It is kind of late in build cycle but I think we gotta cor]()
Andrew Gvozdev ---05/18/2010 10:22:31 PM---It is kind of late in build cycle but I think we gotta correct this. New "Save Build Console" featur
![]()
From: | ![]()
Andrew Gvozdev <angvoz.dev@xxxxxxxxx> |
![]()
To: | ![]()
"CDT General developers list." <cdt-dev@xxxxxxxxxxx> |
![]()
Date: | ![]()
05/18/2010 10:22 PM |
![]()
Subject: | ![]()
[cdt-dev] Making Save Build Console more straightforward |
![]()
Sent by: | ![]()
cdt-dev-bounces@xxxxxxxxxxx |
It is kind of late in build cycle but I think we gotta correct this. New "Save Build Console" feature added in bug 294106 is a wanted feature but it is implemented in an awkward way from user point of view. The current workflow requires user to setup logging in properties before build occurs. It is prone to accidental overwriting as new build will overwrite the old log silently.
My suggestion is attached to bug 306222. It changes "Save Build Console" to straightforward flow:
1. User runs builds
2. User spots interesting output and clicks "Save Output" button saving the build log in chosen file via file selection dialog.
Additional bonus that it will work with non-C projects (builders that not aware of CDT configurations).
I think we better include the change to 7.0 now before the users develop a habit.
Andrew
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
