Jason Greene wrote:
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
Out of curiousity more than anything else I just downloaded the EAP6 source code from the link above and tried to build it, but the build fails:
$ ./build.sh ./tools/maven/bin/mvn -s tools/maven/conf/settings.xml install -Dts.smoke [INFO] Scanning for projects... [ERROR] The build could not read 1 project -> [Help 1] [ERROR] [ERROR] The project com.jboss.eap:jboss-eap-parent:6.0.0.CR1 (/space/downloads/jboss-eap-6.0-src/pom.xml) has 1 error [ERROR] Non-resolvable parent POM: Failure to find org.jboss:jboss-parent:pom:8-redhat-1 in WARNING, replace this url with the location to the EAP 6 maven repository was cached in the local repository, resolution will not be reattempted until the update interval of mead-eap6 has elapsed or updates are forced and 'parent.relativePath' points at wrong local POM @ line 26, column 13 -> [Help 2] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException [ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
The readme suggests that running build.sh is all that is required but this doesn't work for me. Not sure if this is just an issue due to maven repositories not being synced yet since the release is so new?