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

Update createproject.groovy to take into account web content refactoring

    Details

    • Type: Task Task
    • Status: Closed Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.9.3
    • Component/s: Development
    • Labels:
      None
    • Similar issues:
      KULRICE-2609Update createproject.groovy and documentation for 1.0 release
      KULRICE-353Acknowledgments content on web site is incorrect and needs to be updated
      KULRICE-4139Test the createproject.groovy script for the 1.0.2 release
      KULRICE-7229Web Content modularity for KRAD
      KULRICE-4951Implement Web Content Modularity
      KULRICE-329Look into making the rice web content a struts module
      KULRICE-4627Web Content Analysis
      KULRICE-1849Put web content ZIP into the maven repository
      KULRICE-3676Fix issues with createproject.groovy script and update it for 1.0.1, update and improve related documentation
      KULRICE-276consolidate rice web content under common root or other permanent solution

      Description

      In KULRICE-898 we reorganized the rice web content. We need to update createproject.groovy to make sure it still works as expected.

      Additionally, I suspect there may be other problems with this script.

        Issue Links

          Activity

          Hide
          Aaron Hamid (Inactive) added a comment -

          For what it's worth that newer version I was talking about has several new options, one of which is to be able to uncheck "Resolve dependencies from workspace projects"...at least I think that's new.

          Show
          Aaron Hamid (Inactive) added a comment - For what it's worth that newer version I was talking about has several new options, one of which is to be able to uncheck "Resolve dependencies from workspace projects"...at least I think that's new.
          Hide
          Ailish Byrne added a comment -

          i just recall discussing at the integration meeting a while back that the generated project should be a maven project and get the libs from the maven repository or have the libs in it - rather than depending on the rice project. since we didn't expect them to be modifying rice code. sorry, i probably wasn't very clear - maybe that fell of the radar and i need to create a separate jira for that - just seems like it might impact how this one is done, but maybe not - or, maybe i'm just tripping thanks!

          Show
          Ailish Byrne added a comment - i just recall discussing at the integration meeting a while back that the generated project should be a maven project and get the libs from the maven repository or have the libs in it - rather than depending on the rice project. since we didn't expect them to be modifying rice code. sorry, i probably wasn't very clear - maybe that fell of the radar and i need to create a separate jira for that - just seems like it might impact how this one is done, but maybe not - or, maybe i'm just tripping thanks!
          Hide
          Eric Westfall added a comment -

          There actually is a separate issue for this one (KULRICE-1320). And what I'm doing will end up generating a maven project that does not have dependencies on a Rice project. Rather the project will have a pom with a dependency on the rice libraries. Then the standard maven build of the generated project will get the libs and all dependencies from the maven repository(s). As it turns out, I think the concerns raised in KULRICE-1320 will essentially go away since the projects generated by createproject.groovy will no longer be using the Maven plugin for Eclipse (which was what was establishing the dependency on the rice project). In summary, I think we are going to be where we want to be when this work is done

          Show
          Eric Westfall added a comment - There actually is a separate issue for this one ( KULRICE-1320 ). And what I'm doing will end up generating a maven project that does not have dependencies on a Rice project. Rather the project will have a pom with a dependency on the rice libraries. Then the standard maven build of the generated project will get the libs and all dependencies from the maven repository(s). As it turns out, I think the concerns raised in KULRICE-1320 will essentially go away since the projects generated by createproject.groovy will no longer be using the Maven plugin for Eclipse (which was what was establishing the dependency on the rice project). In summary, I think we are going to be where we want to be when this work is done
          Hide
          Ailish Byrne added a comment -

          cool

          Show
          Ailish Byrne added a comment - cool
          Hide
          Eric Westfall added a comment -

          Closing this issue, see specific details on KULRICE-1675

          Show
          Eric Westfall added a comment - Closing this issue, see specific details on KULRICE-1675

            People

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

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 2 hours
                2h
                Remaining:
                Remaining Estimate - 2 hours
                2h
                Logged:
                Time Spent - Not Specified
                Not Specified

                  Structure Helper Panel