> -----Original Message----- > From: Niclas Hedhman [mailto:[EMAIL PROTECTED] > > I also want to point out that Merlin itself will remain compatible, but I > will not issue a guarantee that any 3rd party code using the Avalon > Repository directly will remain compatible. I happen to believe there > ain't many other projects/products that depends on Avalon Repository > directly, so no point making compatibility a requirement. And where it > becomes an issue, we would need to provide wrappers in the old package > names, blah blah blah... not really a difficult issue.
There are not many other users, yet. I've thought about it a couple of times. Avalon-Repository solves basically the same problem as Java WebStart and JNLP but IMHO does a much better job of it. And I think "marketing" it as an alternative to Java WebStart and looking to provide more functionality of JWS would be great. I think this could happen better in Depot where the repository project would be more visible and not overshadowed as a small component of Merlin. So in general, I like the idea. My only concern is with Depot's future. Have they decided if they're going to shoot for a TLP? Or be part of Jakarta Commons or Apache Commons? That would really be my only concern with this move. J. Aaron Farr SONY ELECTRONICS STP SYSTEMS (724) 696-7653 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
