[security-dev] Compilation issues on PicketLink repository

Anil Saldhana Anil.Saldhana at redhat.com
Tue Oct 30 10:37:58 EDT 2012

    I think we have to figure out a way by which we do not affect 
projects such as Aerogear with our compilation issues.

I think we should just cut checkpoints frequently. The projects using PL 
need to be on checkpoints.

This occurrence of compilation problem was from Pedro. He buys us beer 
next time. :)


On 10/30/2012 08:53 AM, Anil Saldhana wrote:
> Bruno,
>    challenges of unification. Hopefully the CI build notifications will
> help us get better.  But this is a rare occurrence of compilation issue.
> That is why I suggest frequent checkpoint releases from PL such that
> projects such as Aerogear can depend on checkpoints rather than snapshots.
> Regards,
> Anil
> On 10/30/2012 08:34 AM, Bruno Oliveira wrote:
>> Good morning everyone.
>> We on AeroGear have been using PicketBox and PicktLink for real, in
>> nowadays have 3 real dependencies:
>> - picketbox-cdi which depends on picketbox-core
>> - picketbox-core which depends on picketlink
>> - picketlink
>> Today I'm facing with compilation issues on PicketLink repository
>> (https://github.com/picketlink/picketlink/commits/master), I know
>> about the fact that PicketLink is a work in progress, but I would like
>> to ask a favour.
>> If the code doesn't compile and that's a working in progress could you
>> please create a separated branch for it until the compilation issues
>> are fixed?

More information about the security-dev mailing list