Details

    • Similar issues:
      KULRICE-204Create "rice" project
      KULRICE-4918Add jars to Rice maven repository
      KULRICE-277Clean up a few things in "rice-commons" to make the project completely Mavenized
      KULRICE-902KEW source code should be added to the Maven repository
      KULRICE-4946Convert Rice to an m2eclipse project
      KULRICE-279Integrate Jetty plugin for Maven in all Rice projects
      KULRICE-349Investigate ways of linking rice-commons and rice projects using Maven
      KULRICE-4529Split out service apis out into their own maven module in the Rice project
      KULRICE-333Look into using Maven Archetypes for our rice_template project (aka createproject.groovy script)
      KULRICE-1495Migrate create project script
    • Rice Module:
      Rice Core

      Description

      Please put the Maven structure in place for the "rice" project in CVS similar to what was done to the "rice-commons" project. Included with this should be the ability to build out a "rice.jar" and a "rice.zip" which for all intents and purposes, should be empty initially.

      Once completed, Ryan and Nate will use this structure to put the extracted KNS code. Once they are complete with the extraction, there may need to be some follow-up work once again to clean up anything that might not have been completely polished during the extraction. This will be a separate task though.

        Issue Links

          Activity

          Hide
          Aaron Godert (Inactive) added a comment -

          Please talk with Nate and Ryan if you need more specifics or information about what they'll need to support the extracted KNS code.

          Show
          Aaron Godert (Inactive) added a comment - Please talk with Nate and Ryan if you need more specifics or information about what they'll need to support the extracted KNS code.
          Hide
          Scott Battaglia (Inactive) added a comment -

          Aaron,

          Can you give me some more details? Do we plan on having anything other than KNS in there? Do we need Maven modules? What are the dependencies, etc.

          Thanks
          -Scott

          Show
          Scott Battaglia (Inactive) added a comment - Aaron, Can you give me some more details? Do we plan on having anything other than KNS in there? Do we need Maven modules? What are the dependencies, etc. Thanks -Scott
          Hide
          Ryan Kirkendall (Inactive) added a comment -

          There is going to be a sample app, which is already in there. KNS will ultimately be distributed as a jar + a zip file containing a bunch of web content. For now a think the root src can be a kns module and a module for the sample app makes sense. Eventually, the other rice stuff will start going in this projects as modules in their own right, which is why i'm suggesting kns as a module. There may be better ways to go. Module wise. I envision the project looking something like:

          rice-commons -> jar
          rice-shared -> jar
          test-harness -> jar
          bus -> jar
          kns -> jar
          kew -> jar
          ken -> jar
          sample app -> war

          It's actually going to be more complicated than that becaus workflow (kew) and maybe ken can be distributed as a war or a jar but we don't have to deal with that now.

          for now:

          kns -> jar
          sampleapp -> war

          should suffice.

          the dependencies are initially going to be workflow 2.3.2. So for now converting the existing project lib to maven should suffice. Shortly after KNS extraction we'll branch and bring in all the rice-commons stuff. We'll probably need to find a convenient place to start putting our libraries at that point.

          The existing unit tests and jetty server will need to continue working from eclipse and in continous integration. I'll get you access to our CI box. It uses anthill, which is real fun .

          Show
          Ryan Kirkendall (Inactive) added a comment - There is going to be a sample app, which is already in there. KNS will ultimately be distributed as a jar + a zip file containing a bunch of web content. For now a think the root src can be a kns module and a module for the sample app makes sense. Eventually, the other rice stuff will start going in this projects as modules in their own right, which is why i'm suggesting kns as a module. There may be better ways to go. Module wise. I envision the project looking something like: rice-commons -> jar rice-shared -> jar test-harness -> jar bus -> jar kns -> jar kew -> jar ken -> jar sample app -> war It's actually going to be more complicated than that becaus workflow (kew) and maybe ken can be distributed as a war or a jar but we don't have to deal with that now. for now: kns -> jar sampleapp -> war should suffice. the dependencies are initially going to be workflow 2.3.2. So for now converting the existing project lib to maven should suffice. Shortly after KNS extraction we'll branch and bring in all the rice-commons stuff. We'll probably need to find a convenient place to start putting our libraries at that point. The existing unit tests and jetty server will need to continue working from eclipse and in continous integration. I'll get you access to our CI box. It uses anthill, which is real fun .
          Hide
          Aaron Godert (Inactive) added a comment -

          Per our discussion Scott, you'll touch base with Ryan and Nate on Friday so that you can work out logistics of the ordering of this stuff.

          Show
          Aaron Godert (Inactive) added a comment - Per our discussion Scott, you'll touch base with Ryan and Nate on Friday so that you can work out logistics of the ordering of this stuff.
          Hide
          Aaron Godert (Inactive) added a comment -

          Re-assigning to Nate and Ryan since they can just do this during the extraction. They can just consult with you if they have questions, Scott.

          Show
          Aaron Godert (Inactive) added a comment - Re-assigning to Nate and Ryan since they can just do this during the extraction. They can just consult with you if they have questions, Scott.
          Hide
          Aaron Godert (Inactive) added a comment -

          Closing for now. For the most part, my perspective is that this is complete... let me know if there is more work that has to get done here and I can spawn separate issues.

          Show
          Aaron Godert (Inactive) added a comment - Closing for now. For the most part, my perspective is that this is complete... let me know if there is more work that has to get done here and I can spawn separate issues.

            People

            • Assignee:
              Nate Johnson (Inactive)
              Reporter:
              Aaron Godert (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Due:
                Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 1 day
                1d
                Remaining:
                Remaining Estimate - 1 day
                1d
                Logged:
                Time Spent - Not Specified
                Not Specified

                  Structure Helper Panel