My main concern is around merging into the dependency plugin that creates a new dependency on a sandboxed item if it's really far away. I'm thinking that it might make sense to keep the analyzer plugin separate until this shared piece can be unsandboxed. If the current version can be unsandboxed and prepared for release if we clearly note in the dependency plugin docs that these goals are very alpha, then that's ok.
What does the PMC think? -----Original Message----- From: Mark Hobson [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 27, 2007 11:09 AM To: Maven Developers List Subject: Re: Re: svn commit: r512016 - /maven/sandbox/trunk/plugins/maven-dependency-plugin/pom.xml On 27/02/07, Brian E. Fox <[EMAIL PROTECTED]> wrote: > How close is the dependency anayzer shared piece from coming out of the sandbox and being released? There's a couple of things I'd like to see before it was released: - write some integration tests to fully verify the bytecode dependency code - abstract the concept of a dependency away from class files and make it pluggable in order to support: classname references in XML files; Java META-INF service files; etc. - javadoc ;) Still, it could be released in it's present form if there's demand to warrant it. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
