If you are retrieving and building the the code from 8.7.x branch, then that will not work with EAP 6.1 Alpha. Take the code from git release tag 8.7-Final. If the maven repo does not contain the version of the software now I am not sure if that can be resolved, but it is not at all common someone removes the contents from maven repo. You can try to build with 6.0.0.CR12 but need to account for all the version mismatches that went into 8.7.Final build to be in sync.
As per naming question, I am not sure what mean by that, what we used to build the 8.7 is in the pom.xml and settings.xml files. EAP 6.3.0.Beta does *not* have same license as EAP 6.1 Alpha
I am building the code from git release 8.7-Final and the build succeeds if I use 6.0.0.CR12.
Regarding the jboss-as-naming. The version mentioned in the pom.xml is 7.4.0.Final-redhat-11 but this version is not available in the maven repository for EAP 6.1.0 Alpha.
The version that exists in the EAP 6.1.0 Alpha is 7.2.0.Alpha1-redhat-4. Can we use 7.2.0.Alpha1-redhat-4?
Add the following repo to your settings.xml file
<profile> <id>jboss-snapshots</id> <repositories> <repository> <id>jboss-snapshots</id> <name>JBoss Snapshots</name> <url>https://repository.jboss.org/nexus/content/repositories/snapshots/</url> <layout>default</layout> <releases> <enabled>true</enabled> <updatePolicy>never</updatePolicy> </releases> <snapshots> <enabled>false</enabled> </snapshots> </repository> </repositories> </profile>
The 6.0.0-SNAPSHOT will be visible.
Can you also help me in the version of jboss-as-naming?