[jira] [Resolved] (SLING-11530) Jenkins Maven Build Failure due to violating rat checks in multimodule build

/b4ab2e0bb6a5361ebe71b3bb7e2cb443873e8f6e. > Jenkins Maven Build Failure due to violating rat checks in multimodule build > > > Key: SLING-11530 > URL: https://issues.apache.org/ji

[jira] [Updated] (SLING-11530) Jenkins Maven Build Failure due to violating rat checks in multimodule build

[ https://issues.apache.org/jira/browse/SLING-11530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-11530: Summary: Jenkins Maven Build Failure due to violating rat checks in multimodule build

[jira] [Closed] (SLING-3449) Build failure on sling trunk

[ https://issues.apache.org/jira/browse/SLING-3449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-3449. -- > Build failure on sling trunk > > > Key

[jira] [Closed] (SLING-3557) Build Failure from sling trunk

[ https://issues.apache.org/jira/browse/SLING-3557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-3557. -- > Build Failure from sling trunk > -- > >

[jira] [Closed] (SLING-7070) Build failure with Java 9 in maven-enforcer-plugin

[ https://issues.apache.org/jira/browse/SLING-7070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-7070. -- > Build failure with Java 9 in maven-enforcer-plu

[jira] [Closed] (SLING-7072) Build failure with Java 9 - unable to create javax script engine for javascript

[ https://issues.apache.org/jira/browse/SLING-7072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-7072. -- > Build failure with Java 9 - unable to create javax script engine for > java

[jira] [Commented] (SLING-7072) Build failure with Java 9 - unable to create javax script engine for javascript

TRUN issues due to alternative implementation. > Build failure with Java 9 - unable to create javax script engine for > javascript > --- > > Key: SLING-7072 > URL: https://

[jira] [Updated] (SLING-7072) Build failure with Java 9 - unable to create javax script engine for javascript

[ https://issues.apache.org/jira/browse/SLING-7072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-7072: --- Fix Version/s: Java Version Maven Plugin 1.0.0 > Build failure with Java 9 - unable to cre

[jira] [Updated] (SLING-7072) Build failure with Java 9 - unable to create javax script engine for javascript

[ https://issues.apache.org/jira/browse/SLING-7072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-7072: --- Component/s: Maven Plugins and Archetypes > Build failure with Java 9 - unable to cre

[jira] [Resolved] (SLING-7072) Build failure with Java 9 - unable to create javax script engine for javascript

/r1806875], [r1806913|https://svn.apache.org/r1806913] - added the javaversion-maven-plugin * [r1806917|https://svn.apache.org/r1806917] - used the new plugin in the parent pom > Build failure with Java 9 - unable to create javax script engine for > java

[jira] [Commented] (SLING-7072) Build failure with Java 9 - unable to create javax script engine for javascript

6275 is not yet fixed I have implemented a basic Maven plugin which does the same job and the antrun snippet and will discuss this proposal on dev@sling > Build failure with Java 9 - unable to create javax script engine for >

[jira] [Commented] (SLING-7072) Build failure with Java 9 - unable to create javax script engine for javascript

1 or newer, so once that is out we need to ask infra to install it, upgrade our jobs and only then add testing jobs for Java 9. > Build failure with Java 9 - unable to create javax script engine for >

[jira] [Commented] (SLING-7072) Build failure with Java 9 - unable to create javax script engine for javascript

.xml ./contrib/extensions/distribution/it/pom.xml ./contrib/extensions/slf4j-mdc/pom.xml ./installer/core/pom.xml ./installer/it/pom.xml ./launchpad/base/pom.xml ./parent/pom.xml ./tooling/maven/archetypes/servlet/pom.xml ./tooling/maven/archetypes/taglib/pom.xml {code} > Build failure with Java 9 -

[jira] [Commented] (SLING-7072) Build failure with Java 9 - unable to create javax script engine for javascript

the antrun execution altogether and write a small custom mojo to set the properties. I think we use the antrun plugin in other areas too, and a fix should be coming for MANTRUN-200 > Build failure with Java 9 - unable to create javax script engine for >

[jira] [Created] (SLING-7072) Build failure with Java 9 - unable to create javax script engine for javascript

Robert Munteanu created SLING-7072: -- Summary: Build failure with Java 9 - unable to create javax script engine for javascript Key: SLING-7072 URL: https://issues.apache.org/jira/browse/SLING-7072

[jira] [Resolved] (SLING-7070) Build failure with Java 9 in maven-enforcer-plugin

[ https://issues.apache.org/jira/browse/SLING-7070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-7070. Resolution: Fixed Fixed in [r1805732|https://svn.apache.org/r1805732] > Build failure w

[jira] [Created] (SLING-7070) Build failure with Java 9 in maven-enforcer-plugin

Robert Munteanu created SLING-7070: -- Summary: Build failure with Java 9 in maven-enforcer-plugin Key: SLING-7070 URL: https://issues.apache.org/jira/browse/SLING-7070 Project: Sling Issue

[jira] [Commented] (SLING-6135) ResourceEditor build failure on Jenkins

fix > ResourceEditor build failure on Jenkins > --- > > Key: SLING-6135 > URL: https://issues.apache.org/jira/browse/SLING-6135 > Project: Sling > Issue Type: Bug > Components: Exte

[jira] [Resolved] (SLING-6135) ResourceEditor build failure on Jenkins

[ https://issues.apache.org/jira/browse/SLING-6135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandro Boehme resolved SLING-6135. -- Resolution: Fixed Thanks for reporting [~rombert]! > ResourceEditor build failure on Jenk

[jira] [Updated] (SLING-6135) ResourceEditor build failure on Jenkins

bug/v0.4.6/node-v14-linux-x64' (1)}} * {{[ERROR] Error: Cannot find module './pre-binding'}} > ResourceEditor build failure on Jenkins > --- > > Key: SLING-6135 > URL: https://issues.apache.

[jira] [Updated] (SLING-6135) ResourceEditor build failure on Jenkins

[ https://issues.apache.org/jira/browse/SLING-6135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-6135: --- Attachment: resourceeditor_failure.txt > ResourceEditor build failure on Jenk

[jira] [Created] (SLING-6135) ResourceEditor build failure on Jenkins

Robert Munteanu created SLING-6135: -- Summary: ResourceEditor build failure on Jenkins Key: SLING-6135 URL: https://issues.apache.org/jira/browse/SLING-6135 Project: Sling Issue Type: Bug

Re: Trunk Build Failure

Ok, that did the trick. If I get a setup working I will debug it as I had a similar issue (JCR Calendar issues based on timezones) in the past. I also will see if I can reproduce it consistently. But at least I am now good to test my merge for a pull request. Thanks - Andy > On Mar 16, 2016,

Re: Trunk Build Failure

Ok, took some time to reproduce but it fails in the "Apache Sling Testing Modules Reactor” module. [INFO] Rat check: Summary of files. Unapproved: 3 unknown: 3 generated: 0 approved: 1 license. Rat.txt: *** Unapproved licenses: /Users/schaefa/Dropbox/Shared.De

Re: Trunk Build Failure

On Thursday 17 March 2016 09:52:13 Andreas Schaefer Sr. wrote: > Ok, took some time to reproduce but it fails in the "Apache Sling Testing > Modules Reactor” module. > > [INFO] Rat check: Summary of files. Unapproved: 3 unknown: 3 generated: 0 > approved: 1 license. > > Rat.txt: > >

Re: Trunk Build Failure

On Wed, 2016-03-16 at 17:01 -0700, Andreas Schaefer Sr. wrote: > There is another issue I encountered. The RAT plugin is complaining > about IntelliJ Module files (*.iml) files. > > I did include the exclude for **/*.iml but that is only local. I will > include the change to the Parent POM inside

Re: Trunk Build Failure

There is another issue I encountered. The RAT plugin is complaining about IntelliJ Module files (*.iml) files. I did include the exclude for **/*.iml but that is only local. I will include the change to the Parent POM inside the latest project but there are other POM files that do not have the e

Re: Trunk Build Failure

On Wednesday 16 March 2016 17:01:01 Andreas Schaefer Sr. wrote: > There is another issue I encountered. The RAT plugin is complaining about > IntelliJ Module files (*.iml) files. > > I did include the exclude for **/*.iml but that is only local. I will > include the change to the Parent POM inside

Re: Trunk Build Failure

Thanks for the hint. Wasn’t aware that Git would not remove these files during a merge but now I know. A nice “git clean” worked wonders. - Andy > On Mar 17, 2016, at 9:58 AM, Oliver Lietz wrote: > > On Thursday 17 March 2016 09:52:13 Andreas Schaefer Sr. wrote: >> Ok, took some time to reprod

Re: Trunk Build Failure

On Tue, Mar 15, 2016 at 9:33 PM, Andreas Schaefer Sr. wrote: > ...This line is causing the failure: > Assert.assertEquals(expected.getTimeZone().getRawOffset(), > actual.getTimeZone().getRawOffset()); ... Makes sense, good catch! I have changed the Calendar comparison method in https://issues.a

Re: Trunk Build Failure

I knew I saw that before and the issue is the Timezone. California does already have Daylight Savings Time and I would guess that’s the issue here. This line is causing the failure: Assert.assertEquals(expected.getTimeZone().getRawOffset(), actual.getTimeZone().getRawOffset()); inside org.apa

Re: Trunk Build Failure

On Tue, Mar 15, 2016 at 7:29 PM, Andreas Schaefer Sr. wrote: > Got the same when checked out the code from SVN:... Ok, I have no idea what's going on unfortunately, and the build also worked on Jenkins earlier today at https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.8/2850/org.apa

Re: Trunk Build Failure

Got the same when checked out the code from SVN: Andreass-MacBook-Pro:sling-trunk schaefa$ svn info Path: . Working Copy Root Path: /Users/schaefa/Dropbox/Shared.Development/AdobeAEM.projects/HW.AEM.Tooling.Development/apache.svn/sling-trunk URL: https://svn.apache.org/repos/asf/sling/trunk Repos

Re: Trunk Build Failure

On Tue, Mar 15, 2016 at 7:11 PM, Andreas Schaefer Sr. wrote: > ...Do I need to work with SVN?.. That shouldn't make a difference, Git catches up quite quickly AFAIK. Anyway, I have posted the md5 digests the code that I have, at https://paste.apache.org/nlui - if you think you might have a diffe

Re: Trunk Build Failure

I use git and this is the latest: git-svn-id: https://svn.apache.org/repos/asf/sling/trunk@1735140 Do I need to work with SVN? - Andy > On Mar 15, 2016, at 10:44 AM, Bertrand Delacretaz > wrote: > > Hi, > > On Tue, Mar 15, 2016 at 6:27

Re: Trunk Build Failure

Hi, On Tue, Mar 15, 2016 at 6:27 PM, Andreas Schaefer Sr. wrote: > Failed tests: > JcrModifiablePropertyMapTest>JcrPropertyMapTest.testJCRType:... That test passes for me at revision 1735149, with both jdk 1.7 and 1.8. -Bertrand

Trunk Build Failure

The current trunk of sling fails in the JCR Resource Resolver with these tests: Failed tests: JcrModifiablePropertyMapTest>JcrPropertyMapTest.testJCRType:76->JcrPropertyMapTest.testValue:258 expected:<-2880> but was:<-2520> JcrPropertyMapTest.testJCRType:76->testValue:258 expected:<

Re: snapshot deployment/build failure

2-14 at 13:35 +0100, Oliver Lietz wrote: > > > > hi, > > > > > > > > another build failure caused by a SNAPSHOT dependency: > > > > > > > > ERROR: Failed to parse POMs > > > > java.io.IOException: remote file operation fai

Re: snapshot deployment/build failure

On Tue, 2015-12-15 at 10:29 +0100, Oliver Lietz wrote: > On Monday 14 December 2015 17:11:00 Robert Munteanu wrote: > > Hi Olli, > > Hi Robert, >   > > On Mon, 2015-12-14 at 13:35 +0100, Oliver Lietz wrote: > > > hi, > > > > > > an

Re: snapshot deployment/build failure

On Monday 14 December 2015 17:11:00 Robert Munteanu wrote: > Hi Olli, Hi Robert, > On Mon, 2015-12-14 at 13:35 +0100, Oliver Lietz wrote: > > hi, > > > > another build failure caused by a SNAPSHOT dependency: > > > > ERROR: Failed to parse POMs > >

Re: snapshot deployment/build failure

Hi Olli, On Mon, 2015-12-14 at 13:35 +0100, Oliver Lietz wrote: > hi, > > another build failure caused by a SNAPSHOT dependency: > > ERROR: Failed to parse POMs > java.io.IOException: remote file operation failed: > <https://builds.apache.org/job/sling-

snapshot deployment/build failure

hi, another build failure caused by a SNAPSHOT dependency: ERROR: Failed to parse POMs java.io.IOException: remote file operation failed: <https://builds.apache.org/job/sling-contrib-1.7/ws/trunk> at hudson.remoting.Channel@55c16db1:jenkins-ubuntu-1404-4gb-437: hudson.remoting.ProxyExc

[jira] [Resolved] (SLING-5296) scripting.sightly.testing build failure due to snapshot dependency on discovery

=rev > scripting.sightly.testing build failure due to snapshot dependency on > discovery > --- > > Key: SLING-5296 > URL: https://issues.apache.org/jira/browse/SLING-5296 > Projec

[jira] [Updated] (SLING-5296) scripting.sightly.testing build failure due to snapshot dependency on discovery

[ https://issues.apache.org/jira/browse/SLING-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli updated SLING-5296: --- Fix Version/s: Launchpad Builder 9 > scripting.sightly.testing build failure due to snaps

[jira] [Commented] (SLING-5296) scripting.sightly.testing build failure due to snapshot dependency on discovery

ting starting a launchpad - which had this snapshot dependency to discovery. > scripting.sightly.testing build failure due to snapshot dependency on > discovery > --- > > Key: SLING-5296 &g

[jira] [Updated] (SLING-5296) scripting.sightly.testing build failure due to snapshot dependency on discovery

[ https://issues.apache.org/jira/browse/SLING-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli updated SLING-5296: --- Affects Version/s: Launchpad Builder 8 > scripting.sightly.testing build failure due to snaps

[jira] [Created] (SLING-5296) scripting.sightly.testing build failure due to snapshot dependency on discovery

Stefan Egli created SLING-5296: -- Summary: scripting.sightly.testing build failure due to snapshot dependency on discovery Key: SLING-5296 URL: https://issues.apache.org/jira/browse/SLING-5296 Project

[jira] [Created] (SLING-3557) Build Failure from sling trunk

Yogesh Upadhyay created SLING-3557: -- Summary: Build Failure from sling trunk Key: SLING-3557 URL: https://issues.apache.org/jira/browse/SLING-3557 Project: Sling Issue Type: Bug

[jira] [Assigned] (SLING-3557) Build Failure from sling trunk

[ https://issues.apache.org/jira/browse/SLING-3557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-3557: --- Assignee: Carsten Ziegeler > Build Failure from sling tr

[jira] [Resolved] (SLING-3557) Build Failure from sling trunk

- should be fixed now > Build Failure from sling trunk > -- > > Key: SLING-3557 > URL: https://issues.apache.org/jira/browse/SLING-3557 > Project: Sling > Issue Type: Bug > Components: Launchp

[jira] [Resolved] (SLING-3449) Build failure on sling trunk

fixes, for the launchpad builder we can use the snapshot as the release is currently under vote, for the testing project we can use the latest release instead. > Build failure on sling trunk > > > Key: SLING-3449 >

Re: Build failure on sling trunk

Thanks for reporting, David - should be fixed now Regards Carsten 2014-03-13 10:58 GMT+01:00 David Bosschaert : > Hi all, > > When trying to build sling on a fresh new machine I ran into two > issues that most Sling developers probably won't see as their local > maven repo has the old snapshot

[jira] [Updated] (SLING-3449) Build failure on sling trunk

[ https://issues.apache.org/jira/browse/SLING-3449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-3449: Fix Version/s: Launchpad Builder 7 > Build failure on sling tr

[jira] [Assigned] (SLING-3449) Build failure on sling trunk

[ https://issues.apache.org/jira/browse/SLING-3449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-3449: --- Assignee: Carsten Ziegeler > Build failure on sling tr

Build failure on sling trunk

Hi all, When trying to build sling on a fresh new machine I ran into two issues that most Sling developers probably won't see as their local maven repo has the old snapshot builds: [ERROR] Failed to execute goal on project org.apache.sling.launchpad: Could not resolve dependencies for project org

[jira] [Created] (SLING-3449) Build failure on sling trunk

David Bosschaert created SLING-3449: --- Summary: Build failure on sling trunk Key: SLING-3449 URL: https://issues.apache.org/jira/browse/SLING-3449 Project: Sling Issue Type: Bug

[jira] [Updated] (SLING-3449) Build failure on sling trunk

[ https://issues.apache.org/jira/browse/SLING-3449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Bosschaert updated SLING-3449: Attachment: fix-build-failures.diff > Build failure on sling tr

Re: Build Failure in Trunk

t;>>> >> > > >> >>>> >> >> >>>> >> >> >>>> >> > > > >> > > > > [INFO] [INFO] Building >> test-servlet-archetype-project >> >>>> >> > > > >> 0.0.1-SNAPSHOT >> >>>> >> > > > >>

Re: Build Failure in Trunk

unning without debug but it > is > >>>> >> > launching, > >>>> >> > > > your > >>>> >> > > > >> > > build > >>>> >> > > > >> > > > > fails to launch, hence the questions. > >>>> >> > > > >> > > > > > >>>> >> > > >

Re: Build Failure in Trunk

build.log 2>&1 >>>> >> > > > >> > > > > and when it finishes pastebin the build.log >>>> >> > > > >> > > > > >>>> >> > > > >> > > > >>>> >> > > > >> > > > Perhaps I have not understood what you told. I did >>>> exact &g

Re: Build Failure in Trunk

>> >> > > > >> > resources >

Re: Build Failure in Trunk

>> > > > >> > > > -Xnoclassgc disable class garbage collection >> >> > > > >> > > > -Xincgc enable incremental garbage >> collection >> >> > > > >> > > > -Xloggc:log GC status to a file with time >> >> stamps >> >> > >

Re: Build Failure in Trunk

; > default > >> > > > >> > > > -Xrs reduce use of OS signals by Java/VM > >> (see > >> > > > >> > > > documentation) > >> > > > >> > > > -Xcheck:jni perform additional checks for JNI > >> > > functions > >> >

Re: Build Failure in Trunk

>> > > > >> > > > >> > > > The -X options are non-standard and subject to change >> without >> > > > notice. >> > > > >> > > > >> > > > >> > > > >> > > > >> > > > >> > > > >>

Re: Build Failure in Trunk

; > > > > > >> > > > > On 27 July 2013 00:15, Dishara Wijewardana < > > > > >> ddwijeward...@gmail.com> > > > > >> > > > > wrote: > > > > >> > > > > > > > > >> >

Re: Build Failure in Trunk

t; > > > > > Can you do > > > >> > > > > > > mvn -X clean install -rf :sling-servlet-archetype > > > >> > > > > > > > > > >> > > > > > > And post the output to a paste bin. > > > >> > > > > > > > > &g

Re: Build Failure in Trunk

t; > >> > > > > > > On 26 July 2013 04:35, Dishara Wijewardana < > > >> > > ddwijeward...@gmail.com> > > >> > > > > > > wrote: > > >> > > > > > > > > >> > > > > >

Re: Build Failure in Trunk

in same > >> > place. > >> > > > So > >> > > > > I > >> > > > > > > > believe this should fail in clean repo. I am compiling > this > >> > code > >> > > in > >>

Re: Build Failure in Trunk

s is local to me. >> > > > > > > > >> > > > > > > > On Fri, Jul 26, 2013 at 6:30 AM, Dishara Wijewardana < >> > > > > > > > ddwijeward...@gmail.com> wrote: >> > >

Re: Build Failure in Trunk

; > > > > > > > > > > > > > [1] - http://pastebin.com/12x8F4UG > > > > > > > > > > > > > > > > > > On Thu, Jul 25, 2013 at 6:53 PM, Robert Munteanu < > &

Re: Build Failure in Trunk

On Thu, Jul 25, 2013 at 11:22 AM, Carsten Ziegeler < > > > > > > > >> cziege...@apache.org>wrote: > > > > > > > >> > > > > > > > > >> >>

Re: Build Failure in Trunk

doing a > > full > > > > > clean > > > > > > >> build > > > > > > >> >> with tests > > > > > > >> >> > > > > > > >> > Hi Carsten > &g

Re: Build Failure in Trunk

; > >> > in inside some sub module (Because the error I am getting when > > > > > building > > > > > >> in > > > > > >> > parent level is not very descriptive. Hence I went in side the > > > > failing > &

Re: Build Failure in Trunk

am getting the same when I go inside and build. > > > > >> > > > > >> > > > > >> 1. Does the build work with -DskipTests for you? > > > > >> 2. Can you paste somewhere ( pastebin, github gist etc ) the full > > > > >> command and build output? > >

Re: Build Failure in Trunk

;> Robert > > > >> > > > >> > > > > >> > > > > >> >> > > > >> >> Carsten > > > >> >> > > > >> >> > > > >> >> 2013/7/25 Dishara Wijewardana > > > >> >>

Re: Build Failure in Trunk

gt; >> > > >> >> 2013/7/25 Dishara Wijewardana > > >> >> > > >> >> > Hi all, > > >> >> > Does any body could build the tru

Re: Build Failure in Trunk

nk in clean repo with/without > tests > >> ? > >> >> > > >> >> > On Thu, Jul 25, 2013 at 6:28 AM, Dishara Wijewardana < > >> >> > ddwijeward...@gmail.com> wrote: > >> >> > > >> >> > > > >&

Re: Build Failure in Trunk

;> > ddwijeward...@gmail.com> wrote: >> >> > >> >> > > >> >> > > >> >> > > On Wed, Jul 24, 2013 at 1:18 PM, Carsten Ziegeler < >> >> cziege...@apache.org >> >> > >wrote: >> >> > > >> >> > >> Should be fixed no

Re: Build Failure in Trunk

>> > > On Wed, Jul 24, 2013 at 1:18 PM, Carsten Ziegeler < > >> cziege...@apache.org > >> > >wrote: > >> > > > >> > >> Should be fixed now > >> > >> > >> > > This is not yet fixed. I tried both ways. W

Re: Build Failure in Trunk

> >> > >> Should be fixed now >> > >> >> > > This is not yet fixed. I tried both ways. With tests and without tests. >> > My >> > > revision is 1506788. >> > > I am building from root level. And fails with following. >

Re: Build Failure in Trunk

- >> > > >> > > [INFO] >> > > >> > > [INFO] --- maven-antrun-plugin:1.7:run >> > > >> > > (set-bundle-required-execution-environment) @ >> > > sling-servlet-archetype &g

Re: Build Failure in Trunk

; > > > >> Should be fixed now > > > >> > > > > This is not yet fixed. I tried both ways. With tests and without > tests. > > > My > > > > revision is 1506788. > > > > I am building from root level. And fails with following. > > > > > > > > [INFO] > >

Re: Build Failure in Trunk

gt; > > This is not yet fixed. I tried both ways. With tests and without tests. > > My > > > revision is 1506788. > > > I am building from root level. And fails with following. > > > > > > [INFO] > > > > ---

Re: Build Failure in Trunk

t yet fixed. I tried both ways. With tests and without tests. > My > > revision is 1506788. > > I am building from root level. And fails with following. > > > > [INFO] > > > > [INFO] BUI

Re: Build Failure in Trunk

is is not yet fixed. I tried both ways. With tests and without tests. My > revision is 1506788. > I am building from root level. And fails with following. > > [INFO] > -------

Re: Build Failure in Trunk

[INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 30.506s [INFO] Finished at: Thu Jul 25 06:27:09 IST 2013 [INFO] Final Memory: 89M/975M

Re: Build Failure in Trunk

SLING-443 > > [echo] on 64bit platforms: MAVEN_OPTS="-Xmx512M > -XX:MaxPermSize=512M", > > see SLING-1782 > > [echo] > > > > > ** > > [INFO] Executed tasks &g

Re: Build Failure in Trunk

On Wed, Jul 24, 2013 at 5:02 AM, Dishara Wijewardana wrote: > Hi all, > I am building the trunk to build a latest pack to try deploy the > implementation. > I am seeing following when building the trunk with -Dtest.skip=true. Is > this a known issue? > > Try running with -DskipTests . IIRC it in

Re: Build Failure in Trunk

ources) > @ sling-servlet-archetype --- > [INFO] Not copying test resources > [INFO] > [INFO] --- maven-antrun-plugin:1.7:run (fix-crlfs) @ > sling-servlet-archetype --- > [INFO] Executing tasks > > main: > [INFO] >

Build Failure in Trunk

[INFO] Executing tasks main: [INFO] -------- [INFO] BUILD FAILURE [INFO] [INFO] Total time: 2.380s [INFO] Finished at: Wed Jul 24 07:28:14 IST 2013

Re: Sling Trunk Build Failure

Hi, There are all sorts of things that can go wrong on a fresh maven build from the central maven repo timing out to an intermediate proxy sending html instead of a pom.xml file. First: The version of mvn, since the output you have pasted doest contain quite as much feedback as I would have expect

Re: Sling Trunk Build Failure

) SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 30.095s [INFO] Finished at: Thu Jun 20 02:29:03 IST 2013 [INFO] Final Memory

Re: Sling Trunk Build Failure

. I will totally update the trunk and try build again. > Also, what kind of environment do you have? OS? Java Versions? Etc. > It is a Linux(Ubuntu) and Sun JDK 1.6.X. > Regards, > Dan > > > On 6/18/13 1:17 PM, "Dishara Wijewardana" wrote: > > >Hi all, &g

Re: Sling Trunk Build Failure

kind of environment do you have? OS? Java Versions? Etc. Regards, Dan On 6/18/13 1:17 PM, "Dishara Wijewardana" wrote: >Hi all, >I checked out the source from trunk and try to build from root. >Is this a known build failure. This occurs when building the trunk with or &

Sling Trunk Build Failure

Hi all, I checked out the source from trunk and try to build from root. Is this a known build failure. This occurs when building the trunk with or without tests. Have anybody came across with this ? [INFO] Apache Sling Launchpad Testing Fragment Bundle SKIPPED [INFO] Apache Sling Launchpad

Build failure in testing/samples/integration-tests

form dependent! [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 1:49.660s [INFO] Finished at: Sun Aug 05 00:49:01 IST 2012 [INFO] Final Memory: 20M/

Re: Build failure

ngServerSideTest): > > Server is not ready according to previous tests > > > > Tests run: 10, Failures: 10, Errors: 0, Skipped: 0 > > > > [WARNING] File encoding has not been set, using pla

Re: Build failure

hecking legal files in: > org.apache.sling.testing.samples.integrationtests-1.0.7-SNAPSHOT.jar > [INFO] Checking legal files in: > org.apache.sling.testing.samples.integrationtests-1.0.7-SNAPSHOT-sources.jar > [INFO] > [INFO] --- maven-failsafe-plugin:2.7.2:verify (verify) @ > org.

Build failure

rify) @ org.apache.sling.testing.samples.integrationtests --- [INFO] Failsafe report directory: /home/bhathiya/Apps/Sling/sling/testing/samples/integration-tests/target/failsafe-reports [WARNING] File encoding has not been set, using platform encoding UTF-8, i.e. build is platform dependent! [INFO

Re: Build failure

hiya Jayasekara > wrote: > > > Hi devs, > > > > When I try to build Sling from trunk, I get following error. Can you > please > > help me to fix that? > > > > [INFO] > > ---------

  1   2   >