Bug 176251 - Need a log of builders run on rebuild
Summary: Need a log of builders run on rebuild
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: eclipse
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Andrew Overholt
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-12-20 16:45 UTC by Thomas Fitzsimmons
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-02-03 16:10:00 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Eclipse Project 121591 0 None None None Never

Description Thomas Fitzsimmons 2005-12-20 16:45:05 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050922 Fedora/1.0.7-1.1.fc4 Firefox/1.0.7

Description of problem:
When building the classpath project in native eclipse, it would be useful if eclipse kept a log of the builders it ran.  We have custom builders that run autogen.sh, configure, make distclean and make -C native/ all install.  Though the console title bar indicates the currently-running builder, some builders run very quickly so it is hard to tell which ones were run.  For debugging and informational purposes, it would be helpful if eclipse logged a list of builders it ran in the order that it ran them.  The log would also have to mark the start and end of each build run in case some builders are run twice.


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. build classpath
2. try to see which builders are being run


Additional info:

Comment 1 Andrew Overholt 2005-12-20 16:54:04 UTC
While I fully agree, this should probably be filed upstream.

Comment 2 Thomas Fitzsimmons 2005-12-20 17:19:11 UTC
Mirrored upstream.


Comment 3 Andrew Overholt 2006-02-03 16:10:00 UTC
Let's just track this upstream.


Note You need to log in before you can comment on or make changes to this bug.