I understand the second point, but i don't quite follow on the first.
 Could it happen where someone pulls from a different repo and doesn't get
my forked version?  Or how would that happen?


On Thu, Nov 21, 2013 at 11:31 AM, Matt Drees <notifications@github.com>wrote:

> In pom.xml:
>
> > @@ -68,7 +68,7 @@
> >  		<dependency>
> >  			<groupId>com.thetransactioncompany</groupId>
> >  			<artifactId>cors-filter</artifactId>
> > -			<version>1.3.2</version>
> > +			<version>1.9-SNAPSHOT</version>
>
> So, my two cents on dealing with customized forks:
>
>    - give your fork a new version. I'd suggest
>    1.9-SNAPSHOT-cru-response-reset-fix. As is, somebody might
>    accidnetally pull in new 1.9-SNAPSHOT without your fix.
>    - (less important) fork from the 1.8 release instead of a
>    1.9-SNAPSHOT. It's generally better to be using a release version instead
>    of a snapshot.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/CruGlobal/conf-registration-api/pull/85/files#r7829059>
> .
>



-- 
*Ryan Carlson*
Sr Programmer / Analyst
Web App Development
ryan.t.carlson@cru.org