11–20 of 59 posts
ASF : Apache Software Foundation
EC : Executive Committee
EE : Enterprise Edition
JCP : Java Community Process
JSR : Java Specification Request
JSPA : Java Specification Participation Agreement
SE : Standard Edition
TCK : Test Compatibility Kit
For people who are unfamiliar with all the acronyms: ASF : Apache Software Foundation EC : Executive Committee EE : Enterprise Edition JCP : Java Community Process JSR : Java Specification Request JSPA : Java Specification Participation Agreement SE : Standard Edition TCK : Test Compatibility Kit
Dear Java,
We remember when you used to be cool. Now you spend all of your time drinking and hanging out with lawyers. We are leaving and taking the dog and all of the CDs with us.
Love, Apache
My, perhaps naive, question is: will there now be a bifurcation of the Java community? Specifically, will there be an open community with its own standards and implementations, and the Oracle community with theirs.
For people who are unfamiliar with all the acronyms: ASF : Apache Software Foundation EC : Executive Committee EE : Enterprise Edition JCP : Java Community Process JSR : Java Specification Request JSPA : Java Specification Participation Agreement SE : Standard Edition TCK : Test Compatibility Kit
FOU: field-of-use restrictions (in the TCK license).
First: Further, the project communities of the ASF, home to Apache Tomcat, Ant, Xerces, Geronimo, Velocity and nearly a 100 mainstay java components have implemented countless JSRs and serve on and contribute to many of the JCPs technical expert groups. And then: To that end, our representative has informed the JCP's Program Management Office of our resignation, effective immediately. As such, the ASF is removing all…
Not really. JSRs have never been leading the innovation in Java world: Ant, Maven, Velocity, Spring, Hibernate, Grails, Hadoop, GWT, Android, Struts, Wicket, Eclipse - none of them started as a JSR. The only JSR that matter is JavaSE and I don't see it having technical problems. JavaME is dying and Spring showed JavaEE how things should be done so they are catching up now.
I don't know what you mean by that. Just have a look at what JSRs JDK 7 consists of:
http://openjdk.java.net/projects/jdk7/features/
Now imagine some of Apaches representatives were spec leads on some JSRs. Thats a serious threat to a JSR then. Spec leads are not easy to find. Participators in a JSR can go with important knowledge on the topic, too.
Earlier quoted context omitted.
Not really. JSRs have never been leading the innovation in Java world: Ant, Maven, Velocity, Spring, Hibernate, Grails, Hadoop, GWT, Android, Struts, Wicket, Eclipse - none of them started as a JSR. The only JSR that matter is JavaSE and I don't see it having technical problems. JavaME is dying and Spring showed JavaEE how things should be done so they are catching up now.
The only JSR that matter is JavaSE and I don't see it having technical problems. I don't know what you mean by that. Just have a look at what JSRs JDK 7 consists of: http://openjdk.java.net/projects/jdk7/features/ Now imagine some of Apaches representatives were spec leads on some JSRs. Thats a serious threat to a JSR then. Spec leads are not easy to find. Participators in a JSR can go with important knowledge on the…
First: Further, the project communities of the ASF, home to Apache Tomcat, Ant, Xerces, Geronimo, Velocity and nearly a 100 mainstay java components have implemented countless JSRs and serve on and contribute to many of the JCPs technical expert groups. And then: To that end, our representative has informed the JCP's Program Management Office of our resignation, effective immediately. As such, the ASF is removing all…
Not really. JSRs have never been leading the innovation in Java world: Ant, Maven, Velocity, Spring, Hibernate, Grails, Hadoop, GWT, Android, Struts, Wicket, Eclipse - none of them started as a JSR. The only JSR that matter is JavaSE and I don't see it having technical problems. JavaME is dying and Spring showed JavaEE how things should be done so they are catching up now.
For people who are unfamiliar with all the acronyms: ASF : Apache Software Foundation EC : Executive Committee EE : Enterprise Edition JCP : Java Community Process JSR : Java Specification Request JSPA : Java Specification Participation Agreement SE : Standard Edition TCK : Test Compatibility Kit
That helps, but can someone provide a babblefish translation of what this means for those of us who don't live in the Java world? Is it basically... Dear Java, We remember when you used to be cool. Now you spend all of your time drinking and hanging out with lawyers. We are leaving and taking the dog and all of the CDs with us. Love, Apache
If a hypothetical Java Servlet API v4.0 would be released they could still make Tomcat be compliant with it.
On the other hand Tomcat is very widely used in the not-quite-huge-enterprise companies and it is obviously helpful for a spec if all implementers can agree on some common ground before it is written. ECMA probably wouldn't see a point in doing ES5 if Microsoft and Mozilla would not talk to them.