Hi Martin, Please see below. On Aug 8, 2013, at 11:04 AM, Martin Desruisseaux <[email protected]> wrote:
> 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? I think something is a miss here, but do not worry about it. What you did now seem to work, after the release is out of the way, we can optimize this step. An easy way will be to use maven profiles, but I am sure there are better alternatives. > 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. Unfortunately, this is normal. I do not know the reason why maven does it this way, but this came up on other lists few times with no resolution. So I would suggest to live with it, this is nothing you are doing and its default maven release plugin behavior. > > 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? I do not know if deleting files will cause any harm when the repo is released and jars published. We should find out. This reminds of me this cartoon - http://xkcd.com/242/ :) Anyway, lets pretend to be scientists and keep deleting the source zips and web site descriptors which I also agree are unnecessary in maven repo. You might already have noticed the vote template which you may find useful - http://sis.apache.org/templates/release-vote.txt Suresh > > Thanks, > > Martin > > > [1] > http://maven.apache.org/guides/mini/guide-configuring-plugins.html#Using_the_reporting_Tag_VS_build_Tag > [2] https://repository.apache.org/content/repositories/orgapachesis-075/
