Uploaded image for project: 'Shiro'
  1. Shiro
  2. SHIRO-137

Go through Shiro dependencies and consider marking most third-party dependencies as provided

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 0.9
    • Fix Version/s: 1.0.0
    • Component/s: None
    • Labels:
      None

      Description

      It's unlikely that users would use Shiro support modules to pull in a dependency to third-party libraries (such as Spring), but rather they explicitly declare the version they are dependent on. If we mark this dependencies as provided, we are forcing users to explicity declare those dependencies but at the same time, we avoid issues with potential version conflicts. What I don't like about this issue is that it's kind of open-ended, but I'll do a first pass before 1.0.0 and then close.

        Attachments

          Activity

            People

            • Assignee:
              kaosko Kalle Korhonen
              Reporter:
              kaosko Kalle Korhonen
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 2h
                2h
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 0.5h Time Not Required
                0.5h