>>>>> Karl Heinz Marbaise <[email protected]>: > based on what I can identify in your pom files/output is that in your > currenty configuration the maven-javadoc-plugin is configured to use the > goal: aggregate[1] which is a goal which forkes the lifecycle. There is > an equivalent "aggregate-no-fork"[2] which could be used instead...
Thanks! I will try that. (The purpose of the javadoc aggregate is to get a javadoc jar attached to the parent pom artifact, that I can link to with a javadoc banner in the README.) > The question is also why running javadoc everytime? Hm... I don't understand...? Could you clarify? > Apart from that you have configured the maven-source-plugin with the > goal "jar" which also forkes the lifecycle[3] this could be replaced by > using the "jar-no-fork" goal[4]. Ok, Thanks! Will try. > Furthermore your configuration can be simplyfied by using the junit-bom > instead of each dependency separately to import the dependencies for > junit-jupiter ... Thanks! I didn't know that. I will try this as well! (lots of improvements here) > The question is: Why have you bound the maven-resources-plugin to > validate life cycle phase? I guess because I needed the stuff copied in early in the build. I probably arrived there by experimentation. What phase should I use? > One thing: Why do you have configured wagon-ftp as extension? Copy/paste leftover from an earlier project. I wanted travis-ci to deploy to my own snapshot repo and there I initially used ftp, but have now transitioned to ssh, so this can be deleted (and well... this particular project is released to maven central so it doesn't need to put snapshots in a repo). I will remove it. Thanks again! --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
