On 8/22/07, Rene Gielen <[EMAIL PROTECTED]> wrote: > In another post Ted mentioned that this was tried in struts1 before, and > it did not work. This was before the merger, so I don't know why that > happened. I'm not sure if preconditions would be the same now, maybe it > works better this time?
The two concerns were creating so many release artifacts, and tracking which artifact release went with each core release. A key question will be whether most plugins remain stable between point releases. If each point release forces several plugins to be released, then we're creating extra work without accomplishing much. Though, given the nature of plugins, they may tend to be stable. We could start to address the second question using Maven as a stopgap, but I don't know if we want to make Maven critical to our API for very long. If we are going to have separate release cycles, then I would strongly prefer that a plugin fail fast and hard if the minimum core requirements are not met. (The way, say, FireFox does.) Of course, if we minimize how many plugins we carry here, then both concerns are also minimized. > For the jasper, pell, plexus and jfreechart I don't see moving them out > to some external project would give us. Do we have major open points for > these plugins? IMO they should reside within the ASF part of the framework. That's fine, so long as another committer says to me: "I'm using this plugin in production, or I have tested it throughly and realistically on my local machine, and I vouch that it works as advertised. And, if it doesn't, I'll fix it!" Otherwise, I'm strongly -1 on distributing code that everyone here is ignoring just because we think someone, somewhere might be using it. If it's in the distribution, people expect it to work. It's cruel to let some hapless soul find out something is broken the hard way. -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
