On 5 September 2016 at 17:33, Gary Gregory <[email protected]> wrote: > I've never used finalName, I'm surprised we'd need this.
I think it's to trick the assembly plugin to make apache-commonsrdf-0.2.0-incubating.tar instead of commons-rdf-parent-0.2.0-incubating.tar (and equivalent subdirectory inside) But for the 0.2.0 we had the problem that we got both a -source and -src tar.. so we've got too many assembly plugin executions! (I'm looking at https://github.com/apache/commons-codec as example) Is it right that most Commons components have explicit assembly config files bin and src? If I go with that then I can get rid of <finalName> - and thus avoid the confusing "apache-commonsrdf-0.3.0-incubating-SNAPSHOT.jar" which appears in both api/target and simple/target BTW - I struggle to enable all the reports as in https://commons.apache.org/proper/commons-codec/project-reports.html but I only get javadoc and test-javadoc. Do you know how I should build it to get the reports? I tried with "mvn site". >> This seems to be a new problem with maven-jar-plugin 3.0.0 - fighting >> with the assembly plugin or the bundle plugin? It was double-execution of <goal>jar</goal> - fixed. -- Stian Soiland-Reyes http://orcid.org/0000-0001-9842-9718
