hmm... which one? Actually for example
has parent keycloak-authentication-parent, which is really in ../pom.xml
. AFAIK it should be good practice to reference parent in one upper
module ? Or are there some issues with it?
For example modules inside "model" references keycloak-parent which is
under "../../pom.xml" so it works too. I wonder that maybe we should
unify that (either all modules to use 1 level upper parent with
relativePath like ../pom.xml or all modules to use keycloak-parent)
Marek
On 22.7.2014 17:14, Bill Burke wrote:
The poms in authentication don't have valid relative paths. That
could
be it.
On 7/22/2014 11:11 AM, Stian Thorgersen wrote:
> Should still work, can you send me the error message?
>
> I've added some two poms that include all dependencies required to create a
server. For an example see:
>
>
https://github.com/keycloak/keycloak/blob/master/project-integrations/aer...
>
> ----- Original Message -----
>> From: "Bruno Oliveira" <bruno(a)abstractj.org>
>> To: "keycloak dev" <keycloak-dev(a)lists.jboss.org>
>> Sent: Tuesday, 22 July, 2014 3:58:04 PM
>> Subject: [keycloak-dev] Building Keycloak from scratch
>>
>> Good morning guys, has anything changed about how to build KC? The build
>> complains about the lack of keycloak-parent with the latest change
>>
https://github.com/keycloak/keycloak/commit/64b8a990f9d5614db9559dc56a626...,
>> but everything goes well with the previous commit
>>
https://github.com/keycloak/keycloak/commit/824aed773b2fd80f9819a3d42879a...
>>
>> Thanks in advance
>> --
>>
>> abstractj
>>
>> JBoss, a division of Red Hat
>> _______________________________________________
>> keycloak-dev mailing list
>> keycloak-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/keycloak-dev
>>
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/keycloak-dev
>