Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tigerstripe-dev] Project Errors
Title: Re: [tigerstripe-dev] Project Errors
This is exactly the purpose of Bug 221966. It will happen but requires quite a bit of change.
I’ve posted a tentative release plan (http://wiki.eclipse.org/Tigerstripe_0.3_stream). This would place the fix in M1.

Eric

On 4/10/08 6:30 AM, "Duncan Keysell (dkeysell)" <dkeysell@xxxxxxxxx> wrote:

We really need the auditor to be run during a headless build (particularly to handle the facet issue described below). Our build validation process is partly based on the incorrect assumption that the auditor did already run as part of the build - because on several occasions we have not added rules to the validation plugin based on the logic that the rule would already be enforced by the auditor.
Duncan

From: tigerstripe-dev-bounces@xxxxxxxxxxx [mailto:tigerstripe-dev-bounces@xxxxxxxxxxx] On Behalf Of Richard Craddock (rcraddoc)
Sent: 10 April 2008 14:22
To: Tigerstripe developers list
Subject: [tigerstripe-dev] Project Errors

When a project contains errors (that are picked up by the auditor) the user is prompted that they exist and asked if they wish to continue.
However when running headless, the audit checks are not run (they are part of the UI) and so there is no record that anything might have been amiss. This can make debugging of builds a bit difficult.
A recent example is when a facet is in error (possibly due to a refactor), and no longer matches anything in the project. This can be seen if you apply the facet in the GUI, but there is no evidence in the logs anywhere.
 
How can we capture this kind of information for debugging purposes?
RC

_______________________________________________
tigerstripe-dev mailing list
tigerstripe-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tigerstripe-dev

Back to the top