You are viewing a plain text version of this content. The canonical link for it is here.
Posted to m2-dev@maven.apache.org by ji...@codehaus.org on 2005/02/07 09:20:20 UTC

[jira] Created: (MNG-128) logging and events

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/browse/MNG-128

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MNG-128
    Summary: logging and events
       Type: Improvement

     Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: m2
   Fix Fors:
             1.0-alpha-1

   Assignee: 
   Reporter: Brett Porter

    Created: Mon, 7 Feb 2005 3:19 AM
    Updated: Mon, 7 Feb 2005 3:19 AM

Description:
need to have a method for logging from m2 and mojos. Base it on an event structure so that it can be embedded easily and provide feedback.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


[jira] Commented: (MNG-128) logging and events

Posted by ji...@codehaus.org.
The following comment has been added to this issue:

     Author: John Casey
    Created: Mon, 28 Feb 2005 1:42 PM
       Body:
What events do we want propagated through to listeners?

My ideas:

mojo
===============
1/ start
2/ stop
3/ error
4/ status?

lifecycle-phase
===============
1/ start
2/ stop
3/ error
4/ status?

build
===============
1/ start
2/ stop
3/ error
4/ status?

Where 'status' might simply report the statistics for execution of that part of the build. 

Also, do we want to integrate notions of {info|debug|warn|error} into a logging/monitoring framework here? If so, do we want to use some sort of adapter to a common framework (jdk-logging, f.e.)?

I basically need to put together a design doc for this, and so I need to discuss the requirements in more detail with you guys.
---------------------------------------------------------------------
View this comment:
  http://jira.codehaus.org/browse/MNG-128?page=comments#action_30372

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/browse/MNG-128

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MNG-128
    Summary: logging and events
       Type: Improvement

     Status: Open
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: m2
 Components: 
             design
   Fix Fors:
             1.0-alpha-1

   Assignee: John Casey
   Reporter: Brett Porter

    Created: Mon, 7 Feb 2005 3:19 AM
    Updated: Mon, 28 Feb 2005 1:42 PM

Description:
need to have a method for logging from m2 and mojos. Base it on an event structure so that it can be embedded easily and provide feedback.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


[jira] Work started: (MNG-128) logging and events

Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-128?page=history ]
     
Work on MNG-128 started by John Casey

> logging and events
> ------------------
>
>          Key: MNG-128
>          URL: http://jira.codehaus.org/browse/MNG-128
>      Project: m2
>         Type: Improvement
>   Components: design
>     Reporter: Brett Porter
>     Assignee: John Casey
>      Fix For: 1.0-alpha-1

>
>
> need to have a method for logging from m2 and mojos. Base it on an event structure so that it can be embedded easily and provide feedback.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/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: (MNG-128) logging and events

Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-128?page=history ]
     
John Casey resolved MNG-128:
----------------------------

    Resolution: Fixed

basic support is implemented. Artifact stuff may need integration with event handler for unified output.

> logging and events
> ------------------
>
>          Key: MNG-128
>          URL: http://jira.codehaus.org/browse/MNG-128
>      Project: m2
>         Type: Improvement
>   Components: design
>     Reporter: Brett Porter
>     Assignee: John Casey
>      Fix For: 1.0-alpha-1

>
>
> need to have a method for logging from m2 and mojos. Base it on an event structure so that it can be embedded easily and provide feedback.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


[jira] Updated: (MNG-128) logging and events

Posted by ji...@codehaus.org.
The following issue has been updated:

    Updater: Brett Porter (mailto:brett@codehaus.org)
       Date: Mon, 7 Feb 2005 8:45 PM
    Changes:
             Component changed to design
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://jira.codehaus.org/browse/MNG-128?page=history

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/browse/MNG-128

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MNG-128
    Summary: logging and events
       Type: Improvement

     Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: m2
 Components: 
             design
   Fix Fors:
             1.0-alpha-1

   Assignee: 
   Reporter: Brett Porter

    Created: Mon, 7 Feb 2005 3:19 AM
    Updated: Mon, 7 Feb 2005 8:45 PM

Description:
need to have a method for logging from m2 and mojos. Base it on an event structure so that it can be embedded easily and provide feedback.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/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: (MNG-128) logging and events

Posted by ji...@codehaus.org.
Message:

   The following issue has been re-assigned.

   Assignee: John Casey (mailto:jdcasey@commonjava.org)
---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/browse/MNG-128

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MNG-128
    Summary: logging and events
       Type: Improvement

     Status: Open
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: m2
 Components: 
             design
   Fix Fors:
             1.0-alpha-1

   Assignee: John Casey
   Reporter: Brett Porter

    Created: Mon, 7 Feb 2005 3:19 AM
    Updated: Sun, 27 Feb 2005 7:26 PM

Description:
need to have a method for logging from m2 and mojos. Base it on an event structure so that it can be embedded easily and provide feedback.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira