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

Look into fixing why Rice standalone can only be packaged properly using Maven 2.0.9

    Details

    • Type: Bug Fix Bug Fix
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.0.3
    • Component/s: Packaging
    • Labels:
      None
    • Similar issues:
      KULRICE-4804maven no longer executing tests for empty packages
      KULRICE-3849Rice sources not downloading with maven eclipse plugin
      KULRICE-1385Create an assembly for a binary package
      KULRICE-2932rice-config.xml for deployment of standalone server
      KULRICE-1335Evaluate using the maven-release-plugin to handle release/packaging tasks
      KULRICE-3217Update Rice packaging process and related documentation for 1.0, practice generating packaged artifacts
      KULRICE-1475Deploy a test Rice Standalone application to a test environment
      KULRICE-4909Look into why the left sidebar in help isn't displaying properly
      KULRICE-9345Fix ruleAttribute related documentation to show use of applicationId
      KULRICE-1421displaytag.properties in KEW is located in a package which results in it not being loaded

      Description

      We discovered this when trying to do some work on building a standalone Rice war here at IU. It succeeds in building the war file but it has duplicates of some libraries on it and, in 2.0.10 version of maven it looked like the excludes weren't even working.

      I'm going to set this as 1.0 for now but if we don't have time to figure it out for the release, we can defer to 1.1.

        Activity

        Hide
        Peter Giles (Inactive) added a comment -

        For what it's worth: I was able to build it with Maven 2.1.0-M1, I don't see any duplicate libraries, and the excludes seem to have worked.

        Show
        Peter Giles (Inactive) added a comment - For what it's worth: I was able to build it with Maven 2.1.0-M1, I don't see any duplicate libraries, and the excludes seem to have worked.
        Hide
        Jonathan Keller added a comment -

        The update on my system to Maven 2.2 was back in September 2009. I've built Rice many times using maven since there. It seems that the 1.0.1.1 branch of rice did work with Maven 2.2. But, the 1.1 branch does not. See stack trace below.

        [INFO] Not compiling test sources
        [INFO] [surefire:test

        {execution: default-test}

        ]
        [INFO] Tests are skipped.
        [INFO] [war:war

        {execution: default-war}

        ]
        [INFO] Packaging webapp
        [INFO] Assembling webapp[rice-web] in [/Users/jonathan/dev/projects/rice-11/web/target/rice-web-1.1.0-SNAPSHOT]
        [INFO] ------------------------------------------------------------------------
        [ERROR] FATAL ERROR
        [INFO] ------------------------------------------------------------------------
        [INFO] null
        [INFO] ------------------------------------------------------------------------
        [INFO] Trace
        java.lang.NullPointerException
        at org.apache.maven.plugin.war.util.WebappStructure.getDependencies(WebappStructure.java:109)
        at org.apache.maven.plugin.war.util.WebappStructure.analyseDependencies(WebappStructure.java:288)
        at org.apache.maven.plugin.war.packaging.DependenciesAnalysisPackagingTask.performPackaging(DependenciesAnalysisPackagingTask.java:46)
        at org.apache.maven.plugin.war.AbstractWarMojo.buildWebapp(AbstractWarMojo.java:439)
        at org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp(AbstractWarMojo.java:375)
        at org.apache.maven.plugin.war.WarMojo.performPackaging(WarMojo.java:181)
        at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:143)
        at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
        at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:41)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
        at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
        at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
        at org.codehaus.classworlds.Launcher.main(Launcher.java:375)

        Show
        Jonathan Keller added a comment - The update on my system to Maven 2.2 was back in September 2009. I've built Rice many times using maven since there. It seems that the 1.0.1.1 branch of rice did work with Maven 2.2. But, the 1.1 branch does not. See stack trace below. [INFO] Not compiling test sources [INFO] [surefire:test {execution: default-test} ] [INFO] Tests are skipped. [INFO] [war:war {execution: default-war} ] [INFO] Packaging webapp [INFO] Assembling webapp [rice-web] in [/Users/jonathan/dev/projects/rice-11/web/target/rice-web-1.1.0-SNAPSHOT] [INFO] ------------------------------------------------------------------------ [ERROR] FATAL ERROR [INFO] ------------------------------------------------------------------------ [INFO] null [INFO] ------------------------------------------------------------------------ [INFO] Trace java.lang.NullPointerException at org.apache.maven.plugin.war.util.WebappStructure.getDependencies(WebappStructure.java:109) at org.apache.maven.plugin.war.util.WebappStructure.analyseDependencies(WebappStructure.java:288) at org.apache.maven.plugin.war.packaging.DependenciesAnalysisPackagingTask.performPackaging(DependenciesAnalysisPackagingTask.java:46) at org.apache.maven.plugin.war.AbstractWarMojo.buildWebapp(AbstractWarMojo.java:439) at org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp(AbstractWarMojo.java:375) at org.apache.maven.plugin.war.WarMojo.performPackaging(WarMojo.java:181) at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:143) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:41) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
        Hide
        Eric Westfall added a comment -

        It seems to me like we should just go ahead and upgrade to the latest version of Maven (2.2.1 i think?). Although Scott mentioned it might make sense to wait for Maven 3, although I'm not sure what the planned release date is for that.

        Show
        Eric Westfall added a comment - It seems to me like we should just go ahead and upgrade to the latest version of Maven (2.2.1 i think?). Although Scott mentioned it might make sense to wait for Maven 3, although I'm not sure what the planned release date is for that.
        Hide
        Garey Taylor added a comment -

        Doesn't give a release date, but you can get a good idea on how things are going:
        http://jira.codehaus.org/browse/MNG#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel

        Show
        Garey Taylor added a comment - Doesn't give a release date, but you can get a good idea on how things are going: http://jira.codehaus.org/browse/MNG#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel
        Hide
        Travis Schneeberger added a comment -

        The newest m2Eclipse plugin uses maven3 by default... I haven't noticed any problems with it while I was testing it. To be safe though we have all devs' m2Eclipse setup pointing at the latest external maven2 installation so I'm not sure how much testing has actually been done.

        Show
        Travis Schneeberger added a comment - The newest m2Eclipse plugin uses maven3 by default... I haven't noticed any problems with it while I was testing it. To be safe though we have all devs' m2Eclipse setup pointing at the latest external maven2 installation so I'm not sure how much testing has actually been done.
        Hide
        Travis Schneeberger added a comment -

        I believe I fixed this in rice 1.1. Please confirm.

        Show
        Travis Schneeberger added a comment - I believe I fixed this in rice 1.1. Please confirm.
        Hide
        Eric Westfall added a comment -

        I checked this and the Rice standalone war is getting packaged correctly now, so all is well. I also verified that the exclusions are working properly and ojdbc14.jar and mysql connector jar aren't making it into the war either (which is good). I'm resolving this issue.

        Show
        Eric Westfall added a comment - I checked this and the Rice standalone war is getting packaged correctly now, so all is well. I also verified that the exclusions are working properly and ojdbc14.jar and mysql connector jar aren't making it into the war either (which is good). I'm resolving this issue.

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Structure Helper Panel