Mailing-List: contact dev-help@archiva.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@archiva.apache.org
MIME-Version: 1.0
In-Reply-To: <e607f371-c159-d0e4-4e80-7cce8b67866b@gmail.com>
References: <5297448.YYAiAJHa12@golgafrichnam> <CAPoyBqRayxXD9V-Yfo1AtknrCAQF6RerGxyaAnW1dLFb94W6hQ@mail.gmail.com>
 <e607f371-c159-d0e4-4e80-7cce8b67866b@gmail.com>
From: Olivier Lamy <olamy@apache.org>
Date: Tue, 25 Oct 2016 09:14:46 +1100
Message-ID: <CAPoyBqQF-_BR384=FcWWoaDcH1t_piTd1sdBrTz0Ce0uaJZoDg@mail.gmail.com>
Subject: Re: Failed builds
To: "dev@archiva.apache.org" <dev@archiva.apache.org>
Content-Type: multipart/alternative; boundary=001a114c996840435b053fa3b86b
archived-at: Mon, 24 Oct 2016 22:14:49 -0000

--001a114c996840435b053fa3b86b
Content-Type: text/plain; charset=UTF-8

Haha
Not sure to have the patience try convincing infra for that ;-)

On Monday, 24 October 2016, Hadrian Zbarcea <hzbarcea@gmail.com> wrote:

> Using a local instance of archiva as a proxy would speed downloads up
> significantly :).
>
> Hadrian
>
>
> On 10/23/2016 08:05 PM, Olivier Lamy wrote:
>
>> well.
>> Ideally that should be same plugin version in main build and archetype.
>> As the archetype build try to resolve locally to avoid downloading
>> everything again.
>> But there is probably few versions mismatch.
>> A solution is to not using local but download everything (this will make
>> build longer)
>>
>> On 23 October 2016 at 19:56, Martin Stockhammer <m.stockhammer@web.de>
>> wrote:
>>
>> Hi,
>>>
>>> the builds are currently very unstable. The ubuntu-eu nodes seem to be
>>> different, so I excluded them in the build config.
>>>
>>> The archiva-master-empty-repo fails always at the "Archiva Consumers ::
>>> Consumers Archetype" module. And mainly because of dependency failures.
>>> The archetype pom.xml has some hard coded build dependencies, that do not
>>> match the versions used in the builds before. E.g. maven-compiler-plugin
>>> is
>>> used in version 3.5.1.
>>>
>>> So I'm not sure where these versions come from and if these should be
>>> changed
>>> to match the current build environment. Otherwise it may help to add a
>>> repository to the archetype pom.xml, because the archetype tests do only
>>> look
>>> in the local repository that is filled by the dependencies of the modules
>>> before. There is no lookup to the central maven repository.
>>>
>>> archiva/archiva-modules/archiva-base/archiva-consumers/archiva-consumer-
>>> archetype/src/main/resourcesstatic/archetype-resources/pom.xml
>>>
>>> <build>
>>>     <pluginManagement>
>>>       <plugins>
>>>         <plugin>
>>>           <groupId>org.apache.maven.plugins</groupId>
>>>           <artifactId>maven-clean-plugin</artifactId>
>>>           <version>2.6.1</version>
>>>         </plugin>
>>>         <plugin>
>>>           <groupId>org.apache.maven.plugins</groupId>
>>>           <artifactId>maven-compiler-plugin</artifactId>
>>>           <version>3.2</version>
>>>         </plugin>
>>>         <plugin>
>>>           <groupId>org.apache.maven.plugins</groupId>
>>>           <artifactId>maven-resources-plugin</artifactId>
>>>           <version>2.7</version>
>>>         </plugin>
>>>         <plugin>
>>>           <groupId>org.apache.maven.plugins</groupId>
>>>           <artifactId>maven-jar-plugin</artifactId>
>>>           <version>2.5</version>
>>>         </plugin>
>>>         <plugin>
>>>           <groupId>org.apache.maven.plugins</groupId>
>>>           <artifactId>maven-surefire-plugin</artifactId>
>>>           <version>2.18.1</version>
>>>         </plugin>
>>>       </plugins>
>>>     </pluginManagement>
>>>     <plugins>
>>>       <plugin>
>>>         <groupId>org.apache.maven.plugins</groupId>
>>>         <artifactId>maven-compiler-plugin</artifactId>
>>>         <configuration>
>>>           <source>1.7</source>
>>>           <target>1.7</target>
>>>         </configuration>
>>>       </plugin>
>>>     </plugins>
>>>   </build>
>>>
>>>
>>>
>>
>>

-- 
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy

--001a114c996840435b053fa3b86b--