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_the_reporting_Tag_VS_build_Tag
[2] https://repository.apache.org/content/repositories/orgapachesis-075/
