Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-19076

move jersey code in hadoop-common jar to a new hadoop-jersey1-common jar

    XMLWordPrintableJSON

Details

    • Task
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • None
    • None

    Description

      Hadoop's Jersey dependencies are causing us real trouble.

      I'm wondering if it would be a good idea to take the jersey and javax.ws code out of hadoop-common and move it into a dedicated hadoop-jersey1-common jar. We could later create a hadoop-jersey2-common.

      hadoop-jersey1-common and hadoop-jersey2-common would have equivalent classes - just depend on different versions of Jersey.

      Example code:

      Hadoop modules that need access to the common jersey code could start with depending on hadoop-jersey1-common but later be refactored to use hadoop-jersey2-common. We could do this on a module by module basis (one a time).

      hadoop-common jar would have its jersey and jsr311-api dependencies removed.

      Wdyt slfan1989, steve_l, ayushsaxena ?

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              fanningpj PJ Fanning
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: