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

POMs are not consistent and both rice and shared poms don't spit out artifacts

    Details

    • Type: Bug Fix Bug Fix
    • Status: Closed Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.9.0.3, Core - 0.9.0.3
    • Component/s: Configuration
    • Labels:
      None
    • Similar issues:
      KULRICE-5234POM Cleanup
      KULRICE-13496Promote Maven Saucelabs/Selenium bits from root pom to parent pom
      KULRICE-10294Promote JMeter maven in root pom to parent pom
      KULRICE-5065Implement parent pom on Rice trunk
      KULRICE-3899Fix the xapool jar, pom and classpath issues
      KULRICE-10638Rice is pulling in multiple versions of the commons-chain artifact
      KULRICE-6798Branch strip-bom-maven-plugin and Add it to the Kuali Rice POM
      KULRICE-350Figure out proper versions of Jetty and JSP libs to use (use what rice has going on) and copy over and make the POM modules in rice-commons consistent with them
      KULRICE-949Let Scott know when JManage is removed so that he can update our acknowledgments, licenses, etc
      KULRICE-387Merge rice-commons POM changes into HEAD
    • Rice Module:
      Rice Core

      Description

      The main rice pom.xml and the shared pom.xml have the full schema listed out for the <project> tag in them; whereas the other poms do not.

      It just so happens that these two don't have artifacts generated for them, while the others do. Coincidence?

      Regardless, they should be consistent and all spit out artifacts in Bamboo.

        Activity

        Hide
        Ryan Kirkendall (Inactive) added a comment -

        poms are fixed. I see artifacts in bamboo about all our modules so I maybe missing something there.

        Show
        Ryan Kirkendall (Inactive) added a comment - poms are fixed. I see artifacts in bamboo about all our modules so I maybe missing something there.
        Hide
        Aaron Godert (Inactive) added a comment -

        If you take a look at https://test.kuali.org/bamboo/download/RICE-ZNZT/artifacts/build-1/shared the output is a blank page, whereas the other modules have the nice little Maven2 project web sites.

        And the other question I have is why the top level main pom, which has an artifactId of rice, doesn't have an artifact associated with it? Is it not supposed to?

        Show
        Aaron Godert (Inactive) added a comment - If you take a look at https://test.kuali.org/bamboo/download/RICE-ZNZT/artifacts/build-1/shared the output is a blank page, whereas the other modules have the nice little Maven2 project web sites. And the other question I have is why the top level main pom, which has an artifactId of rice, doesn't have an artifact associated with it? Is it not supposed to?
        Hide
        Aaron Godert (Inactive) added a comment -

        Looks like /core/pom.xml did not get updated to have it's <project> tag reference the schema appropriately and consistently with the others.

        Show
        Aaron Godert (Inactive) added a comment - Looks like /core/pom.xml did not get updated to have it's <project> tag reference the schema appropriately and consistently with the others.
        Hide
        Ryan Kirkendall (Inactive) added a comment -

        OK. I think I finally got them all.

        Show
        Ryan Kirkendall (Inactive) added a comment - OK. I think I finally got them all.
        Hide
        Aaron Godert (Inactive) added a comment -

        Any idea why the shared artifact is a blank page?

        Show
        Aaron Godert (Inactive) added a comment - Any idea why the shared artifact is a blank page?
        Hide
        Ryan Kirkendall (Inactive) added a comment -

        Nope. Fortunately, there isn't really anything there clover or test wise. Maybe Chi can figure it out. I'm writing up a JIRA of all the issues with our current CI that I can think of.

        Show
        Ryan Kirkendall (Inactive) added a comment - Nope. Fortunately, there isn't really anything there clover or test wise. Maybe Chi can figure it out. I'm writing up a JIRA of all the issues with our current CI that I can think of.
        Hide
        Aaron Godert (Inactive) added a comment -

        Thanks... so basically it spits out a blank page if nothing gets generated. Makes sense... to a certain degree.

        Show
        Aaron Godert (Inactive) added a comment - Thanks... so basically it spits out a blank page if nothing gets generated. Makes sense... to a certain degree.

          People

          • Assignee:
            Ryan Kirkendall (Inactive)
            Reporter:
            Aaron Godert (Inactive)
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Due:
              Created:
              Updated:
              Resolved:

              Structure Helper Panel