I was involved with the Sourceforge project Ted mentioned, as well as having a couple of S2 plugins in the registry now... my question, which I had for the Sourceforge project too, was why not host this at Apache and have it under Struts itself? If we're talking about CLAs for GC contributions now too, I'm not sure I see the difference. If it's a question of perception, i.e., if it's external than no plugin is officially endorsed or anything, that seems to run contrary to listing developers and all that's being talked about here. I can't imagine there's infrastructure issues that couldn't be dealt with.
Why wouldn't/couldn't/shouldn't/*dn't this be put officially under the Struts umbrella and hosted alongside Struts itself? Frank -- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com AIM/Yahoo: fzammetti MSN: [EMAIL PROTECTED] Author of "Practical Ajax Projects With Java Technology" (2006, Apress, ISBN 1-59059-695-1) and "JavaScript, DOM Scripting and Ajax Projects" (2007, Apress, ISBN 1-59059-816-4) Java Web Parts - http://javawebparts.sourceforge.net Supplying the wheel, so you don't have to reinvent it! On Tue, November 27, 2007 8:48 am, Tom Schneider wrote: > I think having separate googlecode projects for each plugin has worked > well up to this point. Creating a googlecode project is quick and > easy. Googlecode seems to be designed to have a lot of really small > projects, rather than one big projects with many subprojects. The one > thing that ties everything together is the plugin registry. If > anything, I'd rather see that expanded. Maybe add a list of developers > to the plugin registry. I think the apache developers would feel more > obligated to maintain something hosted on Apache as opposed to something > hosted on googlecode. As you may be able to tell, not a lot of the > googlecode plugin sites have a ton of content. The only reason I > created a common maven repository is so that end users only have to add > one plugin repository to get access to most of the plugins. > > Ted Husted wrote: >> Very cool, Tom. >> >> Has anyone started a shared GoogleCode project for Struts 2 plugins yet? >> >> The notion being that instead of everyone starting up one-off >> projects, we could have one GC project that anyone with a Google ID >> could join and use to maintain a "third-party" Struts 2 plugin -- a >> Struts 2 Plugin Commons. >> >> Of course, the group could still have a select group of owners that >> could remove someone who joined and then turned out to be a troll. >> >> -Ted. >> >> On Nov 25, 2007 10:12 AM, Tom Schneider <[EMAIL PROTECTED]> wrote: >> >>> Hey all, >>> I finally figured out a way to host a maven repository on googlecode. >>> This should greatly simplify using googlecode hosted plugins in Struts >>> 2. For me, it's also much nicer to use maven to deploy than trying to >>> get a jar manually uploaded into the central repository. Instructions >>> on how to use this repo for Struts 2 projects are at: >>> http://code.google.com/p/struts2plugin-maven-repo/ >>> >>> Anyone who has a plugin hosted at googlecode can use this maven >>> repository to host their plugin. (I've already added several >>> developers >>> that I know of, if your not in the list let me know) I've also already >>> added several of my more popular plugins. I plan on adding the rest as >>> time permits. Please look at the scope plugin (on googlecode) for an >>> example of how to configure maven to deploy to this repository. >>> Tom >>> >> >> --------------------------------------------------------------------- >> 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
