Return-Path: X-Original-To: apmail-maven-dev-archive@www.apache.org Delivered-To: apmail-maven-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0388E17AD9 for ; Sat, 30 May 2015 12:02:28 +0000 (UTC) Received: (qmail 98478 invoked by uid 500); 30 May 2015 12:02:27 -0000 Delivered-To: apmail-maven-dev-archive@maven.apache.org Received: (qmail 98412 invoked by uid 500); 30 May 2015 12:02:27 -0000 Mailing-List: contact dev-help@maven.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Maven Developers List" Reply-To: "Maven Developers List" Delivered-To: mailing list dev@maven.apache.org Received: (qmail 98401 invoked by uid 99); 30 May 2015 12:02:27 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 30 May 2015 12:02:27 +0000 Received: from robertscholte.dynamic.ziggo.nl (5248749D.cm-4-1b.dynamic.ziggo.nl [82.72.116.157]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 0D0D21A01AB for ; Sat, 30 May 2015 12:02:26 +0000 (UTC) Content-Type: text/plain; charset=iso-8859-15; format=flowed; delsp=yes To: "Maven Developers List" Subject: Re: Problems with Jenkins builds of invoker and assembly plugins References: Date: Sat, 30 May 2015 14:02:21 +0200 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Robert Scholte" Message-ID: In-Reply-To: User-Agent: Opera Mail/12.17 (Win32) Unittests fixed with http://svn.apache.org/r1682598 Op Sun, 03 May 2015 21:27:37 +0200 schreef Robert Scholte : > Op Fri, 01 May 2015 22:59:05 +0200 schreef Dennis Lundberg > : > >> 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? > > https://jira.codehaus.org/browse/MNG-4565 fixes AND-activation. > > I think Dan Tran tried to do a fixed, but discovered too late that the > introduced dependency requires Java6. > The strategy is already to move the plugin requirements to both Maven3 > and JDK6, so this is probably no issue. > For now the plugin is in a bad condition, so maybe it is better to > revert those last commits and reopen the related issue, since the plugin > requires special attention due to maven-compat requirement for Maven3. > >> >> 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 >> / to >> , but I dare not change the tests. >> > > If it is about path separators, I can have a look. Normally it shouldn't > be too hard to let it work for both separators. > You could also add an Assumption[1] to the test... > > Robert > > [1] http://junit.sourceforge.net/javadoc/org/junit/Assume.html > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org > For additional commands, e-mail: dev-help@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For additional commands, e-mail: dev-help@maven.apache.org