Some general notes on the top-level stuff. I suggest we ignore
sandbox and soc directories for the purpose of the Maven conversion.
I'd like to keep "sandbox" free-form, so that committers could check
in whatever they want in there. It should not be a part of any
automated build either. "soc" is a sandbox for the Google Summer of
Code projects, so it also doesn't fit into the Maven tree.
> site - static docs and java doc (why are the java doc's checked in?)
We had ant-based automation for javadocs generation in the past.
Since the build systems (and repositories) across 1.0/1.1/1.2/3.0 are
incompatible, I ended up checking in the static docs to avoid cross-
version build nightmare. Once we start talking about migrating the
site to Maven (it will be migrated later per your comment), let's re-
think it.
> In main we need to add a top level pom
>
> groupId - org.apache.cayenne
> arifactId - cayenne-parent
+1
see cayenne/cayenne-ant/maven/ directory for templates with general
info. But are probably past that point already.
> 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.
+1.
> sandbox;
> ....
> soc;
> ...
See my comment above - I suggest that we leave them out.
Andrus
This archive was generated by hypermail 2.0.0 : Fri Jul 21 2006 - 11:19:40 EDT