[m2] directory structure

From: Bill Dudney (bdudne..pache.org)
Date: Fri Jul 21 2006 - 08:08:14 EDT

  • Next message: Andrus Adamchik: "Re: Apache Confluence Migration"

    HI All,

    Part 2 of the Maven 2 move discussion...

    We have 5 logical repositories

    examples - what you'd expect
    main - where just about everything lives
    sandbox - future stuff, experiments
    site - static docs and java doc (why are the java doc's checked in?)
    soc - eclipse plugin(s)

    In main we need to add a top level pom

    groupId - org.apache.cayenne
    arifactId - cayenne-parent

    This pom will contain all the 'over all' info like mailing list info,
    license info, repositories etc.

    I'd like to leave site for later as I'm not quite as sure what to do
    there and it will take a bit of playing around with to get it right
    but essentially I'd like to remove the javadoc and other generated
    content, keep only the unique content and have it generate the 'root'
    site with the rest of the subprojects hanging off that root.

    I will also send main out in another email as this one is already too
    long...

    examples;

    1) add a pom to the root of the examples tree

            parent - org.apache.cayenne:cayenne-parent
            groupId - org.apache.cayenne.examples
            artifactId - examples-parent

    2) each example gets its own artifactId but shares the groupId with
    examples-parent

    3) directory changes - lots to do here
            3t-example - change to reflect the maven layout for web applications
    (src/main/java, src/main/webapp, etc)
            3t-example-client - add main/java to the src dir and move all the
    code under that
            cayenne-jpa-annotations-example - already an m2 layout, just update
    the pom
            cayenne-petstore - web layout, remove the dependencies and the
    generated war
            cross-db-example - move source and resources for m2 layout - make a
    manifest so this can be run with java -jar
            generic-mapping-example - move source and resources - make a
    manifest so this can be run with java -jar

            The examples all have Eclipse .project & .classpath files checked
    in. We can get rid of that after we finish the move to maven.

    I think examples is the place to start so we can get our feet wet but
    not impact too much. If everyone is in agreement I'll get started
    later today.

    sandbox;

    1) add a pom
            parent - org.apache.cayenne:cayenne-parent
            groupId - org.apache.cayenne.sandbox
            artifactId - sandbox-parent

    2) each module gets its own artifactId sharing the parent groupId

    3) derby-pool gets lib removed and src moved to reflect maven 2 layout

    soc;

    1) add a pom
            parent - org.apache.cayenne:cayenne-parent
            groupId - org.apache.cayenne.soc
            artifactId - soc-parent

    of the 3 modules in here only cayenne-rop seems to have anything in it.

    2) each module again shares the groupId and has its own artifactId

    3) directory changes -
            from what I can tell based on what is there we can drop the rob-
    browser directory and move everything in there up one level to
    cayenne-rop.
            a) remove lib, dist, .classpath, .project, .settings
            b) move META-INF, icons, and cayenne to the src/main/resources
    directory
            c) move the src/org director to src/main/java
    I've not used m2 for an eclipse plugin but from what I have Geronimo
    has so I'll check with them to make sure this is all a good thing
    before moving the stuff around.

    That is all for now.

    TTFN,

    -bd-

    This archive was generated by hypermail 2.0.0 : Fri Jul 21 2006 - 08:09:01 EDT