Uploaded image for project: 'Seam Security'
  1. Seam Security
  2. SEAMSECURITY-66

Separated API/IMPL jars do not allow compilation of the SimpleAuthenticator example

    Details

    • Steps to Reproduce:
      Hide

      1. Use the SimpleAuthenticator example.
      2. Attempt to compile using the separated api/impl jars, with api in the compile scope, and impl in the runtime scope.

      Show
      1. Use the SimpleAuthenticator example. 2. Attempt to compile using the separated api/impl jars, with api in the compile scope, and impl in the runtime scope.
    • Affects:
      Compatibility/Configuration
    • Workaround:
      Workaround Exists
    • Workaround Description:
      Hide

      Use the combined jars, or put the impl jar into the compile scope.

      Show
      Use the combined jars, or put the impl jar into the compile scope.
    • Estimated Difficulty:
      Low

      Description

      The SimpleAuthenticator example is not compilable with the separated API/IMPL jars, but instead must use either the combined jars, or the impl jar must be in the compile scope.

      This seems like an incorrect factoring of impl vs api classes if the impl classes are required to compile a simple example of a custom authenticator. In particular, the PasswordCredential, BaseAuthenticator and SimpleUser classes are not available if only the API jar is used as a compile time dependency.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  shdwshard Charles C
                • Votes:
                  1 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated: