On 3/31/06, Don Brown <[EMAIL PROTECTED]> wrote: > It isn't the jars I'm talking about, it is the multiple release > processes: the plan, the checklists, the voting, the testing. I'd much > rather do it once on a large project than 6 times on small ones. > > As for the risk of being held up, I think that is a much easier risk to > manage. I'm perfectly comfortable with > a) quickly fixing the problem > b) deferring it to the next release > c) backing out the offending code for the release > and each of those operations can take only a few minutes. To assume a > release must have no known issues is not always realistic. > > I guess what I'm saying is I'm willing to be the release manager for > 1.3.1, but I'm looking to do as little work as possible :)
There were no objections to your proposed reorganization, so IMO the thing to do is try it and see what happens. Preferably in the test repo. :) We don't need history for this, so svn export/svn import should do it. (https://svn.apache.org/repos/test) If not, maybe Sean can help; he did the same thing for MyFaces before they switched to Maven 2. Minor issues: * I think Struts EL and Taglib should stay in separate jars because you only need Struts EL in a Servlet 2.3 environment. (Further, I thought there was some technical reason they could not be combined.) * Faces doesn't compile against the latest code. It's complaining about RequestUtils.selectModule(...). Right now, it depends on Struts 1.2.2. Also, its Maven 1 build is not finished. It's probably best to leave it separate for now. I can't take on the reorganization project, but I have time to help with the build if you need it. I made some comments in the proposal thread about removing the svn:externals, etc. And, thanks. :) -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
