PicketLink issue

[mutantu2002]

I've created an issue regarding PicketLink Hibernate implementation https://jira.jboss.org/browse/PLINK-41

It's explained there how to resolve this.

Can you tell me when can you release a GA version with this bug resolved?

Maybe you can create a patch for 1.1.1 GA with this bug resolved?

Maybe I can help?

Thanks

[bdaw]

Thanks!

It is rare to get a bug report with ready and proper fix. I applied your patch in http://anonsvn.jboss.org/repos/picketlink/idm/branches/1.1.0/

I'm still looking at other bugs and may release 1.1.5.CR02 this week. Try to upgrade to the latest code brom 1.1.0 branch as there were couple of important bug fixes and performance improvments since 1.1.1.GA. 

[mutantu2002]

Thanks.

Two more question please:

1. I saw that the SVN tags are different from the version on your maven repository: http://repository.jboss.org/maven2/org/picketlink/idm/picketlink-idm-hibernate/. For instance from the repository is missing the 1.1.4.GA version. Why is that? Is there another repository where you deploy your artifacts?

2. We use the PicketLink IDM by synchronizing our internal maven repository with yours: http://repository.jboss.org/maven2/org/picketlink/idm/, but apparently this is not the best way to do it (your artifactory not beeing very offen updated (?)). We use also Hudson for our CI process.

What do you suggest in order to keep updated? Can you update your repository with each version released? Or is better to chec-out sources and build locally?

Thanks again.

[bdaw]

I'm always deploying every release/tag into JBoss.org maven repository. After it migrated to nexus URLs changed. You will find all tags here:

https://repository.jboss.org/nexus/content/groups/public/org/picketlink/idm/picketlink-idm-hibernate/

Should be ok to just rely on repository.jboss.org but for those rare moments when updates are in svn and not yet released some mechanism to build and install locally would do. You can always just build patched jar and attach it to your build with "system" dependency scope and then remove once it is deployed into the repo.