Kuali Rice Development
  1. Kuali Rice Development
  2. KULRICE-1760

mvn eclipse:eclipse is not pulling in dependencies properly

    Details

    • Type: Bug Fix Bug Fix
    • Status: Closed Closed
    • Priority: Blocker Blocker
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.9.3
    • Component/s: Development
    • Labels:
      None
    • Similar issues:
      KULRICE-1654Switch 0.9.3 project to Maven eclipse:eclipse plugin and update docs
      KULRICE-8445Pull out KRAD into a separate project
      KULRICE-10638Rice is pulling in multiple versions of the commons-chain artifact
      KULRICE-4877createproject.groovy still generates a project which does not compile successfully in Eclipse
      KULRICE-13350Loadtest CI Jobs: do full mvn clean install during build
      KULRICE-2953Rice is currently pulling in the geronimo javamail jar as an undesirable dependency from CXF, this is conflicting with sun javamail functionality
      KULRICE-13003Test git with mvn validate
      KULRICE-5008Prepare the main 1.1 branch of Rice for Eclipse-based development with Maven
      KULRICE-3628use provided scope for dependencies where applicable in POM
      KULRICE-7907Exclude jsp-api from jstl-impl dependency

      Description

      If you execute this with a fresh checkout then you will get the following libraries which are in the eclipse classpath but not in the maven repository:

      commons-code-1.2
      commons-collections-3.1.jar
      servlet-api-2.3.jar
      xml-apis-1.3.02.jar

      At the very least, the commons-collections-3.1 dependency is wrong (it should require 3.2) however we are not manually specifying this dependency in our POM. Most likely what we need to do is declare these dependencies at the top level in our pom and this should resolve the issue.

        Issue Links

          Activity

          Hide
          Eric Westfall added a comment -

          This issue should be resolved now. I believe the problem was related to optional dependencies which mvn eclipse:eclipse was pulling into the .classpath file, but a mvn install was not pulling them into the repository. Maven only pulls in optional dependencies if there is a direct dependency from the POM. Any transitive optional dependencies are not pulled in automatically unless explicitly defined in POM (some of the offending libraries in the case were optional dependencies of OJB 1.0.4).

          Show
          Eric Westfall added a comment - This issue should be resolved now. I believe the problem was related to optional dependencies which mvn eclipse:eclipse was pulling into the .classpath file, but a mvn install was not pulling them into the repository. Maven only pulls in optional dependencies if there is a direct dependency from the POM. Any transitive optional dependencies are not pulled in automatically unless explicitly defined in POM (some of the offending libraries in the case were optional dependencies of OJB 1.0.4).

            People

            • Assignee:
              Eric Westfall
              Reporter:
              Eric Westfall
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 45 minutes
                45m
                Remaining:
                Remaining Estimate - 45 minutes
                45m
                Logged:
                Time Spent - Not Specified
                Not Specified

                  Structure Helper Panel