Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automatic dependency resolution. #420

Merged
merged 1 commit into from
Aug 26, 2015
Merged

Commits on Aug 26, 2015

  1. Automatic dependency resolution.

    Dependency configuration happens in 2 phases:
    - Dependency conversion:
      This converts your compile and testCompile dependencies into
      equivalent j2objcTranslation and j2objcLinkage dependencies.  Namely
      local jars are copied to j2objcTranslation, external Maven jars are
      converted into their 'sources' form and copied to j2objcTranslation,
      and projects are copied to j2objcLinkage (they don't need translation).
    
      This phase is optional and controlled by j2objcConfig.autoConfigureDeps
    
    - Dependency resolution:
      This phase converts j2objcTranslation and j2objcLinkage deps into
      actual j2objc commands.  Any source jar on j2objcTranslation is
      added to translateSourcepaths with --build-closure.  Any project
      on j2objcLinkage is added to translateClasspaths and has its final
      j2objc static library linked in to this project's objective c code.
    
      This phase always runs.  If your dependencies are too complicated
      for the plugin to figure out in the first phase, keep autoConfigureDeps=false,
      and just add the appropriate projets, jars, and libraries here.
    
    Also adds system tests for both project and external Maven dependencies.
    
    issue j2objc-contrib#180; Fixes j2objc-contrib#41; Fixes j2objc-contrib#372
    
    TESTED=yes
    advayDev1 committed Aug 26, 2015
    Configuration menu
    Copy the full SHA
    e5889e1 View commit details
    Browse the repository at this point in the history