this solved the problem in sling-mock.
still failing because the same problem occurred in sling-mock-oak, should be 
fixed in rev. 1756606

i will create a ticket for updating to the latest maven-jar-plugin in our 
parent pom.

the reason it failed only in sling-mock is that there a tests jar is 
additionally published as artifact. may affect other projects as well where 
this is the case.

stefan

>-----Original Message-----
>From: Stefan Seifert [mailto:[email protected]]
>Sent: Wednesday, August 17, 2016 9:17 AM
>To: [email protected]
>Subject: RE: Build failed in Jenkins: sling-trunk-1.8 #3788
>
>updated to maven-jar-plugin 3.0.2 in the sling-mock project in rev.
>1756581
>let's see if this helps on jenkins.
>
>stefan
>
>>-----Original Message-----
>>From: Konrad Windszus [mailto:[email protected]]
>>Sent: Wednesday, August 17, 2016 8:55 AM
>>To: [email protected]
>>Subject: Re: Build failed in Jenkins: sling-trunk-1.8 #3788
>>
>>Probably it is related to https://issues.apache.org/jira/browse/MJAR-
>227
>><https://issues.apache.org/jira/browse/MJAR-227> and
>>https://github.com/codehaus-plexus/plexus-archiver/issues/5
>><https://github.com/codehaus-plexus/plexus-archiver/issues/5> which is
>only
>>fixed with maven-jar-plugin 3.0.0.
>>Try if upgrading to 3.0.1 helps in your case.
>>Konrad
>>
>>> On 17 Aug 2016, at 08:43, Stefan Seifert <[email protected]>
>wrote:
>>>
>>>
>>>> [INFO] Apache Sling Testing Sling Mock .................... FAILURE
>[
>>>> 54.843 s]
>>> ...
>>>> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-jar-
>>>> plugin:3.0.0:test-jar (default) on project
>>org.apache.sling.testing.sling-
>>>> mock: Error assembling JAR: Problem creating jar: Execution
>exception:
>>Java
>>>> heap space -> [Help 1]
>>>
>>>
>>> hmm... this happens since i updated to sling parent pom 28 yesterday
>on
>>this project.
>>>
>>> can anyone reproduce this heap space problem on building locally? (i
>>cannot currently)
>>>
>>> is 512MB heap space not engough for the maven build?
>>>
>>> stefan
>
>


Reply via email to