This is a little linked to the Apache-open source question raised a while back, though it actually comes from trying to explain to someone what the pro's and reasons for groovy as a jsr might be.
How about if Jakarta [or Apache-Java as a whole] embraced the latest JCP process? If there's anything the ASF are not happy with in the JCP we can adjust it, but generally we would manage our own projects in the same way that ASF involvement in the JCP.org says we should manage standards. What I'm largely interested in are the reasons why not, as these would be perfect reasons why something like groovy, or ant or httpclient, should not become jsr's. So... why not run [EMAIL PROTECTED] under the JCP process? Hen --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
