List-Unsubscribe

From: Peter Thompson (peter.thompso..unthered.com)
Date: Thu Jul 03 2008 - 15:39:36 EDT

  • Next message: Mike Schrag: "Re: how SHOULD it look"

    -----Original Message-----
    From: Pierce T. Wetter III [mailto:pierc..winforces.com]
    Sent: Friday, 4 July 2008 7:07 a.m.
    To: woproject-de..bjectstyle.org
    Subject: Re: Maven Skepticism

    On Jul 2, 2008, at 9:11 PM, Lachlan Deck wrote:

    > On 03/07/2008, at 10:00 AM, Pierce T. Wetter III wrote:
    >
    >>>> Yeah, as I said I read that, but that seems to assume you're
    >>>> making a new project rather then migrating an existing project to
    >>>> maven. Or are you implying the best way to migrate an old project
    >>>> is to generate a new project, then move the old project files
    >>>> into the new locations? I could see that, though of course it
    >>>> would give the source control system fits, so what I really need
    >>>> to do is make a new Maven WebObjects application, then copy files
    >>>> from it to the old project, and issue "svn mv" commands as
    >>>> appropriate until the old project structure mirrors the new layout.
    >
    > I've added some more stuff to the following page:
    >
    http://wiki.objectstyle.org/confluence/display/WOL/Maven+Kicking+the+tyr
    es+without+changing+your+project+structure
    >
    > It's kind of a scratch pad of ideas at the moment.

      I made some edits to make things much more explicit. Could you:

      1. Please review for accuracy.

      2. Add as attachments complete samples of:

       trunk/pom.xml
       trunk/frameworks/pom.xml
       trunk/frameworks/CustomBusinessLogic/pom.xml
       trunk/apps/pom.xml
       trunk/apps/ApplicationA/pom.xml

       I also think that this example would work better if the FBL changes
    were in trunk/pom.xml, rather then duplicated between [frameworks|
    apps]/pom.xml. I also think it would be better if more of the
    repositories and stuff was in trunk/pom.xml.

       That is, its seems to me that it would be much easier to "kick the
    tyres" if there was a pom.xml you could download, put in trunk/
    pom.xml, another one for your Frameworks directory, then define a
    minimal pom.xml for trunk/frameworks/YourFirstFramework/pom.xml and
    run a build.

       I'm saying that because I'm looking at your example apps/pom.xml
    and there are some plugins/repositories in there that you've figured
    out, that I don't want to have to! Seems like it should be possible
    for a maven expert to come up with an optimum trunk/pom.xml for people
    to start with, assuming they're using FBL.

      3. Extra Credit:

        Thinking about this some more, some great child documents to hang
    off of this document would be a series of annotated pom.xml examples,
    with snippets that could be added/removed. A maven cookbook if you
    will. Maybe if Henrique's pom patches ever show up in Wonder I can
    reverse engineer them and put them up there.

      Pierce



    This archive was generated by hypermail 2.0.0 : Thu Jul 03 2008 - 15:41:58 EDT