This week's book giveaway is in the General Computing forum. We're giving away four copies of Arduino in Action and have Martin Evans, Joshua Noble, and Jordan Hochenbaum on-line! See this thread for details.
Dave Hinkle wrote:e the fixes made to the EAP version backfilled into the OSS version?
Yes, usually the fixes are merged in the next relevant version of the community AS.
As for you other questions, from a community user point of view, the patching is usually against the SVN checked out version. I believe it's the same even if you are creating a patch for production applications hosted on community AS. But i'll let others with more experience around this, answer the question.
Yes, usually the fixes are merged in the next relevant version of the community AS.
Are the fixes available in the SVN repository, or do I have to wait for them to be merged?
Anyone else care to share how they keep the OSS version current or patched in their environments? I'm just now starting to introduce this into my workplace, and need some guidence on how to keep current...
I usually just follow the release versions (although I largely use Tomcat and not JBoss). For Tomcat at least the number of releases is frequent enough so that patches to problems I see are available in a few months as part of a release version.
I am very reluctant to patch against an SVN version and take that in production. If Tomcat releases slow down to the point where I need to start doing so regularly, I will switch to an app server that brings out releases more often. I expect app server vendors and communities to provide me with a functional whole server, and most do.
I know some big names like to bring out app servers as a base release and then a long list of individual file patches. I really don't like that model, because it means that you a) don't have the same version as everyone else and b) don't know if you did it precisely right and in the right order and nothing silently failed and c) you don't really know what actual version you have.
0
