You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beehive.apache.org by "Lawrence Jones (JIRA)" <be...@incubator.apache.org> on 2005/01/28 18:14:17 UTC
[jira] Created: (BEEHIVE-209) Need ability to log warnings, errors etc for controls assembly
Need ability to log warnings, errors etc for controls assembly
--------------------------------------------------------------
Key: BEEHIVE-209
URL: http://issues.apache.org/jira/browse/BEEHIVE-209
Project: Beehive
Type: Bug
Components: Controls
Versions: V1Beta
Environment: Windows
Reporter: Lawrence Jones
Currently if something goes wrong or you want to warn the user of something in assembly you have 2 choices:
1. write directly to System.out or System.err
2. raise an exception
At the moment all exceptions are caught in Assembler.assemble(). A stack trace is written to stderr but the exception is not rethrown so AssembleTask looks as though it finishes successfully.
But if that is fixed there is no way to raise a warning or information message without either stopping assembly completely or writing to stdout or stderr directly.
We should provide a Logger interface available via the assembly context to which you can log errors, warnings and info messages at least. And we should provide an implementation of this interface which can be used by default in the AssembleTask.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Closed: (BEEHIVE-209) Need ability to log warnings, errors etc for controls assembly
Posted by "Zach Smith (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-209?page=all ]
Zach Smith closed BEEHIVE-209:
------------------------------
>From a custom Assembler I was able to access a Messenger implementation class via 'ControlAssemblyContext.getMessenger()' and make use of 'printError(String)'. Running the assembler showed the expected error message.
[assemble] Error: (<not available>:0:0) MESSAGER API WORKS OK!!!
> Need ability to log warnings, errors etc for controls assembly
> --------------------------------------------------------------
>
> Key: BEEHIVE-209
> URL: http://issues.apache.org/jira/browse/BEEHIVE-209
> Project: Beehive
> Type: Bug
> Components: Controls
> Versions: V1Beta
> Environment: Windows
> Reporter: Lawrence Jones
> Assignee: Kenneth Tam
> Fix For: v1m1
>
> Currently if something goes wrong or you want to warn the user of something in assembly you have 2 choices:
> 1. write directly to System.out or System.err
> 2. raise an exception
> At the moment all exceptions are caught in Assembler.assemble(). A stack trace is written to stderr but the exception is not rethrown so AssembleTask looks as though it finishes successfully.
> But if that is fixed there is no way to raise a warning or information message without either stopping assembly completely or writing to stdout or stderr directly.
> We should provide a Logger interface available via the assembly context to which you can log errors, warnings and info messages at least. And we should provide an implementation of this interface which can be used by default in the AssembleTask.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (BEEHIVE-209) Need ability to log warnings, errors etc for controls assembly
Posted by "Steve Tocco (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-209?page=history ]
Steve Tocco updated BEEHIVE-209:
--------------------------------
Fix Version: V1
moving to v1 (if not needed for ship, please move to Fix For = TBD)
> Need ability to log warnings, errors etc for controls assembly
> --------------------------------------------------------------
>
> Key: BEEHIVE-209
> URL: http://issues.apache.org/jira/browse/BEEHIVE-209
> Project: Beehive
> Type: Bug
> Components: Controls
> Versions: V1Beta
> Environment: Windows
> Reporter: Lawrence Jones
> Assignee: Kenneth Tam
> Fix For: V1
>
> Currently if something goes wrong or you want to warn the user of something in assembly you have 2 choices:
> 1. write directly to System.out or System.err
> 2. raise an exception
> At the moment all exceptions are caught in Assembler.assemble(). A stack trace is written to stderr but the exception is not rethrown so AssembleTask looks as though it finishes successfully.
> But if that is fixed there is no way to raise a warning or information message without either stopping assembly completely or writing to stdout or stderr directly.
> We should provide a Logger interface available via the assembly context to which you can log errors, warnings and info messages at least. And we should provide an implementation of this interface which can be used by default in the AssembleTask.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Assigned: (BEEHIVE-209) Need ability to log warnings, errors etc for controls assembly
Posted by "Kenneth Tam (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-209?page=history ]
Kenneth Tam reassigned BEEHIVE-209:
-----------------------------------
Assign To: Kenneth Tam
Yes, this would definitely be useful.
> Need ability to log warnings, errors etc for controls assembly
> --------------------------------------------------------------
>
> Key: BEEHIVE-209
> URL: http://issues.apache.org/jira/browse/BEEHIVE-209
> Project: Beehive
> Type: Bug
> Components: Controls
> Versions: V1Beta
> Environment: Windows
> Reporter: Lawrence Jones
> Assignee: Kenneth Tam
>
> Currently if something goes wrong or you want to warn the user of something in assembly you have 2 choices:
> 1. write directly to System.out or System.err
> 2. raise an exception
> At the moment all exceptions are caught in Assembler.assemble(). A stack trace is written to stderr but the exception is not rethrown so AssembleTask looks as though it finishes successfully.
> But if that is fixed there is no way to raise a warning or information message without either stopping assembly completely or writing to stdout or stderr directly.
> We should provide a Logger interface available via the assembly context to which you can log errors, warnings and info messages at least. And we should provide an implementation of this interface which can be used by default in the AssembleTask.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Resolved: (BEEHIVE-209) Need ability to log warnings, errors etc for controls assembly
Posted by "Kenneth Tam (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-209?page=all ]
Kenneth Tam resolved BEEHIVE-209:
---------------------------------
Resolution: Fixed
Fixed as of rev 164906. Added a getMessager() API to the ControlAssemblyContext, which returns an apt Messager for assemblers to log diagnostics.
> Need ability to log warnings, errors etc for controls assembly
> --------------------------------------------------------------
>
> Key: BEEHIVE-209
> URL: http://issues.apache.org/jira/browse/BEEHIVE-209
> Project: Beehive
> Type: Bug
> Components: Controls
> Versions: V1Beta
> Environment: Windows
> Reporter: Lawrence Jones
> Assignee: Kenneth Tam
> Fix For: V1
>
> Currently if something goes wrong or you want to warn the user of something in assembly you have 2 choices:
> 1. write directly to System.out or System.err
> 2. raise an exception
> At the moment all exceptions are caught in Assembler.assemble(). A stack trace is written to stderr but the exception is not rethrown so AssembleTask looks as though it finishes successfully.
> But if that is fixed there is no way to raise a warning or information message without either stopping assembly completely or writing to stdout or stderr directly.
> We should provide a Logger interface available via the assembly context to which you can log errors, warnings and info messages at least. And we should provide an implementation of this interface which can be used by default in the AssembleTask.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira