Using a self build EAP binary in production| JBoss.org Content Archive (Read Only)

15. Re: Using a self build EAP binary in production

wdfink Jan 8, 2014 1:20 PM (in response to michelmemeteau)

If you use EAP bit's you have to pay the subscription if you are in a production or similar environment (i.e. Hot-standby, PreProduction or UAT). Not for developer or temporary test instances.

If I understand you correct you have both in production with EAP bits (EAP6.1.0.Alpha is a special case as it is free to use).

So you need to pay the subscription, remember EAP will have no license cost and is cheaper as other servers.

16. Re: Using a self build EAP binary in production

michelmemeteau Jan 9, 2014 4:58 AM (in response to wdfink)

So but your post is just repeating what has been already said, I m searching for real answers :

- If EAP is a binary product built from 100% the LGPL wildfly sources, a rebuild of those EAP source cannot have any restrictions apart from trademarks, isn't it ?

thus we need to remove all trademarks of Redhat from EAP sources and rebuild it ? and the binary result will be free of restrictions ?

17. Re: Using a self build EAP binary in production

wdfink Jan 9, 2014 3:36 PM (in response to michelmemeteau)

From my understanding (I'm not a lawyer) you can not use the EAP source code which you have donwloaded from the Red Hat customer portal.

If you have access to it you have to follow the rules which you sign to have Enterprise Support.

So you will breach this contract.

A different thing is if you use the github repository, use the appropriate tag and aply the patches from later releases.

But as I understand your question this is not what you want.

18. Re: Using a self build EAP binary in production

michelmemeteau Jan 9, 2014 3:45 PM (in response to wdfink)

As JbossAS is LGPL I don't see how EAP sources wouldn't need to be redistributed ?

they are already : ftp://ftp.redhat.com/redhat/jbeap

To sum up , all this complicated story about Eap sources / use in prodution has been up for more than one year and is really disappointing

19. Re: Re: Using a self build EAP binary in production

fcorneli Feb 16, 2014 2:11 AM (in response to fcorneli)

Makes me smile:

dig centas.org
...
centas.org.        300    IN    SOA    ns1.redhat.com. noc.redhat.com.

20. Re: Using a self build EAP binary in production

marcelomrwin Mar 17, 2014 7:45 PM (in response to stoty2)

Can you help me to build EAP 6.2.1. I've tried your script but no luck.

21. Re: Using a self build EAP binary in production

henk53 Mar 30, 2014 8:27 AM (in response to wdfink)

Wolf-Dieter Fink wrote:

From my understanding (I'm not a lawyer) you can not use the EAP source code which you have donwloaded from the Red Hat customer portal.

I don't think is correct. The source is LGPL and can't be restricted in that way. The (L)GPL was specifically designed to prevent the very thing you are now attributing to it.

In one of the many earlier threads Jason Greene has indeed clarified/confirmed that the LGPL source can not have the kinds of restrictions you are now mentioning. It does contain trademarks and if a product based on the source is going to be distributed then those have to be removed of course.

22. Re: Using a self build EAP binary in production

manarh Mar 31, 2014 3:03 AM (in response to hwellmann.de)

Harald Wellmann wrote:

Absolutely true, but this still sounds like FUD to me. Many people and organizations are happy to use JBoss AS Community builds in production. With the current policy of moving certain branches to a private source repository and binary artifacts to separate Maven repositories, Red Hat is just making everyone's lives harder, acting maybe not against the legal terms of LGPL but definitely against the spirit of OSS by introducing artificial obstacles.

It is not FUD, just a reality and a WARNING, because majority of users won't realize the differences And even you are complaining that it is against spirit of OSS, it is not. All commercial offering are add-on services you can't get with your own build from sources except user forums. And that is limited in time if you are in troubles with some urgent issue(s). And if you look around you will see more stricter offers than what is now in relation of EAP <-> Wildfly/JBoss AS 7

Harald Wellmann wrote:

Anyone intelligent enough to work with JBoss AS will surely be able to build it from source...

In my understanding, there will be no more AS 7.x releases, and the next community release will be WildFly 8.0.0.Final, so if Red Hat do not publish binaries with no strings attached, AS 7.x users will be stuck with 7.1.1. This is really an invitation for people to fork the source repository, backport EAP patches, build the whole lot and publish their own binaries.

I don't think such a fork would benefit the JBoss community, but I can see it coming.

Fork is not directly beneficial - that's true, but spreading the code and merging of patches in forked/original streams together is possible due OSS and don't forget that is the merit of OSS. You can do what you know and would like to do it with sources (surely except included trademarks and such things). OSS is not that thing you only can download binaries and just use it.

BTW Wildfly 8 was already released - Downloads · WildFly

23. Re: Using a self build EAP binary in production

stoty2 Jun 19, 2014 9:37 AM (in response to marcelomrwin)

I have just built 6.2.3. This is the easiest version yet, very nearly builds out of the box.

The usual patch+readme: https://app.box.com/s/x2uwhm325ihp0tevi3tn

24. Re: Using a self build EAP binary in production

stoty2 Aug 7, 2014 3:17 AM (in response to stoty2)

I've made patches for 6.2.4, and 6.3 beta.

You can find all patches at the URL below.

I may upload patches there for new versions as they become available, and as I have time/motivation to do them.

https://app.box.com/s/fmsvp5gups0mi59kn57q