Re: mvn move of main code

From: Bill Dudney (bdudne..pache.org)
Date: Thu Jul 27 2006 - 18:33:26 EDT

  • Next message: Kevin Menard: "RE: mvn move of main code"

    Hi Andrus,

    I was just about to commit a bunch of changes to cayenne-java. Is now
    a good time?

    TTFN,

    -bd-

    On Jul 27, 2006, at 12:43 PM, Andrus Adamchik wrote:

    > Bill,
    >
    > could you please post a note to the list when you start moving
    > folders around? I started working on some changes related to the
    > pluggable query cache, so I may be checking in the code to cayenne-
    > java.
    >
    > Andrus
    >
    >
    > On Jul 26, 2006, at 8:07 AM, Bill Dudney wrote:
    >
    >> HI All,
    >>
    >> The move to a maven directory layout is going to be disruptive and
    >> I wanted to get everyone's take on how to handle it.
    >>
    >> for example;
    >>
    >> main/cayenne/cayenne-java/lib - to be removed
    >> main/cayenne/cayenne-java/lib-src - to be removed
    >> main/cayenne/cayenne-java/src/cayenne - to be moved to ..
    >> main/cayenne/cayenne-java/src/cayenne - to be moved to ..
    >> main/cayenne/cayenne-java/src/dvmodeler - to be moved to ..
    >> main/cayenne/cayenne-java/src/modeler - to be moved to ..
    >> main/cayenne/cayenne-java/src/regression - to be moved to their
    >> respective projects?
    >> main/cayenne/cayenne-java/src/tests - moved into their respective
    >> projects?
    >>
    >> Then once all the modules are moved there will be similar moves
    >> within each directory, i.e;
    >>
    >> main/cayenne/cayenne-java/cayenne/dtd/*.dtd -> main/cayenne/
    >> cayenne-java/cayenne/src/main/resources
    >> main/cayenne/cayenne-java/cayenne/resources/* -> main/cayenne/
    >> cayenne-java/cayenne/src/main/resources
    >> main/cayenne/cayenne-java/cayenne/java -> main/cayenne/cayenne-
    >> java/cayenne/src/main/java
    >>
    >> I'm getting started today and hope to be done by late tomorrow
    >> with the first cut (i.e. a build that gets a jar file into a local
    >> repo) that we can build on.
    >>
    >> It would be easiest for me to check things in incrementally (i.e.
    >> do one module at a time and check it in) with everyone
    >> understanding that the build will be hosed for a time. This is
    >> probably not the best way for our users but I wanted to get your
    >> take, would it be ok for the build to be hosed for a couple of
    >> days to a week? The other option of course is to branch but then
    >> we have to pull everything up from the main line into the branch.
    >> The Geronimo team went this way and its working OK but its not fun.
    >>
    >> Does anyone have any major outstanding changes that will be hard
    >> to merge as a result of these moves? If so can they be checked in
    >> now?
    >>
    >> Thoughts?
    >>
    >> TTFN,
    >>
    >> -bd-
    >>
    >



    This archive was generated by hypermail 2.0.0 : Thu Jul 27 2006 - 18:34:12 EDT