No, not that one, in particular. I'm sure there are quite a few out there. I figured it was a pretty common problem, so I was wondering what the popular solution was.
Jim -----Original Message----- From: Wim Deblauwe [mailto:[EMAIL PROTECTED] Sent: Fri 4/20/2007 9:59 AM To: Maven Users List Subject: Re: My plugin maintainer died Are you talking about the launch4j plugin? Because I seem to have the same situation there. I tried emailing the author already 2 times, but no luck. regards, Wim 2007/4/20, Crossley, Jim <[EMAIL PROTECTED]>: > > Or at least, so it seems. Only SNAPSHOT versions of the plugin upon which > my project depends have ever been released, and I need to cut a release of > my project. The release plugin won't let me as long as I depend on a > SNAPSHOT plugin. I understand why, but I'm wondering which best practice > addresses "plugin maintainer death". > > My workaround was to grab the source, change the version in its pom and > deploy to my local repository, but I felt moist and dirty afterwards. Is > there a better way? > > Thanks, > Jim > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Vigilog - an open source log file viewer: http://vigilog.sourceforge.net Blog: http://www.jroller.com/page/Fester
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]