[jaikiran]

For all those who have asking about the 7.1.2 release, here's what it really is - There isn't a 7.1.2 release. After 7.1.1 Final was released the product team (the EAP version) started testing the release as always. Various issues were reported and fixed. All these bug fixes have been done to the upstream community repo (the one you all know at github). Now the EAP team are at a point where they need to freeze any more code changes and continue with the rest of the EAP process. That's where a tag comes into picture. That tag is named 7.1.2.Final. The EAP team will continue working against this tag for the rest of their productization process. There's been no release named 7.1.2.Final and that's why you don't see it in the downloads page.

Now, like I said earlier, all these fixes have been made to the upstream repo available for community. This means that the next release of AS7 community version will have all these fixes (plus more). When that release happens and whatever foo-bar version number is assigned to that release is something that Jason (the project lead) will decide. For all those who have been asking if you will have to build against the tag  then the answer is - if your application/project can't wait till the next version is released, then you are free to build against that tag or any subsequent tags  (just like you would against the latest upstream). But if you can wait till the next release (the project lead decides the date), then you'll certainly see one available in the download pages of AS7 project. Bottomline is 7.1.2 is just a tag.

Message was edited by: jaikiran pai - Fixed minor typo

[juergen.zimmermann]

Thank you very much, Jaikiran, for the clarification.

[hemyperry]

Thank you very much Jaikiran!

Now the status is clear.

I guess we are all waiting to hear from Jason (Project Lead) about the timeline for the next release so we could all make the right decisions whether to build it ourselves or wait for the next release.

Jason?

BTW - Can you tell us based on which tag the EAP Beta announcement was based on? 7.1.1.Final? 7.1.2.Final?

thanks!

[jason.greene]

We just started working on 7.2, so the next release, 7.2.0.Alpha1 is just scheduled for July 16th. As Jaikiran mentions, it will include everything in 7.1.2, plus additional features. It's possible we could release earlier if feature development progresses faster, or if we get some interesting contributions. It's also possible we might call this Beta instead of Alpha.

You are probably wondering why call it 7.1.2 then? We have always had product tags and branches in our community repos. The difference is that we aligned the versioning between AS and EAP to make it easy to see the serial progression of releases. For example, EAP 6.0.0.GA will report itself on start as something like EAP 6.0.0.GA (AS 7.1.2-redhatX). The parens contains the actual singular version stream. In this case X = build number, which includes a patch stream on top of 7.1.2. Why is this useful? Well, if you are a user of both, which many of our customers are, you easily know if a set of features or bugs you were monitoring made it into the release.

The other change is that we are using community JIRA for these EAP only version releases to make it easier for contributors (internal or external) to resolve an issue for both EAP and AS.

EAP 6 beta1 is based on 7.1.0 (with some additional patches that are in 7.1.1):

10:33:40,801 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.0.0.Beta1 (AS 7.1.0.Final-redhat-1) started in 2173ms - Started 134 of 205 services (70 services are passive or on-demand)

EAP 6 beta2 is based on 7.1.1 (with some additional patches that are in 7.1.2).

Hope this helps.

[jason.greene]

Savas Ali Tokmen wrote:

Hi all

In November 2010 I had caused very active discussions between JBoss and Oracle when Oracle took over GlassFish and I had said about JBoss having "split their efforts between an open source branch with few releases and no corrective versions, and commercial versions which fix critical issues". For details, read here: http://jaxenter.com/glassfish-and-jboss-clarify-lifecycles-after-accusatory-comment-32646.html

Oracle had then done very good pubicity on it and told that they would have maintenance releases of their GlassFish product's open source edition... a promise that they kept as GlassFish has had many corrective patches and even reached version 3.1.2.

I wouldn't hold your breath. Look at what they are doing to Java. After November there will be no more public Java 6 updates even security updates without a paid license, and this includes source code! Future Java 6 releases will be proprietary non-OSS after November. You will be forced to either update to 7 or to buy a 6 contract.

Now lets compare that to Red Hat. Unlike Oracle, we are 100% open source and give you the source to everything, including our product versions. The only thing we don't provide is the convenience of binaries that go into our product versions. although we do give you tags and source zips. You can look at our release history and can see that we have always done maintenance releases for our community versions, it's just that we only do them up until we hit the next product rev, at which point we start on the next community minor/major release stream. So in this case after EAP6 Beta the next community stream is 7.2.x

[alitokmen]

Hi Jaikiran

Here comes the killer question: is there going to be a 7.1.2.Final?

Thank you

[haukem]

Just to clarify this, is this correct?

There will be no JBoss version 7.1.2 or any other 7.1.X downloadable at https://www.jboss.org/jbossas/downloads ?

So just the official build and upload to the download page is not done the source code with a tag is freely available at github?

The next version will be 7.2 with 7.2.0.Alpha1 in July so the final release of this branch (7.2.0 Final) is targeted somewhere at end of this year?

If I want a 7.1.2 or any other 7.1.X JBoss version I have to build it myself?

If this is true it is a sad situation, we want our application to run on the community edition and the EAP edition and our developers are mostly using the community edition, so we do not have to think about licensing and so on and on productive system we always recommend the EAP version.

[morphy]

Hauke Mehrtens ha scritto:

If this is true it is a sad situation, we want our application to run on the community edition and the EAP edition and our developers are mostly using the community edition, so we do not have to think about licensing and so on and on productive system we always recommend the EAP version.

Uhm, it doesn't seem to be a so bad situation... 7.1.2.Final and next releases are facilities to provide a better EAP release, and that's good, community editions are alive as code (7.1.x) and as binaries (7.2.x), and that's good... i think that we have to thanks redhat for their effort and i'm pleased if with my (sadly, very small by my side) contribution i can help to improve everyone business

[rbertoncelj]

Hauke Mehrtens wrote:

If I want a 7.1.2 or any other 7.1.X JBoss version I have to build it myself?

If this is true it is a sad situation, we want our application to run on the community edition and the EAP edition and our developers are mostly using the community edition, so we do not have to think about licensing and so on and on productive system we always recommend the EAP version.

Building a community version is a process that takes 2 (yes, only two!) actions:

1.) Take the source code from GitHub using your favourite Git client (takes a minute or so, depending on your internet connection)

2.) Run build.bat / build.sh (takes couple of minutes, depending on your hardware)

After build process completes, the binaries are available in [JBOSS_SOURCES_ROOT]\build\target (in exactly the same form as those downloaded from jboss.org).

That's not too hard now, is it? Good luck

[frank.cornelis]

Actually this is what I run to build a new JBoss AS 7.1.2.Final (under Linux):

git clone https://github.com/jbossas/jboss-as.git
cd jboss-as
git checkout 7.1.2.Final
mvn clean install -Prelease

The compiled JBoss AS distribution is available under dist/target.

Only downside to this strategy so far is that you don't have the artifacts (like the jboss-as-maven-plugin) in some public repository. But those from 7.1.1.Final should do for the moment.

[jaikiran]

Frank Cornelis wrote:

Only downside to this strategy so far is that you don't have the artifacts (like the jboss-as-maven-plugin) in some public repository.

You mean the (optional) plugin which is used to deploy applications to AS7? That's built and released independent of the AS7 source. Although their version numbers match sometimes, it's not always the case. For example, if after 7.1.1 version of AS7, there haven't been any bug fixes/changes in the jboss-as-maven-plugin, then there won't be a new release for that plugin. Anyway, that's my understanding, I'll check with James (who maintains that plugin) to be sure.

[jaikiran]

Like others have explained in this thread (thanks guys), building AS7 from a tag is not an issue. It's going to be a one time activity (just like the one time download you would do of the binary from the AS7 download page) and can be done by just one person from within your entire project team (everyone in the project doesn't have to build it). Once that's built, you can share that built binary internally to the rest of your project team, on an accessible location (just like you would do for a binary you downloaded from AS7 download page).

Now I can understand if building from source is a painful process. Like others have replied in this thread, it isn't. You just need to checkout the tag and trigger one command. You don't even need Maven installed since the AS7 sources come with pre-packaged a Maven installation.

If however, you still run into issues while building from the tag, feel free to raise it here in the forums. We'll surely try and help, just like we have been doing to one another user https://issues.jboss.org/browse/AS7-4782

[jamezp]

jaikiran pai wrote:

Frank Cornelis wrote:

Only downside to this strategy so far is that you don't have the artifacts (like the jboss-as-maven-plugin) in some public repository.

You mean the (optional) plugin which is used to deploy applications to AS7? That's built and released independent of the AS7 source. Although their version numbers match sometimes, it's not always the case. For example, if after 7.1.1 version of AS7, there haven't been any bug fixes/changes in the jboss-as-maven-plugin, then there won't be a new release for that plugin. Anyway, that's my understanding, I'll check with James (who maintains that plugin) to be sure.

You are correct Jaikiran. I have tended to correspond the plugin release with the release of a the server, but that likely will diverge at some point. In fact I will likely release a 7.1.2 plugin to introduce some new features.

[alitokmen]

I have two questions:

1. Cas someone push the Maven2 artefacts for JBoss 7.1.2.Final onto Central?
2. Is it legal to mvn clean install the JBoss 7.1.2.Final tag and provide a public download to the generated binary?

Based on size of the changelog between 7.1.1.Final and 7.1.2.Final; I believe MANY people would be interested in having that version

Cheers

[jaikiran]

Savas Ali Tokmen wrote:

I have two questions:

1. Cas someone push the Maven2 artefacts for JBoss 7.1.2.Final onto Central?

JBoss AS artifacts have never been uploaded to Maven central, not even the released versions since many of its dependencies aren't in Maven central. We have our own Maven repo at JBoss. And again, I keep repeating this - 7.1.2.Final is not a release it's a tag. Pushing every tag to Maven repo isn't feasible.

Savas Ali Tokmen wrote:

1. Is it legal to mvn clean install the JBoss 7.1.2.Final tag and provide a public download to the generated binary?

Keeping aside the legal part of this - why would anyone "trust" a binary built and uploaded by someone else, outside of the official project team, more than building it themselves from source?

Savas Ali Tokmen wrote:

Based on size of the changelog between 7.1.1.Final and 7.1.2.Final; I believe MANY people would be interested in having that version

Sure, we have been repeating in our replies - all these fixes will be available in next release. If someone can't wait for the next release they can build from a tag themselves.

Message was edited by: jaikiran pai - Fixed minor typo