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

createproject.groovy still generates a project which does not compile successfully in Eclipse

    Details

    • Type: Improvement Improvement
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.0.3.1
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-5624Evaluate Groovy/Maven compiler choices
      KULRICE-7101createproject.groovy does not work in Rice 2.0.1
      KULRICE-4139Test the createproject.groovy script for the 1.0.2 release
      KULRICE-6854Fixes to Rice createproject.groovy script
      KULRICE-1639Add /modules to .classpath file generation in createproject.groovy
      KULRICE-1654Switch 0.9.3 project to Maven eclipse:eclipse plugin and update docs
      KULRICE-4618Update createproject.groovy to have option to create project for use with standalone rice
      KULRICE-5417Get createproject.groovy working for Rice 2.0
      KULRICE-1320Examine the need for a generated Rice project to have a dependency on the Rice eclipse project
      KULRICE-4434Fix issues with compilation in Eclipse
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      First of all, it seems that the .classpath file generated by mvn eclipse:eclipse defaults to using java 1.5 which seems wrong. I suspect this is because the pom file which is generated by groovy includes the following in it:

      <build>
      <plugins>
      <plugin>
      <artifactId>maven-compiler-plugin</artifactId>
      <configuration>
      <source>1.5</source>
      <target>1.5</target>
      </configuration>
      </plugin>
      </plugins>
      </build>

      Second, the generated .classpath file still has a reference to xml-apis in it as follows:

      <classpathentry kind="var" path="M2_REPO/xml-apis/xml-apis/1.0.b2/xml-apis-1.0.b2.jar"/>

      This conflicts with the xml apis provided by the jdk and you end up with an error like the following in eclipse:

      The method getTextContent() is undefined for the type Node AccountAttribute.java /trnapp/src/main/java/edu/sampleu/travel/workflow line 64

      The is fixed by either moving the JRE system library to the top of the "order and export" list inside fo the project build path properties or removing xml-apis from the classpath entirely. Requiring someone to do this manually is not desirable.

      Running an mvn dependency:tree, it looks like xml-apis is being brought in by xalan, so one possible solution is just to exclude this transitive dependency in our pom.xml

        Activity

        Hide
        William Balderamos (Inactive) added a comment -

        See revision #15603.

        Show
        William Balderamos (Inactive) added a comment - See revision #15603.
        Show
        William Balderamos (Inactive) added a comment - http://fisheye.kuali.org/cru/rice-25
        Hide
        William Balderamos (Inactive) added a comment -

        See revision #15609.

        Show
        William Balderamos (Inactive) added a comment - See revision #15609.
        Hide
        Jessica Coltrin (Inactive) added a comment -

        closing since 1.0.3.1 is released.

        Show
        Jessica Coltrin (Inactive) added a comment - closing since 1.0.3.1 is released.

          People

          • Assignee:
            William Balderamos (Inactive)
            Reporter:
            Eric Westfall
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Structure Helper Panel