Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.0
    • Component/s: Configuration
    • Labels:
      None

      Description

      • get rid of the ant/maven mix, switch to maven plugin for the project
      • update project documentation (e.g. setting up your dev environment)
      • If you want to check out multi maven module project you need this "extras" link: http://m2eclipse.sonatype.org/sites/m2e-extras
      • the suggestion is going to "project per module"

      This should be mentioned at the KTI before we plunge in headlong.

        Attachments

          Issue Links

            Activity

            Hide
            gilesp Peter Giles (Inactive) added a comment -

            Scott mentioned that sometimes the launch scripts get converted automatically and sometimes they don't. Sometimes you have to add the maven classpath container by hand, so keep an eye out for that.

            Show
            gilesp Peter Giles (Inactive) added a comment - Scott mentioned that sometimes the launch scripts get converted automatically and sometimes they don't. Sometimes you have to add the maven classpath container by hand, so keep an eye out for that.
            Hide
            gilesp Peter Giles (Inactive) added a comment -

            Did some work on this today, but Rice 1.1.0's maven modules are in a bad state. Travis says Garey is working on it, so I'm going to wait until his work completes before I go back for more.

            Show
            gilesp Peter Giles (Inactive) added a comment - Did some work on this today, but Rice 1.1.0's maven modules are in a bad state. Travis says Garey is working on it, so I'm going to wait until his work completes before I go back for more.
            Hide
            gilesp Peter Giles (Inactive) added a comment -

            Worked through a number of issues with doing "project per module" cleanly, but came upon what may be a show stopper: Each module ends up with its own .project and .settings/, and (unless there is a trick that I'm missing) there isn't inheritance going on here amongst the projects. What that means is that you can't set up something like the code templates for Rice in just the root project – instead you have to painfully repeat the configuration for each module. We could try to propagate these settings during the build, but that would put us back into ungainly hack territory.

            Someone mentioned that a new version of the m2eclipse plugin just came out so I'm going to try to download that next and see if it magically solves this problem. After that though, I'm pretty much stuck with trying "mulitple Maven modules mapped to a single Eclipse workspace project" which I've heard has has the major downside of unrealistic classpathing (everything munged together).

            I'm open to any and all super-awesome suggestions on this.

            Show
            gilesp Peter Giles (Inactive) added a comment - Worked through a number of issues with doing "project per module" cleanly, but came upon what may be a show stopper: Each module ends up with its own .project and .settings/, and (unless there is a trick that I'm missing) there isn't inheritance going on here amongst the projects. What that means is that you can't set up something like the code templates for Rice in just the root project – instead you have to painfully repeat the configuration for each module. We could try to propagate these settings during the build, but that would put us back into ungainly hack territory. Someone mentioned that a new version of the m2eclipse plugin just came out so I'm going to try to download that next and see if it magically solves this problem. After that though, I'm pretty much stuck with trying "mulitple Maven modules mapped to a single Eclipse workspace project" which I've heard has has the major downside of unrealistic classpathing (everything munged together). I'm open to any and all super-awesome suggestions on this.
            Hide
            gilesp Peter Giles (Inactive) added a comment -

            Brought this up in the KTI, and Jonathan suggested I might use svn externals to bring eclipse project settings down into each module from one authoritative source. It sounds like it would work, but would make branching more complex since the externals have absolute paths. If I can't come up with something better I'll try this.

            On that note, I did some googling around and I ran into this target for the maven eclipse plugin: http://maven.apache.org/plugins/maven-eclipse-plugin/m2eclipse-mojo.html
            Maybe using this we could get rid of the checked in eclipse project and generate our project files using 'mvn eclipse:m2eclipse' ? Worth a try.

            Show
            gilesp Peter Giles (Inactive) added a comment - Brought this up in the KTI, and Jonathan suggested I might use svn externals to bring eclipse project settings down into each module from one authoritative source. It sounds like it would work, but would make branching more complex since the externals have absolute paths. If I can't come up with something better I'll try this. On that note, I did some googling around and I ran into this target for the maven eclipse plugin: http://maven.apache.org/plugins/maven-eclipse-plugin/m2eclipse-mojo.html Maybe using this we could get rid of the checked in eclipse project and generate our project files using 'mvn eclipse:m2eclipse' ? Worth a try.
            Hide
            gilesp Peter Giles (Inactive) added a comment -

            I'm recusing myself from this one. m2eclipse is causing me great amounts of grief.

            Show
            gilesp Peter Giles (Inactive) added a comment - I'm recusing myself from this one. m2eclipse is causing me great amounts of grief.
            Hide
            jcoltrin Jessica Coltrin (Inactive) added a comment -

            Closing since these items are now in the release notes.

            Show
            jcoltrin Jessica Coltrin (Inactive) added a comment - Closing since these items are now in the release notes.

              People

              • Assignee:
                tschneeb Travis Schneeberger
                Reporter:
                gilesp Peter Giles (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: