+1 to release a beta then
+1 componentize it On 9/13/06, Brian E. Fox <[EMAIL PROTECTED]> wrote:
I think you may be right about a shared component. Most of the refactoring from 1.0 to 2.0 has been around cleaning up the plugin and creating some more generic objects to allow better code reuse and paramater consistency among the various mojos in this plugin. My main concern right now is to get something released that works in place of 1.0. Since the plugin moved and nothing new was released since then, it creates a bunch of confusion. Before I do the release I'd like to get some form of integration tests in place. My trouble is that I can't find a good example of integration tests in plugins that rely on local and remote repositories. Once the release is done I think it would be worth looking at making this code shared. It probably means more overall work to release first, but at least we have a semi functional dependency plugin in the meantime. -----Original Message----- From: Jason van Zyl [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 13, 2006 4:23 AM To: Maven Developers List Subject: Re: dependency plugin? On 12 Sep 06, at 4:17 AM 12 Sep 06, Brian E. Fox wrote: > Must have been a psychic connection here. I finally started working on > this tonight and have resolved many issues before seeing this email. I > have also finally been using 2.0 in production with no problems...it's > at least as stable as 1.0 from what I can tell. Once I get the > existing patches applied and any low hanging fruit, I'd suggest an > ALPHA release. > I will need to come back and finish up the new goals that where added > into 1.1 and get unit tests in place for them. > If the goal is try try and make some useful dependency management tools with this mojo why don't you make it a Plexus component which can easily be reused in other mojos? I think composition is generally more useful then inheritance. And it may end up that you have a set of components that help with dependencies instead of trying to wedge everything into one mojo. It seems to me that you're really trying to make a toolbox for people to use when it comes to dependencies. Maybe something suitable for maven-shared. > -----Original Message----- > From: dan tran [mailto:[EMAIL PROTECTED] > Sent: Sunday, September 10, 2006 2:49 AM > To: Maven Developers List > Subject: Re: dependency plugin? > > I have been using it in my production build ( I cut an internal > release of this plug) Please dont make it to go back to the mojo > version. > > Suggest to cut a beta for this plugin with current state of doc to get > more visibility. > > -Dan > > > > On 9/9/06, Brett Porter <[EMAIL PROTECTED]> wrote: >> >> Anyone know what the plan is for this? I thought I saw documentation >> improvements checked in last week, but see it is still a problem. >> >> Should we remove it's documentation from the Maven site, push it back >> to the sandbox and link to the codehaus version until it sees a > release? >> >> - Brett >> >> --------------------------------------------------------------------- >> 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] > > Jason van Zyl [EMAIL PROTECTED] --------------------------------------------------------------------- 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]
