[keycloak-dev] Failed building latest master - as7-subsystem

[Marko Strukelj]

Yeah, it's a bug. It happens if you pass -P to your mvn.

When maven profile is activated via <activeByDefault>true</activeByDefault> any use specifying of profiles via -P will deactivate such profiles that would otherwise be active.

I already made a PR for this ... but it's not in the master yet: https://github.com/keycloak/keycloak/pull/1275

You can work around this by first building without -P to make sure artifacts are downloaded to local repo, then build again with -P and it should work.

You may have issues if you have a mirror configured as these artifacts are pulled from JBoss Early Access repo ...


----- Original Message -----
> I have some issues building latest master. Namely when building
> "integration/as7-subsystem" I had:
> 
> [ERROR] Failed to execute goal on project keycloak-as7-subsystem: Could
> not resolve dependencies for project
> org.keycloak:keycloak-as7-subsystem:jar:1.3.0.Final-SNAPSHOT: The
> following artifacts could not be resolved:
> org.jboss.as:jboss-as-naming:jar:7.5.0.Final-redhat-15,
> org.jboss.as:jboss-as-server:jar:7.5.0.Final-redhat-15,
> org.jboss.as:jboss-as-ee:jar:7.5.0.Final-redhat-15,
> org.jboss.as:jboss-as-web:jar:7.5.0.Final-redhat-15: Could not find
> artifact org.jboss.as:jboss-as-naming:jar:7.5.0.Final-redhat-15 in
> jboss-public-repository-group
> (https://repository.jboss.org/nexus/content/groups/public-jboss)
> 
> 
> To workaround this, I downloaded jboss-eap-6.4.0.Alpha.zip and unzip it
> to my local maven repo. I guess we don't want this step to be required
> for build Keycloak? Is there any public repository, which contains those
> artifacts and which should be put into pom.xml ? Or am I just missing
> something?
> 
> Marek
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>