Dear All,
This is the first release of Mercury with all major [mercury] functionality enabled: repository access + dependency resolution. You can try using it for resolving artifacts and then writing them into a local repo in a standalone application, event system helps to understand what is goin
Thanks for catching this one,
Oleg
Brett Porter wrote:
On 08/12/2008, at 11:46 AM, [EMAIL PROTECTED] wrote:
- maven-release-plugin
- 2.0-beta-7
-
-
https://svn.apache.org/repos/asf/maven/mercury/tags
-true
-
-
On 08/12/2008, at 11:46 AM, [EMAIL PROTECTED] wrote:
- maven-release-plugin
- 2.0-beta-7
-
-https://svn.apache.org/repos/asf/maven/mercury/tags
-true
-
-
did you intend to roll this back too? Also the
A patch would be great!
Sent from my iPhone
On Dec 7, 2008, at 1:36 AM, "Arnaud HERITIER" <[EMAIL PROTECTED]>
wrote:
Hi,
Our reports on votes are down :
http://www.sonatype.org/~j2ee-hudson/reports/
https://ci.sonatype.org/view/Reports/
It's certainly a Jira upgrade which broke the xml-
being able to bind to the front and back of a lifecycle would be
absolutely
splendid
+1. A simple event system which fired build events to registered
listeners (plugins could register these) would go a long way. Example
events could be:
* Build Started
* Phase Started
* Goal Started
*
