r/java • • Sep 06 '17

JavaEE is now on GitHub

https://github.com/javaee/
203 Upvotes

64 comments sorted by

37

u/_INTER_ Sep 06 '17 edited Sep 06 '17

JavaEE is now on Github.

It was already there, for atleast 4 months.

Also Java EE is moving to an open source foundation after the Java EE 8 release, mostlikely Apache, maybe Eclipse. Often that includes having a repository at the site and only have a mirror at github if at all.

8

u/springnews Sep 06 '17

prediction: it's either Eclipse Foundation, or they'll create a new foundation from scratch. Apache is unlikely.

3

u/nutrecht Sep 07 '17

Apache is unlikely.

Strange. I recall a twitter poll of some Java bobo (forgot who, sorry) where a vast majority of respondents were in favour of Apache.

I personally don't see Apache as a place where projects "go to die", there's a ton of great apache projects (Spark, Cassandra to name a few).

1

u/spyhunter99 Sep 07 '17

Many apache projects either have svn to git mirrors on github or have asf git to github mirrors. Many projects have processes for accepting prs from github. Asf repos only being on github and not on asf infra is unlikely.

-2

u/Tok-A-Mak Sep 06 '17

Apache is perceived as a graveyard for failed heavy-weight projects. The match would be perfect. I think Oracle may not letting it end up there for reasons of reputation.

20

u/jrh3k5 Sep 07 '17

I don't get this sentiment. Apache also manages Hadoop, HBase, Storm, Flume...

4

u/nutrecht Sep 07 '17

I don't get this sentiment.

I really don't see that sentiment either. Like I said in a previous comment; a twitter poll showed a strong (more than 2/3rds) preference for Apache.

5

u/F14D Sep 07 '17

There isn't a day that goes by where I don't have have a coupla apache libs in my dependencies..

1

u/Tok-A-Mak Sep 07 '17

Yes, Hadoop would be a perfect example. I never worked with it and I'm not saying it's a failed project or anything, but it appears far too heavy unless you are actually Google or Amazon doing rocket science. I mean, their logo is an elephant.

4

u/_INTER_ Sep 07 '17

Others like Apache Spark are also used by smaller companies. E.g. 9gag. Rather Eclipse Foundation seems like a graveyard.

3

u/jrh3k5 Sep 07 '17

You're unlikely to need it if you're just doing a small at-home project, but Hadoop and associated products are perfectly suited for small companies. Data ingestion, processing, persistence, and searching are all capabilities of these systems that I've seen companies much smaller than Google leverage.

3

u/[deleted] Sep 07 '17

The postgres logo is an elephant, too.

8

u/snuxoll Sep 07 '17

Apache has a pretty big interest in seeing Java EE continue to evolve, Tomcat is still one of the most popular servlet containers out there. I think it’d be a good fit.

2

u/Shredforgirls Sep 07 '17

You made me laugh.

2

u/avoidhugeships Sep 07 '17

I do not know who holds that few. Apache has a number of very large and successful projects.

25

u/space_coder Sep 06 '17

When it comes to open source, Oracle is damned if they do and damned if they don't.

4

u/xckzwar Sep 06 '17

Why so?

29

u/space_coder Sep 07 '17

People complained that Oracle didn't have an open source development model for Java EE and accused them of being greedy corporate overlords.

Now that Oracle is moving forward with its plans to have an open source development model for Java EE, people are complaining that Oracle may be abandoning Java EE.

2

u/nafsadh Sep 06 '17

Wisely put.

0

u/tkruse Sep 09 '17

No, Oracle has a bad reputation due to how badly they treated the Java community. If they start treating it better, their reputation will improve.

Of course neither going open-source or not will not by itself change the reputation of Oracle. But that does not mean they cannot redeem themselves. It just isn't that easy to make a comeback from years of abusive behavior.

12

u/freebit Sep 06 '17

What does this mean? Was it unexpected? Did Oracle just throw the entirety of Java onto Github? Does Oracle still own Java? Does this mean Oracle doesn't care about Java anymore? I desperately need context here.

30

u/[deleted] Sep 06 '17

Was it unexpected?

There have been signs showing that Oracle is not very interested in Java EE and it's all but been officially confirmed. This seemed like the next logical step. They're going to take a less active roll in Java EE development and instead put it in the hands of the community.

Does Oracle still own Java?

Yes. They did not open source the Java language. They open sourced Java EE, which is the 'Enterprise Edition' of Java. Java EE provides various APIs that are orientated towards enterprise development. It's built on top of the Java language.

What does this mean?

This shows that Oracle wants to take a more hands off approach with Java EE, and put it in the hands of the community. This means companies like IBM, Red Hat, Spring and others who are interested in Java EE can take a more active roll in its development. I think it's an overall good thing for Java EE.

Does this mean Oracle doesn't care about Java anymore?

No. This has to do with Java EE, not the Java Language.

12

u/mayhempk1 Sep 06 '17

Isn't this a good thing because it ensures the longevity of JavaEE rather than letting it slowly fade out?

10

u/frenetix Sep 06 '17

They did not open source the Java language.

The JDK is already open source.

6

u/freebit Sep 06 '17

I understand now that JavaEE and Java are very different things but related. Additionally, you mentioned this move seems to signal Oracle's "hands off" feeling towards JavaEE. Does any of this signify possible future shift of Oracle's policy/feelings/stance on Java itself?

9

u/gogostd Sep 06 '17

It could be a good thing for Java itself, as Oracle will be able to allocate more resources on it. IMO it's a good move.

-5

u/springnews Sep 06 '17

I seriously doubt Oracle is allocating more resources to Java EE

4

u/[deleted] Sep 07 '17

That's not what u/gogostd said.

5

u/evils_twin Sep 06 '17

Oracle also just layed off a bunch of people in their hardware and Solaris operations, not sure how that could be related though.

5

u/thesystemx Sep 06 '17

I'm just guessing here, but Oracle is moving away from licensing on-premisse software and selling hardware and moves completely to a cloud offering vendor, with their database perhaps being an exception.

6

u/evils_twin Sep 06 '17

That's probably a pretty good assessment, Oracle along with everyone else is pushing cloud a lot.

1

u/Luolong Sep 06 '17

No. It has no bearing on Java the language and related SDK. Those are still firmly in Oracle's hands and there have been no signs of reduced interest in Java from Oracle.

6

u/VGPowerlord Sep 07 '17

Yes. They did not open source the Java language.

They didn't open source the Java language now because Sun already did it a decade ago... before Oracle even bought them. That's what OpenJDK is, although it's not on Github.

0

u/randomMAR Sep 06 '17

What do you mean by "They did not open source the Java language" ? what about OpenJDK?

8

u/DJDavio Sep 06 '17

Oracle felt burdened by Java EE because they had to maintain a free open source reference implementation, GlassFish. Now that they are freeing themselves from the API (but not the trademark name Java EE), they can focus more on their paid implementation WebLogic.

1

u/shaner23 Sep 06 '17

So Glassfish is going away?

8

u/thesystemx Sep 06 '17

GlassFish as name, perhaps. But Payara has forked GlassFish some time again and works hard on it.

5

u/DJDavio Sep 07 '17

No, GlassFish was already open source and it will remain so, it's just that the burden to maintain it has been placed on the same community that wants to maintain Java EE. There's also Payara, basically a GlassFish++ version which I think will remain large contributors to the GlassFish codebase.

4

u/TheRedmanCometh Sep 06 '17

I also would like more context. This appears to be a ridiculously big deal. If they really did that...good on you Oracle about time you started working with us instead of against us.

4

u/dablya Sep 06 '17

Looks like the enterprise edition spec and reference implementation are now hosted on github instead of java.net.

8

u/nafsadh Sep 06 '17

The whole universe would be better off if Oracle hands over Java to Apache or some other community. It would be perfect if they'd just handed over everything they got from SUN to the community.

9

u/DJDavio Sep 06 '17

Isn't the JVM already sort of handed over with openjdk? This means that you can be free of Oracle if you use Kotlin/Scala/Groovy, openjdk and Wildfly/Tomcat/...

3

u/nafsadh Sep 06 '17

Sort of, but not fully. Oracle still retains strong hold on various aspects of Java. Notoriously, license requirements for embedded systems. Also, take note about the Google-Oracle suit on Java API.

5

u/DJDavio Sep 06 '17

I did some research and it seems like Oracle wants to phase out proprietary stuff from the JDK to the point they're both basically the same. They realized that the 3rd party licensed stuff they use in their JDK is difficult to maintain and might be better off using an open source alternative.

3

u/snuxoll Sep 07 '17

Oracle only requires commercial licenses for their build of the JDK, you can build OpenJDK for embedded systems if you want or use Azul’s pre-built package without licensing headaches - yay for OpenJDK being released under the GPL.

0

u/nafsadh Sep 07 '17

So many ifs and elses. Good for us, ain't it? On a side note, Java coders are famous for generating complex entanglements of monolithic if-else code blocks.

2

u/evils_twin Sep 06 '17

I'm not sure they're just going to hand over something they paid 7 billion dollars for.

5

u/nafsadh Sep 06 '17

I am not sure Java was SUN's cash cow. SUN made money from h/w sales, right?

4

u/evils_twin Sep 06 '17

Yeah, SPARC. Interestingly enough, I just heard on the news today that Oracle is doing massive layoffs in their hardware divisions.

2

u/nafsadh Sep 06 '17

SPARC

Good old SUN Solaris SPARC!

2

u/nutrecht Sep 07 '17

A few days ago actually. That last remnant of Sun is basically gone now; they laid off somewhere around 1500 people IIRC.

0

u/thesystemx Sep 06 '17

Indeed, and that hw often (but not mandatory, of course) was running Java server software.

1

u/[deleted] Sep 10 '17

They should hand it over to the Pivotal so that, there is no duplication between Spring innovations and then lagging, bureaucratic reception in the JavaEE.

1

u/aretebit Sep 06 '17

It's the right choice, in last Java EE edition they decided just replicate what Spring did, they saw how powerful community is.

4

u/thesystemx Sep 06 '17

in last Java EE edition they decided just replicate what Spring did

What did Java EE 8 exactly replicate from Spring?

1

u/aretebit Sep 07 '17

Lol sorry I meant latest Java EE, not the last one. Java EE replicated everything from Spring because their job is set the standard and Spring became the defacto industry standard (and pretty much still it is). For example Java EE CDI is Spring core, MVC is Spring MVC, Batch is Spring Batch, etc.

3

u/thesystemx Sep 07 '17

Java EE replicated everything from Spring

Not really...

Spring became the defacto industry standard

Sorry, but not really...

Java EE CDI is Spring core

Lol, not really.

CDI is inspired by JSF Managed Beans, EJB, Seam and Guice.

JSF Managed Beans were a full bean model and DI solution based on XML, pretty much like in Spring 1.0. JSF 1.0 and Spring 1.0 were released at the same time.

EJB pioneered the annotation approach, when Spring was still pushing you to do massive amounts of XML.

CDI introduced contextual injection and portable extensions, both way ahead of what Spring core ever had.

If anything, Spring reluctantly followed Java EE here by going the annotation way.

MVC is Spring MVC

MVC is not in Java EE 7. It was a new JSR for Java EE 8, but was dropped at some point.

Batch is Spring Batch

Batch is largely based on IBM's batching systems. IBM already did batching before most Spring team members were even born. Plus, Spring actually participated in the Batch JSR and Spring Batch is a fully compliant Java EE Batch implementation.

etc.

I wonder what that etc is...

-1

u/nutrecht Sep 08 '17

CDI is inspired by JSF Managed Beans, EJB, Seam and Guice.

So CDI was inspired by all that but not Spring. At all. Is that what you're saying?

2

u/Cyberiax Sep 08 '17

IT is known! King when asked answered that and he designer of CDI no?

1

u/henk53 Sep 07 '17

/u/aretebit are you going to explain yourself further?

1

u/aretebit Sep 07 '17

What do you want me to explain further? Is my word against yours. If you lived those times when everyone left java ee for Spring (absolutely everyone, the only one job offers for java ee were for maintaining code, because of how awful it was) you couldn't deny my statements. Oracle saw that the founder of Spring was right and they had to adopt Spring's features to survive. My answer is: Yes really. If you do not believe me go and argue against wikipedia guys becuase I have better things to do that argue with dogmatic people: "Starting from Java EE 6, Java EE is trying to incorporate and standardize concepts/features from and merge with Spring framework. The SOAP with Attachments API for Java (SAAJ) is now part of Java SE 6, and is thus available to Java EE 6 applications without needing to be included in the EE specification.[1] The Java API for RESTful Web Services (JAX-RS) is now included in Java EE.[2] Java EE 6 also standardized DI, AOP and others from Spring into Contexts and Dependency Injection for Java, Dependency Injection for Java, Bean Validation, Managed Beans, and Interceptors." (from: https://en.wikipedia.org/wiki/Java_EE_version_history).

Even Oracle people shows gratitude: "Thank you Spring framework for filling the interim gap and providing functionality that is now included in the mainstream Java EE 6 application servers. The Java EE platform has evolved over the years learning from frameworks like Spring and provides all the functionality to build an enterprise application. Thank you very much Spring framework!" (from: https://blogs.oracle.com/arungupta/why-is-java-ee-6-better-than-spring)

My answer is yes really, in java ee they simply copied what was working with spring because it became extremely popular and java ee clearly failed. And yes really, it became de facto and still it is in some grade, if you do not believe me read the first page of "Learning Spring Application Development" by Ravi Kant Soni (2015) which says: "Spring is now a long-time de-facto standard for Java enterprise software development."

CDI is a cheap copy of spring IOC. I am not talking about the invention of DI nor batch, is the way of doing it, and they just decided catch it because it became very popular in spring.

Sorry I am not active user and don't know/ can't format this text nicely.

2

u/henk53 Sep 08 '17

/u/aretebit a vague statement on Wikipedia is not necessarily right of course. It likely reflects an opinion of a Spring fan who thinks juist like you. I don't see a reference there that proves that statement.

The problem is that people all too commonly parrot each other and the urban myth is strong that Java EE supposedly took so much from Spring.

Now Spring has undoubtedly influenced Java EE, especially the developers first approach. But specific technologies, less than you think.

JPA for instance was based on TopLink and Hibernate. It's not a Spring invention nor technology.

CDI is NOT a cheap copy of Spring. You probably don't know CDI well. As explained here already; CDI was inspired by JSF Managed Beans, EJB, Seam and Guice.

The scopes (request scope, session scope, application scope) came directly from JSF. The named aspect of beans and the ability to reference them from Expression Language came directly from JSF as well. The proxy concept and the interceptors came from EJB, in fact the interceptor spec is still part of EJB. The annotation approach came from EJB as well. EJB started with the very simple @Stateless annotation vs a ton of XML in some file.

So while it's undoubtedly popular among Spring fans to give Spring credit for all those things, if you look in history it's just not true.

Then take a look at other popular Java EE technologies. Expression Language... not a Spring invention either. It originates from an Apache JSP library which later became JSTL. Didn't Spring actually copied that in Spring EL?

Bean Validation... not a Spring invention either. It came from Hibernate.

JTA... again not Spring, this is based on quite old code from IBM from even before Java 1.0 (~1995).

JAX-RS, not really Spring either. You could argue it looked at Spring MVC and Spring MVC influenced it, but JAX-RS goes way beyond Spring MVC and is overal clearly the better REST API.

3

u/xjvz Sep 07 '17

That's probably because Spring developers were heavily involved in those standards. For example Java EE Batch was led by the same guy in charge of Spring Batch.

0

u/[deleted] Sep 06 '17

[deleted]

3

u/thesystemx Sep 06 '17

renaissance ;)