Pax Construct
  1. Pax Construct
  2. PAXCONSTRUCT-25

Allow management of maven dependencies using OBR

    Details

    • Type: New Feature New Feature
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: scripts
    • Labels:
      None

      Description

      In most cases, OSGi developer should not be worried figuring out which bundles that satisfies a particular import.

      The idea is:

      • pax-update-maven-dependencies (PUMD) will read the bnd file and figure out all the required import package.
      • PUMD reads the relevant OBR settings, and query each of the OBR.
      • When PUMD founds all bundles that satisfies particular import, checks, whether the URL is a maven repository.
        (e.g, strip off the file extension, and replace with .xml, to query the pom.xml of that bundle).
      • All the search results that are in Maven repositories are listed in the console for user to choose.
      • PUMD updates the dependencies by updating to either <dependencyManagement> or <dependencies> or both depending on the project structure.

      Note; We also need another jira issue for how to deploy the OBR repository xml.

        Activity

        Hide
        mcculls added a comment -

        FYI, there's an open issue over at FELIX to support deployment of the OBR repository xml via the bundleplugin.

        Show
        mcculls added a comment - FYI, there's an open issue over at FELIX to support deployment of the OBR repository xml via the bundleplugin.
        Hide
        mcculls added a comment -

        Moving to 0.1.7 (at earliest) as this requires some thinking - most of the time the BND file won't contain enough information about what packages need to be imported, by default the bundle-plugin will expand the list of imports based on the compiled classes (which suggests the dependent jars are on the classpath already!)

        May need to use some form of resolver to match imports in the source code against bundles (not perfect, but may be good enough).

        Show
        mcculls added a comment - Moving to 0.1.7 (at earliest) as this requires some thinking - most of the time the BND file won't contain enough information about what packages need to be imported, by default the bundle-plugin will expand the list of imports based on the compiled classes (which suggests the dependent jars are on the classpath already!) May need to use some form of resolver to match imports in the source code against bundles (not perfect, but may be good enough).
        Hide
        mcculls added a comment -

        Forms part of better Eclipse / OBR integration

        Show
        mcculls added a comment - Forms part of better Eclipse / OBR integration
        Hide
        mcculls added a comment -

        bumping to 0.1.8 for now

        Show
        mcculls added a comment - bumping to 0.1.8 for now

          People

          • Assignee:
            Unassigned
            Reporter:
            Edward Yakop
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:

              Development