Hi Martin, This looks like a great example to have, but my first impression is this belongs to a wiki. The dist locations should only have the releasable artifacts which you nicely staged at - https://dist.apache.org/repos/dist/dev/sis/0.3/RC2/
So it might be better not to have the maven folder. Once you stage the release and close the repo, they anyway are accessible publicly from - https://repository.apache.org/content/repositories/staging/org/apache/sis/core/ Suresh On Aug 14, 2013, at 11:09 AM, Martin Desruisseaux <[email protected]> wrote: > Le 14/08/13 16:31, Mattmann, Chris A (398J) a écrit : >> Maybe I misunderstood -- what exactly is the Maven test project doing? > > It just a trivial Maven project which declare all SIS modules as dependencies > (i.e. we simulate an external project that would use SIS) and executes all > SIS tests. The purpose is to: > > * Download all files from the Nexus staging repositories (provided > that the developer cleaned his local > "~/.m2/repository/org/apache/sis" first) in order to ensure that > they are not corrupted. > * Ensure that the checksums deployed on the Maven repository are okay. > * Ensure that the tests still pass when all modules co-exists on the > classpath (as opposed to the module-by-module tests performed in a > normal Maven build). > > > For the next release, the only things to modify are: > > * The number in <version>...</version>. > * The URL in <repository>...</repository>, which shall point to the > Nexus staging directory (different for each release). > > > Martin >
