Hi,

After doing some work on the Checkstyle Plugin today, I noticed that
several of our Jenkins jobs for plugins are failing. I looked into it
and found a couple of problems.

1. maven-invoker-plugin is added as a module in two different
profiles; java-6 and maven-3. The first one because it requires Java 6
and thee second one as a workaround for MNG-3814. The problem is that
the invoker plugin gets built if Java 6 OR Maven 3 is used. This fails
some of the Jenkins jobs. Is there a way to require Java 6 AND Maven 3
to activate a profile?

2. maven-assembly-plugin fails on Windows, and it fails for me locally
on Windows as well. This is due to *nix-style absolute path references
in outputDirectory in FileItemAssemblyPhaseTest. Not sure how to solve
this. In my own projects I simply changes from
<outputDirectory>/</outputDirectory> to
<outputDirectory></outputDirectory>, but I dare not change the tests.

-- 
Dennis Lundberg

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to