On 29/07/10 15:05, Jody Garnett wrote: >> **<licenses> >> **<scm><url> >> **<scm><connection> >> **<developers> >> ** If the project packaging is jar, and the jar file contains java classes, >> there must be a -javadoc.jar for main artifact. >> ** If the project packaging is jar, there must be a -sources.jar for main >> artifact. >> ** All project artifacts are signed using GPG,
I have a bunch of artifacts that are jars of GML application schemas used for GeoTools and GeoServer testing. Maven is the ideal way of distributing these so we can use them for offline testing. (app-schema-resolver enables schema resolution in these artifacts on the classpath.) None of them have sources or javadoc. I am just the packager, not the developer. Don't even get me started on the licensing or scm arrangements (these schemas are developed by international information standards communities that appear to have avoided addressing licensing issues). Also, how do we manage GPG signing keys? Any chance of fixing download.osgeo.org? I liked what we had. -- Ben Caradoc-Davies <ben.caradoc-dav...@csiro.au> Software Engineering Team Leader CSIRO Earth Science and Resource Engineering Australian Resources Research Centre ------------------------------------------------------------------------------ The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
