Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Auto Closed
-
3.0.4
-
None
-
None
-
Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
Maven home: C:\Program Files (x86)\Maven-3.0.4\bin\..
Java version: 1.6.0_30, vendor: Sun Microsystems Inc.
Java home: C:\Program Files\Java\jdk1.6.0_30\jre
Default locale: fr_FR, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100) Maven home: C:\Program Files (x86)\Maven-3.0.4\bin\.. Java version: 1.6.0_30, vendor: Sun Microsystems Inc. Java home: C:\Program Files\Java\jdk1.6.0_30\jre Default locale: fr_FR, platform encoding: Cp1252 OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
Description
I'm working on a maven growl extension (https://github.com/Riduidel/maven-growl-plugin) that should send growl notification based upon project lifecycle.
Typical use case is to receive a growl notification when build is over.
According to discussion with olamy, there currently can be only one execution listener in maven. What's more, some code has to be added to execution listener class if one want these listeners calls to be chained.
Like in Swing for all event listeners, it should be possible to have more than one listener, and those listeners management should be handled by maven itself, and not by the listener.