Hey Martin, I normally just take the result of target/checkout/target (the zip and .asc and .md5 files) and upload that to dist/dev as the staging RC.
Looks right to me. RE: the reporting plugin, not sure how to fix that but wouldn't be surprised if you have to jerry rig it since I have to do that a lot with Maven (though I do love it!) Cheers, Chris ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: [email protected] WWW: http://sunset.usc.edu/~mattmann/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -----Original Message----- From: Martin Desruisseaux <[email protected]> Organization: Geomatys Reply-To: "[email protected]" <[email protected]> Date: Thursday, August 8, 2013 8:04 AM To: Apache SIS <[email protected]> Subject: Release attempt: facing Maven oddity >Hello all > >I'm trying to submit a release candidate for SIS but I'm facing 2 Maven >oddities. Does anyone can provide some light on the following issues? > > >1) Need to duplicate the maven-javadoc-plugin configuration >---------------------------------------------------- >In my understanding of the Maven documentation [1], the plugin >configuration in the <reporting> section should be used by "mvn site" >(that work well), but also by other goals. But it doesn't seem to work >for "mvn release" or "mvn install -Papache-release": the configuration >is ignored. I had to copy the maven-javadoc-plugin in both <reporting> >and <build> sections in order to get the plugin configured for both the >site generation and the "*-javadoc.jar" files to be deployed. Do I'm >doing something wrong? > > >2) Aggregated source files deployed to Maven repository: is it normal? >----------------------------------------------------------- >Maven does automatically the following: > > * deploy "*-sources.jar" files for each module (ok) > * create a source-release.zip file for the whole project (cool) > * deploy the above ZIP file in the parent directory of the SIS project > in the Maven repository (surprising) > > >Is the last item really a normal behaviour? This is the file that we are >suppose to put on dist/dev/sis. Having it on the Maven repository too >does not look like the right place to me. > >In the Maven repository to be part of the vote (later) [2], I deleted >that source ZIP file. I also deleted the site.xml files which were >deployed for each artifact having a "pom" packaging, since I can't see >why someone would want to have the Maven web site descriptors >deployed... Is it a correct thing to do? > >Thanks, > > Martin > > >[1] >http://maven.apache.org/guides/mini/guide-configuring-plugins.html#Using_t >he_reporting_Tag_VS_build_Tag >[2] https://repository.apache.org/content/repositories/orgapachesis-075/
