>-----Original Message----- >From: Marlon Pierce [mailto:[email protected]] >Sent: Thursday, August 04, 2011 3:17 PM >To: [email protected] >Subject: [discuss] non-default service implementations in svn > >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA1 > >I'd like to extend the DefaultUserService.java for some upcoming Rave-based >projects. Would there be objections to putting such things in the Apache >SVN, under rave/trunk/rave-extensions, for example?
Maybe not under trunk. But a different directory all together? > > >Pro: would provide examples for customizing and extending Rave, especially >for those not familiar with Spring; would be applicable to a defined developer >community (XSEDE Science Gateways) I'd like to attract to the project. > > >Con: "extensions" are a slippery slope, could become a mess of disjointed >code fragments out of sync with the main code base. I think it depends on how complete the solution is. If you are going to have an entire set of classes that override/extend default Rave implementations, but are all in support of the same purpose (science gateways), then I could see making the case that there is a science gateway extension. Otherwise, it would just be example code, IMO. > > >Marlon > >-----BEGIN PGP SIGNATURE----- >Version: GnuPG/MacGPG2 v2.0.16 (Darwin) >Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > >iQEcBAEBAgAGBQJOOvAOAAoJEEfVXEODPFIDgE4H/3d37ptn48zT3sP9NxLz8Af >V >u8jPVKQ9TWevieCgTlI9cbgGrfIrdu/aX1sQBdZiUCulCwp0Vd1fGvJWbFuNfYzY >mNvnb7f4WrxM6uqqs8FpLUyek6SBrVc3ZJfyjV1Aq9ejqWDShQJhNkVNd1qdE >yEn >9OVm7aEnTjNroxO1hKUF7fzDktsdghBUlDkIxRT6M2V66sOYNNb61jbD0SoBDm >ZP >V1PV5ueK0Yu6S4LD0Y3YspWlUo7q50ktx3LCb/pCZyIG+nh9Q9ADB3bggllmn+T >+ >0VswKgTqd0ASI3WGEqokQTJ0+Uh0rpKIHqTMeb+CY0W72ch9op655TNxVf4fI >Og= >=0IkE >-----END PGP SIGNATURE-----
