yes, I did cut a sureplugin release my self at work, however since you are an apache project, dont think you can release Cayenne with a private copy of surefire.
Perhaps you can file a JIRA to release 2.5, i am sure lots of folks will vote for it, that will get attention. -Dan On Sun, Oct 11, 2009 at 10:01 PM, Andrey Razumovsky <razumovsky.and...@gmail.com> wrote: > Well, we can if we want to - we have a repository which can be used for such > artifacts. So you advice to make a *local* copy of 2.5-SNAPSHOT and use it > until official 2.5 is released? > > Thanks, > > 2009/10/12 Dan Tran <dant...@gmail.com> > >> since Apache Cayenne cant just fork its own copy of surefire plugin, i >> think releasing 2.5 is badly needed. >> >> -D >> >> On Sun, Oct 11, 2009 at 4:26 PM, Barrie Treloar <baerr...@gmail.com> >> wrote: >> > On Mon, Oct 12, 2009 at 5:48 AM, Andrey Razumovsky >> > <razumovsky.and...@gmail.com> wrote: >> >> Hello, >> >> >> >> While enchancing our Hudson builds here at Apache Cayenne, we got bitten >> by >> >> SUREFIRE-551. It is now fixed, but doesn't exist in any released >> version. >> >> We've found the snapshot in http://repository.apache.org/snapshots/. So >> our >> >> questions are: >> >> 1. Is 2.5-SNAPSHOT stable enough? >> >> 2. Can we rely on http://repository.apache.org/snapshots/ repository in >> our >> >> builds (i.e. aren't there any plans to delete snapshot from that repo)? >> >> 3. When official 2.5 will be released? >> >> >> >> Thanks, >> >> Andrey >> >> >> > >> > For 1) & 2) NEVER rely on snapshots for your builds. >> > >> > There are a number of problems with using the snapshot repository. >> > 1) You can't select which snapshots to use, it is all or nothing. So >> > if you aren't following best practice and locking down plugin versions >> > then you will automatically start using snapshot versions when you >> > didnt want to. >> > 2) Snapshots get rebuilt so it may work one day and fail the next. >> > >> > I wrote up the steps I use for this scenario >> > http://docs.codehaus.org/display/MAVENUSER/Patching+Maven+Plugins >> > >> > Essentially you take a copy of the source and build a local version of >> > the plugin. >> > If you use a suitable numbering scheme when the official release >> > arrives it will replace your patched version. >> > >> > I can't answer 3) for you. >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> > For additional commands, e-mail: users-h...@maven.apache.org >> > >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >> > > > -- > Andrey > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
