To my knowledge, the latest non-alpha version of the #ui5/cli and #sap/ux-ui5-tooling (as of 2nd March 2022 - version 2.14.6 and 1.5.0 respectively) are the ones to use.
However, I wanted to confirm as my organisation has multiple ui5 projects and so having a standardised version of the #ui5/cli and #sap/ux-ui5-tooling dependencies could prevent issues around bugs in tooling.
If the advice is just to use the latest non-alpha version, then I just need to update the dependencies regularly.
The versions you mentioned should be your choice to use in a productive environment.
The upcoming UI5 tooling 3.0 is not.
I don't think you will achieve the same version in every app because of the lifecycle.
The packages are fast paced and when u have a stable app deployed you will not update it every month I think.
I would not invest time to find the perfect tooling version.
We are planning to use Drools in our organisation with Scala/Spark. We have selected Drools Version 5.3.0 and 7.15.0 for our use but we have some stability doubts between them because Version 7.15.0 has recently launched & we are not sure whether it is stable or not.
We have practiced with Version 5.3.0 but we want to know the life cycle of it. What if after some time, Version 5.3.0 will not available for use or some update is brought for this?
So please help us to chose between them which version should we chose for longer use.
Drools 5.3 is outdated version and its not under development. Its better you go with latest release.Drools 7.15 is also stable, but if you are planning to use it for business critical application then I will recommend you to go with enterprise release of Drools 7.x , i.e Red Hat Decision Manager. With enterprise release will get patches for known issue on regular basis and one-off patch for critical issues.
I'm looking for dates until when patches for known vulnerabilities will be delivered for the products mentioned above. I found the same for RedHat's JBoss Enterprise Application Platform, but not for JBoss AS or Wildfly.
Here's an example.
Regarding JBoss Middleware, there is a product update and support policy.
For long-life products, JBoss offers Full support for 4 years, Maintenance support for 3 years and Extended-life support for other 3-6 years.
Although you can imagine JBoss engineers working on the underlying Widlfly software creating patches and solutions for all the time of the Full Support, there is not any guarantee. In addition, note that the version numbers of the JBoss EAP are not the same of the used by Wildfly.
The JBoss EAP v 7.0 (released in 2016, for Java EE 7) uses the Wildfly 9.x (alias "Kenny", released in 2015)
The JBoss EAP v.7.1Beta (released in 2017) uses Wildfly 10.x (released in 2016).
Today (September 6, 2017), reviewing the Issue Tracker for Wildfly, almost all the updated issues in the last week are related to the last versions: 20 are for the version 11.x, 3 for the 12.x-Beta, and 1 for the 8.x. Other 31 do not specify a version. All the resolved issues (9/9) in the last week are related to the version 11.x.
I think you must consider to use one of the last two GA versions of Wildfly. The community is more active in these versions. According to the Wildfly governance page, they deliver a new final major version in around a nine month cycle.
You don't get any guaranteed support for community projects like WildFly and JBoss AS. Commercial support is only available for commercial products like JBoss EAP.
We are using JBoss 4.2 GA, and need use a newest version in some new project.
I heard that JBoss 5.0 encounter such bugs... is this correct?
If not, which exact version of 5.0 to use?? and what about 6.0??
Thanks.
JBoss AS 5.1 is perfectly fine. Every app server has bugs, they're big, complex applications in themselves, but 5.1 is solid.
JBoss AS 6 hasn't been released yet, it's still in beta.
Jboss Application Server 7 is released, and up to a beta version of 7.1.0. You can download a copy here, and find the Getting Started Guides here.
As with any major revision of an application server, there are significant changes that might impact upon your business and will need to be considered in the context of your use case. Being an open source project, the early praise and early bugs are in the public arena, so it is easy to research for yourself.
Working on a documentation project involving AS7 I have seen some of the great work that the team has undertaken, and I couldn't imagine going back to a previous version now I've enjoyed the fast boot-up times, the ease of application deployment, custom configuration and the powerful Management CLI.
These kinds of improvements and features, not just constrained to JBoss Application Server or JBoss Enterprize Application Platform, speak volumes about the speed, stability and usability that will be increasing exponentially in this field for all competitors over the coming years. I'd urge you to check out the current generation of application servers if your experience is largely with JBoss AS 4.2.
As far as i know the EAP editions of JBoss Application Server (AS) are just a bunch of community edition JBoss projects with some sugar.
So, what is the community edition of the JBoss Application Server that JBoss EAP 4.3.0 corresponds to?
This response is really late but I came across the unanswered question in a Google search and I wanted to make sure there's a correct response. I work for JBoss support so you can consider this a qualified answer.
JBoss EAP is the only commercially supported version of JBoss. It contains JBoss AS and JBoss Seam. EAP diverged (in terms of the svn branch it's built off) from JBoss AS around version 4.2.1 (not exactly, but close enough). EAP has a 5-year lifetime and is tested and certified rigorously. EAP has paid commercial support and patches (called CPs or cumulative patches) that are designed to maintain ABI/API stability over time while allowing for security issues and bugs to be fixed. It is actually against policy to introduce a feature in a CP, but it happens on occasion.
If you're familiar with how Red Hat Enterprise Linux differs from Fedora, you can consider the difference to be quite similar. The JBoss project/product split is much newer, though, so the differences are smaller. Here's the official page describing what I've said.
http://www.jboss.com/products/community-enterprise
Cheers,
Chris
According to JBoss Enterprise Application Platform Component Details, JBoss EAP 4.3 is based on:
JBoss Application Server 4.2.1 with various updates, component upgrades, and bug fixes
The primary difference between EAP and the community release is that EAP is the officially supported configuration of the community edition, with fixed versions of the various components. RedHat was finding it too difficult to support the different component versions used by man+dog, and nailed it down to one set.
As for versioning, the EAP version numbers roughly track the community releases, but with differences:
EAP 4.2 is based on JBossAS 4.2
EAP 4.3 is also based on JBossAS 4.2.1, but with JBossMQ replaced by JBossMessaging, and Java6 support
EAP 5.0 is based on JBossAS 5.1
EAP 5.1 also seems to be based on JBossAS 5.1, with some cumulative patches
Edit:
EAP 6.x is based on JBoss Application Server 7.x
I've been digging into JBoss version information to try and find an answer to a more specific question i'm dealing with, and i thought i'd share my observations. You can get a picture of the names and dates of releases from JBoss's JIRA bug tracker: you can check out the info for the Community and Enterprise editions.
I was interested in the 4.2 branch rather than 4.3. If you hunt back a few years, you'll find that the Community release 4.2.0.GA came out on the 14th of May 2007, and was followed six weeks later by the Enterprise release 4.2.0.GA on the 3rd of July 2007. After that, the numbering diverged: the Community edition shipped point upgrades - 4.2.1.GA, 4.2.2.GA and 4.2.3.GA - every few months after that. The Enterprise edition instead shipped a series of 'cumulated patch' releases based on 4.2.0, starting with 4.2.0.GA_CP01 and hitting 4.2.0.GA_CP06 a few months ago. How do these releases relate to each other? I'm still not sure about this, but i think the theory is that the Enterprise edition doesn't gain any new features (within that branch), only bugfixes, but that those bugfixes are applied to both the Enterprise and Community editions. In fact, i suspect that in the case of my bug10, the fix was developed against the Community edition, and then crossported to the Enterprise edition, although i'm far from sure about that.
Turning back to your actual question, things are less clear. The Enterprise 4.3.0.GA came out on the 7th of January 2008, after the Community 4.2.2.GA, but before 4.2.3.GA. There is no Community 4.3.0, nor is there an Enterprise 4.2.x for any x > 0. Chris says that the Enterprise and Community versions "diverged", and i assume that what he means by that is that the Enterprise version is no longer based on just bugfixing a Community version, but rather is now an entirely separate development stream - presumably taking code drops from the Community edition where that's appropriate.
So, the answer to your question is some combination of: 4.2.2.GA (but only distantly), 4.2.0.GA (plus years of separate development), and mu.
While JBoss AS / Wildfly is really the basis for JBoss EAP, it's definitely not just "some sugar" what is added.
EAP is what went through an extensive testing and many many bug and security issues are fixed.
More, EAP is usually also faster after going though a period of performance tests, soak testing, and code analysis.
Also, EAP artefacts (jars) are all built by Red Hat, i.e. Red Hat is responsible for whatever is in them - i.e. you don't get whatever anyone puts in the central repo or whichever other repo you may have configured in your settings.xml (in case you build your own AS). Many of these third-party libraries are changed - CVE's fixed, performance issues addressed etc.
And lastly, EAP is way better in terms of features. For example, last 7.x release of JBoss AS is 7.1.1, year-and-something old, while EAP 6.1 is about a month old, and is way better in regards of manageability, stability, configurability etc. There is a several hundreds of commits difference between those two.
So, stating that "JBoss EAP X is based on JBoss AS Y" may be true, but at the same time misleading.
Check the EAP 6.1.