Avro
  1. Avro
  2. AVRO-1044

avro-maven-plugin requires dependency resolution which breaks multi-module projects

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Critical Critical
    • Resolution: Unresolved
    • Affects Version/s: 1.6.2
    • Fix Version/s: None
    • Component/s: java
    • Labels:
      None

      Description

      Use of avro-maven-plugin breaks multimodule projects since it forces the dependency resolution of all of the dependencies, some of which may be from within the reactor and not yet installed in the local cache.

        Issue Links

          Activity

          Hide
          Arvind Prabhakar added a comment -

          Attaching a test multi-module project that reproduces this issue.

          Show
          Arvind Prabhakar added a comment - Attaching a test multi-module project that reproduces this issue.
          Hide
          Arvind Prabhakar added a comment -

          The tarball I attached does not reproduce this problem, it is complaining about something else. Hence I will remove it and work on getting a reproducible testcase.

          Show
          Arvind Prabhakar added a comment - The tarball I attached does not reproduce this problem, it is complaining about something else. Hence I will remove it and work on getting a reproducible testcase.
          Hide
          Scott Carey added a comment -

          On my own multi-module (~30 modules) project, one of them uses avro-maven-plugin. I can clear my local repo of all artifacts related to this build, then do 'mvn clean test-compile' without failure or any attempt to pull artifacts from a repo.

          I have had a problem similar to this due to the remote-resources-plugin when combined with test-jar artifacts. The apache parent pom pulls in and activates the remote resources plugin.

          https://jira.codehaus.org/browse/MRRESOURCES-53

          Show
          Scott Carey added a comment - On my own multi-module (~30 modules) project, one of them uses avro-maven-plugin. I can clear my local repo of all artifacts related to this build, then do 'mvn clean test-compile' without failure or any attempt to pull artifacts from a repo. I have had a problem similar to this due to the remote-resources-plugin when combined with test-jar artifacts. The apache parent pom pulls in and activates the remote resources plugin. https://jira.codehaus.org/browse/MRRESOURCES-53
          Hide
          Scott Carey added a comment -

          Is the problem you are having with the 'idl' mojo? It is the only mojo that requires dependency resolution, as it declares '@requiresDependencyResolution runtime' for some reason.

          That would explain why you have issues and I do not. I am not sure why this mojo requiers all runtime dependencies to be in scope.

          Show
          Scott Carey added a comment - Is the problem you are having with the 'idl' mojo? It is the only mojo that requires dependency resolution, as it declares '@requiresDependencyResolution runtime' for some reason. That would explain why you have issues and I do not. I am not sure why this mojo requiers all runtime dependencies to be in scope.
          Hide
          Scott Carey added a comment -

          This is due to AVRO-971.

          This feature should be optional since it breaks builds.

          Show
          Scott Carey added a comment - This is due to AVRO-971 . This feature should be optional since it breaks builds.

            People

            • Assignee:
              Unassigned
              Reporter:
              Arvind Prabhakar
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:

                Development