EAP 6.2 depends on AS 7.3-SNAPSHOT???

[arjant]

I found the following in the source code of EAP 6.2 (in the root pom.xml):

<parent>
  <groupId>org.jboss.as</groupId>
  <artifactId>jboss-as-parent</artifactId>
  <version>7.3.0.Final-redhat-SNAPSHOT</version>
  <relativePath>../../pom.xml</relativePath>
  </parent>

Does it really depend on 7.3.0.Final-redhat-SNAPSHOT, or is this a mistake? Is the build even repeatable this way? Judging from the Maven repository, shouldn't this be 7.3.0.Final-redhat-14?

[wdfink]

You should follow this thread EAP 6.2 is built from AS 7.3

The EAP is based on AS7 but AS7 will never be released as WildFly, this is a rename of JBossAS, will be the next community release.

I'm not sure whether this will be a problem as the EAP6.2-maven repostiory is provided as download.

[atijms]

Wolf-Dieter Fink wrote:

You should follow this thread EAP 6.2 is built from AS 7.3

The EAP is based on AS7 but AS7 will never be released as WildFly, this is a rename of JBossAS, will be the next community release.

Of course, but I'm not sure if that is the issue.

The question is not whether AS 7.3 is available or not, but if the source code (pom.xml) for the released version of JBoss EAP should be referencing a SNAPSHOT version. It now looks like the published source code of EAP 6.2 is not the actual source code that was used for the final build but a slightly older version.

[jaikiran]

Where exactly did you find that file? It doesn't look right for the released version to depend on the snapshot.

[arjant]

It's in the source that you can download from: http://jboss.org/products/eap and http://jboss.org/jbossas/downloads and ftp://ftp.redhat.com/redhat/jbeap/6.2.0/en/source

The SNAPSHOT dependency is basically in every other pom.xml e.g. /jboss-eap-6.2-src/pom.xml

[arjant]

p.s. I did some more thorough checking; grepping the source code reveals that 141 files contain this SNAPSHOT version. There are also 141 pom.xml files, so it looks like every other pom.xml file has this SNAPSHOT dependency.

Furthermore, in the source in jboss-eap-6.2-src/dist/pom.xml "package.finalName" is set to "jboss-eap-6.2", but in the binary download the zip/tar file as well as the directory is "jboss-eap-6.2.0". I'm not sure if this means anything, but it looks like "package.finalName" should set this name and thus the appearance of the ".0" out of the blue seems strange.

All at all, it gives the impression that the source that is published is not the actual source that was used for building EAP 6.2.0. Could it be that per accident an older version of the source was published?

[wdfink]

I don't think that the sources are different.

But it might be packed in a different way.

But that are only my two cents.

On the other hand did you are able to compile it? Did you try to run a self build version?

[pgier]

The snapshot versions are only referring to inter-module dependencies, so there is no possibility of the snapshot disappearing or other problems that you might have with an actual external snapshot dependency.

To give some background on this, we have a build tool that automatically sets the pom versions after a source checkout.  This allows us to make updates and test internal builds without adding lots of commits that are just pom version updates.  After the build has undergone some testing/verification, then the git commit ID that was used for the build is tagged with the appropriate version.  The only change made to the sources after checkout is the POM versions, so the resulting run-time is functionally identical.

Locally you should be able to use the versions maven plugin (http://mojo.codehaus.org/versions-maven-plugin/) and run something like this to get the correct versions in your poms:

mvn versions:set -DnewVersion=7.3.0.Final-redhat-14

Sorry for any confusion this caused!

[arjant]

Thanks for the information Paul! It's now really clear to me

One somewhat related question; wouldn't it be more convenient to just make the source repository (e.g. git) public instead of publishing a source archive?