Hi all,here is what Shane and I have been discussing in the last 10 daysthat we can come to an agreement in this thread. Please provide yourfeedback and insights as we move forward with the PicketLink main workspace.Proposal:PicketLink main workspace will have the following modules:a) core : will contain the CDI based security code that Shane has beendriving.
b) idm: will contain the idm api and impl submodules. This is lowdependency JavaSE library for Identity Management functionality (CRUD ofusers/roles/groups). This module is ultra critical to all projects. c) federation: will contain the core SAML (and maybe WS-Trust) code
c) federation: will contain the core SAML (and maybe WS-Trust) codewithout any EE container dependencies. Mainly parsing, writing and modelcode.d) social: will contain social login code that allows signin usingfacebook, google/openid, twitter.
Versioning:Last major release of PL has been with 2.1.5So definitely we can release above with 3.xSince we may need some container binding code with AS, Tomcat etc, wehave two possibilities:a) Create another workspace in PicketLink github organization for thecontainer binding. (My preference)
b) Create a separate github organization that will host all thecontainer bindings, integration testing workspaces etc. We can call itpicketlinkbindings.
Regards,Anil_______________________________________________security-dev mailing list