+1
On 21-Jan-09, at 4:17 PM, Oleg Gusakov wrote:
Logistics were sorted out, here we go:
This is iterative improvements release of Mercury.
Most important are:
- repository exception handling adjusted for clearer client
notifications. For example - absence of metadata did produce NPE
result, now it throws a checked exception
- plexus component now correctly resolves multiple artifacts, not
just one as it used to
- put Mercury on a diet - made encryption optional, factored out
jetty server artifact
7 issues fixed: http://jira.codehaus.org/browse/MERCURY/fixforversion/14748
One known issue will be fixed in maven-mercury component -
[MERCURY-75]
Staged release in repository at
http://people.apache.org/~ogusakov/repos/staging/
Site at http://people.apache.org/~ogusakov/sites/mercury
Vote open for 72 hours.
[ ] +1
[ ] +0
[ ] -1
Thanks,
Oleg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
People develop abstractions by generalizing from concrete examples.
Every attempt to determine the correct abstraction on paper without
actually developing a running system is doomed to failure. No one
is that smart. A framework is a resuable design, so you develop it by
looking at the things it is supposed to be a design of. The more
examples
you look at, the more general your framework will be.
-- Ralph Johnson & Don Roberts, Patterns for Evolving Frameworks
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
