Uploaded image for project: 'Commons VFS'
  1. Commons VFS
  2. VFS-571

make optional providers optional to osgi

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Duplicate
    • Affects Version/s: 2.0
    • Fix Version/s: None
    • Labels:
      None

      Description

      Only Major because it's easy to fix

      Generated osgi metadata in the dist jars do not have packages optional for providers that ARE optional.

      If you look in providers.xml you can see some providers shouldn't load based on where classes are present. However the osgi manifest requires these classes (currently). To make these classes also optional to osgi you need to change commons-vfs2-project pom.xml to include the property:

      <properties>
      <!-- existing properties, then... -->
      <commons.osgi.import>com.jcraft.jsch.*;resolution:=optional,
      javax.crypto.*;resolution:=optional,
      org.apache.commons.httpclient.*;resolution:=optional,
      org.apache.commons.net.ftp.*;resolution:=optional,
      org.apache.jackrabbit.webdav.*;resolution:=optional,
      *</commons.osgi.import>
      </properties>

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                taylor_tails Peter Taylor
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 1h
                  1h
                  Remaining:
                  Remaining Estimate - 1h
                  1h
                  Logged:
                  Time Spent - Not Specified
                  Not Specified