On 2015-08-08T20:20:25 +0200 Karl Heinz Marbaise <[email protected]> wrote:
> Hi, > Hello! > The first thing which i saw where the wrong SCM connections given: Corrected. I've actually switched to the https URIs, as those allow anonymous cloning and authenticated pushes. > Apart from that it would be helpfull to know which Maven version you are > using? How have you Maven called to generate the site ? Apache Maven 3.3.3 (NON-CANONICAL_2015-07-27T12:38:38_root; 2015-07-27T09:38:38+00:00) Maven home: /opt/maven Java version: 1.8.0_45, vendor: Oracle Corporation Java home: /usr/lib/jvm/java-8-openjdk/jre Default locale: en_GB, platform encoding: UTF-8 OS name: "linux", version: "4.0.7-2-arch", arch: "amd64", family: "unix" According to rfscholte in the Freenode IRC channel, I'm running into this known issue: https://issues.apache.org/jira/browse/MPIR-234 I've applied the workaround until it's fixed. > The first thing i stumbled over was the ssh-extension you are defining? > So are you really trying to deploy via ssh your maven artifacts? Apart > from that why are you using such an old version? There are newer > versions available: http://maven.apache.org/wagon/ Right. I'm actually now just updating this project, which hasn't had any kind of build updates since early 2012. I am deploying maven artifacts to a privately hosted server over ssh, in addition to deploying to Maven Central. I've not found a way to avoid including that extension in the POM file without having to edit the Maven super POM (changes to which will obviously be wiped out every time I upgrade the OS package). I'm using an old version simply because I haven't yet updated, and nothing told me it was out of date. > > Furthermore i have seen that you define plugins in your parent like this: > ... > Which should be done like this: Fixed, thanks. > which brings me to the next point you have defined the > maven-compiler-plugin in your jnull-core module like this: > ... OK. > > And then you can remove the definition of this in every submodule... > Also the definition of maven-jar-plugin which you did in the submodule > (jnull-core): > ... > > Should be done only in the parent only once within the pluginManagement > block... OK. > > See the docs of the archiver: > http://maven.apache.org/shared/maven-archiver/index.html which is > referenced from the doc site of the maven-jar-plugin: > https://maven.apache.org/plugins/maven-jar-plugin/jar-mojo.html > > I have seen also that you define the maven-sources-plugin in your core > module like this: > > Apart from the manifest part as mentioned for the maven-jar-plugin you > have defined explicit executions with binding to life cycle which is not > neccessary cause maven-sources-plugin is already bound to the life > cycle....And you should prevent using the goal 'jar' cause it will fork > the life cycle...Are you sure making source packages of your test code ? I'm not sure what you mean here. I agree about the forking and didn't actually realize I was still using those goals here (I switched to the non-forking variants on my other projects and apparently missed this one). I'm not sure what you mean by "Are you sure making source packages of your test code?". I have always distributed four jars per module in each of my projects: The sources jar, the compiled code jar, the javadoc jar, and the test-sources jar. > So i can give you a hint to read this: > > http://blog.soebes.de/blog/2015/04/04/maven-prerequisites/ Right, I had no idea it was deprecated. I think it originally went in because the versions plugin nagged me if I didn't use one. M --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
