Re: Googlecode Maven Repository for External Struts 2 Plugins

2007-11-27 Thread Ted Husted
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

Re: Googlecode Maven Repository for External Struts 2 Plugins

2007-11-27 Thread Philip Luppens
On 11/27/07, Ted Husted [EMAIL PROTECTED] 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

Re: Googlecode Maven Repository for External Struts 2 Plugins

2007-11-27 Thread Ted Husted
On Nov 27, 2007 4:21 AM, Philip Luppens [EMAIL PROTECTED] wrote: By this 'commons' project, do you mean that (some of) these projects should become consolidated (thus giving up their own googlecode page) ? Or would it just be a listing with news and information (=plugin registry), and a global

Re: Googlecode Maven Repository for External Struts 2 Plugins

2007-11-27 Thread Ted Husted
On Nov 27, 2007 3:54 AM, Ted Husted [EMAIL PROTECTED] wrote: 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,

Re: Googlecode Maven Repository for External Struts 2 Plugins

2007-11-27 Thread Philip Luppens
On 11/27/07, Ted Husted [EMAIL PROTECTED] wrote: On Nov 27, 2007 4:21 AM, Philip Luppens [EMAIL PROTECTED] wrote: By this 'commons' project, do you mean that (some of) these projects should become consolidated (thus giving up their own googlecode page) ? Or would it just be a listing with

Re: Googlecode Maven Repository for External Struts 2 Plugins

2007-11-27 Thread Tom Schneider
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

Re: Googlecode Maven Repository for External Struts 2 Plugins

2007-11-27 Thread Martin Cooper
On Nov 27, 2007 1:21 AM, Philip Luppens [EMAIL PROTECTED] wrote: On a side note: what could be useful would be an overview of all plugin developers and their contact details, so that when a new project gets started, they can be added and/or contacted when required. It could be nice to get an

Re: Googlecode Maven Repository for External Struts 2 Plugins

2007-11-27 Thread Frank W. Zammetti
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

Re: Googlecode Maven Repository for External Struts 2 Plugins

2007-11-27 Thread Dave Newton
Licensing? I don't want to encourage a situation where there's a perception of golden plugins vs. everything else, and I'd assume (perhaps incorrectly) that projects hosted under the Apache umbrella would have to be Apache-licensed. d. --- Frank W. Zammetti [EMAIL PROTECTED] wrote: I was

Re: Googlecode Maven Repository for External Struts 2 Plugins

2007-11-27 Thread Philip Luppens
On 11/27/07, Frank W. Zammetti [EMAIL PROTECTED] wrote: 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

Re: Googlecode Maven Repository for External Struts 2 Plugins

2007-11-27 Thread Frank W. Zammetti
On Tue, November 27, 2007 11:02 am, Dave Newton wrote: Licensing? The licensing issue, which Phil mentioned too, could be... I'm not sure what the policy is around that, i.e., can a project hosted at Apache have a non-ASL license? I'm not at all sure that's insurmountable though even if it's

Re: Googlecode Maven Repository for External Struts 2 Plugins

2007-11-27 Thread Frank W. Zammetti
The other fairly obvious concern that I thought of after that last reply is how to deal with plugin authors... if these third-party plugins are hosted at Apache, their authors clearly would need some degree of commit priveleges to their own code bases. There's two ways I could see to deal with

Re: Googlecode Maven Repository for External Struts 2 Plugins

2007-11-27 Thread Philip Luppens
On 11/27/07, Frank W. Zammetti [EMAIL PROTECTED] wrote: The other fairly obvious concern that I thought of after that last reply is how to deal with plugin authors... if these third-party plugins are hosted at Apache, their authors clearly would need some degree of commit priveleges to their

Re: Googlecode Maven Repository for External Struts 2 Plugins

2007-11-27 Thread Ted Husted
On Nov 27, 2007 11:22 AM, Frank W. Zammetti [EMAIL PROTECTED] wrote: It may be nothing more than a matter of perception and nothing more, but I think externally-hosted projects will automatically have a connotation of not being golden as you say, no matter what else is done to say otherwise,

Re: Googlecode Maven Repository for External Struts 2 Plugins

2007-11-27 Thread Wendy Smoak
On 11/25/07, 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

Re: Googlecode Maven Repository for External Struts 2 Plugins

2007-11-27 Thread Frank W. Zammetti
I don't disagree with most of what you say here, and what Phillip says in his reply, so let me make a more concrete suggestion: make the plugin registry much more prominent on the Struts home page (that is to say, mention it at all, since I don't see it on the front page anywhere at present).

Re: Googlecode Maven Repository for External Struts 2 Plugins

2007-11-27 Thread Philip Luppens
On 11/27/07, Frank W. Zammetti [EMAIL PROTECTED] wrote: I don't disagree with most of what you say here, and what Phillip says in his reply, so let me make a more concrete suggestion: make the plugin registry much more prominent on the Struts home page (that is to say, mention it at all, since

Re: Googlecode Maven Repository for External Struts 2 Plugins

2007-11-27 Thread Matt Raible
Marketing is easy - finding the time to do it is the hard part. Maybe someone should write a Developer Works article on Struts Plugins? I say DW because it seems to have the widest reach among online articles. I have connections if anyone is interested in doing this. I'd also like to see Don

Re: Googlecode Maven Repository for External Struts 2 Plugins

2007-11-27 Thread Frank W. Zammetti
On Tue, November 27, 2007 12:15 pm, Philip Luppens wrote: On 11/27/07, Frank W. Zammetti [EMAIL PROTECTED] wrote: I don't disagree with most of what you say here, and what Phillip says in his reply, so let me make a more concrete suggestion: make the plugin registry much more prominent on the

Re: Googlecode Maven Repository for External Struts 2 Plugins

2007-11-27 Thread Ted Husted
Were you thinking of a roundup, or an article on a specific plugin, or something about to roll your own? I do have an aticle about the SmartURLs plugin pending with TSS. I've also been thinking of trying a JPA plugin of my own. There wouldn't be much to it, so it could also be a how-to. But,

Re: Googlecode Maven Repository for External Struts 2 Plugins

2007-11-27 Thread Matt Raible
If we're focusing on plugins and trying to build a community/ecosystem around them, it's probably best to write an article about how to roll your own. Part of that article could certainly include dissecting an existing plugin. I'll e-mail you privately with my Developer Works contact. Matt On

Re: Googlecode Maven Repository for External Struts 2 Plugins

2007-11-27 Thread Philip Luppens
On 11/27/07, Matt Raible [EMAIL PROTECTED] wrote: Marketing is easy - finding the time to do it is the hard part. Maybe someone should write a Developer Works article on Struts Plugins? I say DW because it seems to have the widest reach among online articles. I have connections if anyone is

Re: Googlecode Maven Repository for External Struts 2 Plugins

2007-11-27 Thread Philip Luppens
On 11/27/07, Frank W. Zammetti [EMAIL PROTECTED] wrote: On Tue, November 27, 2007 12:15 pm, Philip Luppens wrote: On 11/27/07, Frank W. Zammetti [EMAIL PROTECTED] wrote: I don't disagree with most of what you say here, and what Phillip says in his reply, so let me make a more concrete

Re: Googlecode Maven Repository for External Struts 2 Plugins

2007-11-27 Thread Musachy Barroso
We do need an article explaining how to write plugins, specially how to create tags in those plugins. People email me a lot asking how to get started with a plugin. musachy On Nov 27, 2007 12:35 PM, Philip Luppens [EMAIL PROTECTED] wrote: On 11/27/07, Matt Raible [EMAIL PROTECTED] wrote:

Re: Googlecode Maven Repository for External Struts 2 Plugins

2007-11-27 Thread Frank W. Zammetti
Ok, there appears to be an issue with the site then... when I view it in Macthon, my browser of choice, I don't see the buttons. In FF I see them just fine. I tried in IE7 as well and I see the same thing as Maxthon (which makes sense, since Maxthon is just a wrapper around IE). I fiddled with

Re: Googlecode Maven Repository for External Struts 2 Plugins

2007-11-27 Thread Ted Husted
On Nov 27, 2007 12:35 PM, Philip Luppens [EMAIL PROTECTED] wrote: Struts 2 must be the most 'quiet' framework I have ever encountered (for such a big mature framework) It's like there never was a hype fase (probably due to the webwork inheritance) - note: hype is used in a positive. And yes,

Re: Googlecode Maven Repository for External Struts 2 Plugins

2007-11-27 Thread Dave Newton
The site looks *horrible* in IE6, at least on my machine. I just never use it, so I had no idea. d. --- Frank W. Zammetti [EMAIL PROTECTED] wrote: Ok, there appears to be an issue with the site then... when I view it in Macthon, my browser of choice, I don't see the buttons. In FF I see

Plugin Article/Pamphlet, was: Re: Googlecode Maven Repository for External Struts 2 Plugins

2007-11-27 Thread Dave Newton
I'm writing a short (30-40pp) Lulu PDF on creating plugins-with-tags as part of the jQuery tags. d. --- Musachy Barroso [EMAIL PROTECTED] wrote: We do need an article explaining how to write plugins, specially how to create tags in those plugins. People email me a lot asking how to get

Re: Googlecode Maven Repository for External Struts 2 Plugins

2007-11-27 Thread Tom Schneider
Wendy, I'm all for syncing it with the central repository, it's just a question of how. Googlecode doesn't give shell access so I have no access to cron to sync things up. I could sync it up manually by checking it out and running the rsync on my local machine, but that seems less than ideal.

Re: Googlecode Maven Repository for External Struts 2 Plugins

2007-11-27 Thread husted
Voila, that's the kind of thing that we'd need more. (Speaking to no one in particular.) If I was going to pull a rabbit out of my hat ... I think it would be labeled patches. :( * https://issues.apache.org/struts/secure/IssueNavigator.jspa?mode=hiderequestId=10740 Though, now that the

Googlecode Maven Repository for External Struts 2 Plugins

2007-11-24 Thread Tom Schneider
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