Re: Build Failure in Trunk

Hi all, I checked out the trunk code to a new location and removed my existing M2 repository and do a mvn clean install. Still fails in same place. So I believe this should fail in clean repo. I am compiling this code in 1.6 JDK in Ubuntu 11.10. These are the only facts left for me to compare with

Re: Build Failure in Trunk

Still getting the same error. 1. Command is mvn clean install -DskipTests. 2. Please find the link [1] for the pastebin build log. [1] - http://pastebin.com/12x8F4UG On Thu, Jul 25, 2013 at 6:53 PM, Robert Munteanu wrote: > On Thu, Jul 25, 2013 at 3:04 PM, Dishara Wijewardana > wrote: > > On

Build failed in Jenkins: sling-trunk-1.6 #1770

See Changes: [cziegeler] SLING-2980 : Update to latest quartz scheduler 2.2.0 [cziegeler] Remove unused configuration property [rombert] SLING-2978 - Create tooling top-level directory and move maven and ide under it Moved the curr

Build failed in Jenkins: sling-trunk-1.6 » Apache Sling Launchpad Testing #1770

See -- [...truncated 348 lines...] INFO: Bundle org.apache.sling.scripting.javascript installed from slinginstall:org.apache.sling.scripting.javascrip

[jira] [Updated] (SLING-2789) deploying Sling 7-SNAPSHOT on Karaf fails

[ https://issues.apache.org/jira/browse/SLING-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz updated SLING-2789: Attachment: SLING-2789.2013-07-25.a.patch What do you mean with "BUILD part referenced in snapshots

[jira] [Created] (SLING-2980) Update to latest quartz scheduler 2.2.0

Carsten Ziegeler created SLING-2980: --- Summary: Update to latest quartz scheduler 2.2.0 Key: SLING-2980 URL: https://issues.apache.org/jira/browse/SLING-2980 Project: Sling Issue Type: New F

[jira] [Resolved] (SLING-2980) Update to latest quartz scheduler 2.2.0

[ https://issues.apache.org/jira/browse/SLING-2980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-2980. - Resolution: Fixed > Update to latest quartz scheduler 2.2.0 > ---

[jira] [Updated] (SLING-2912) Update to latest quartz scheduler 2.1.7

[ https://issues.apache.org/jira/browse/SLING-2912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-2912: Summary: Update to latest quartz scheduler 2.1.7 (was: Update to latest quartz scheduler)

[jira] [Created] (SLING-2979) Scheduled task should only run on leader

Carsten Ziegeler created SLING-2979: --- Summary: Scheduled task should only run on leader Key: SLING-2979 URL: https://issues.apache.org/jira/browse/SLING-2979 Project: Sling Issue Type: New

[jira] [Commented] (SLING-2789) deploying Sling 7-SNAPSHOT on Karaf fails

[ https://issues.apache.org/jira/browse/SLING-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719610#comment-13719610 ] Robert Munteanu commented on SLING-2789: I've applied the patch but we still have

[jira] [Updated] (SLING-2789) deploying Sling 7-SNAPSHOT on Karaf fails

[ https://issues.apache.org/jira/browse/SLING-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-2789: --- Attachment: SLING-2789-remove-BUILD-from-version.patch > deploying Sling 7-SNAPSHOT on Ka

Re: Build Failure in Trunk

On Thu, Jul 25, 2013 at 3:04 PM, Dishara Wijewardana wrote: > On Thu, Jul 25, 2013 at 11:22 AM, Carsten Ziegeler > wrote: > >> The first error you reported is fixed - now you're running into a new issue >> which I can't reproduce on my machine. I'm usually doing a full clean build >> with tests >

Re: Build Failure in Trunk

On 25 July 2013 14:17, Ian Boston wrote: > Hi Dishara, > mvn clean install worked for me thismorning at > oops somehow hit send. at: r1506645 I had to restart the build once because I hit a timeout in an integration test in org.apache.sling.event Ian > > > > On 25 July 2013 13:04, Dishara

[jira] [Resolved] (SLING-2978) Create tooling top-level directory and move maven and ide under it

[ https://issues.apache.org/jira/browse/SLING-2978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-2978. Resolution: Fixed > Create tooling top-level directory and move maven and ide under it

Re: Build Failure in Trunk

Hi Dishara, mvn clean install worked for me thismorning at On 25 July 2013 13:04, Dishara Wijewardana wrote: > On Thu, Jul 25, 2013 at 11:22 AM, Carsten Ziegeler >wrote: > > > The first error you reported is fixed - now you're running into a new > issue > > which I can't reproduce on my machi

Re: [ide] Moving the IDE tools to contrib

Given the discussions, I've moved the codebase from the whiteboard to tooling/ide. I've created a Sling job at https://builds.apache.org/view/S-Z/view/Sling/job/sling-ide-1.6/ and also applied exclusions for tooling/ide when building the sling-trunk-{1.6,1.7} jobs. The tooling/ide reactor is not y

[jira] [Commented] (SLING-920) Jenkins continuous integration setup

[ https://issues.apache.org/jira/browse/SLING-920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719599#comment-13719599 ] Robert Munteanu commented on SLING-920: --- Added sling-ide-1.6 job, set to build hourly

[jira] [Commented] (SLING-2978) Create tooling top-level directory and move maven and ide under it

[ https://issues.apache.org/jira/browse/SLING-2978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719592#comment-13719592 ] Robert Munteanu commented on SLING-2978: Moved the IDE tooling in http://svn.apac

[jira] [Commented] (SLING-920) Jenkins continuous integration setup

[ https://issues.apache.org/jira/browse/SLING-920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719590#comment-13719590 ] Robert Munteanu commented on SLING-920: --- Updated sling-trunk-{1.6,1.7} to ignore chan

Re: Build Failure in Trunk

On Thu, Jul 25, 2013 at 11:22 AM, Carsten Ziegeler wrote: > The first error you reported is fixed - now you're running into a new issue > which I can't reproduce on my machine. I'm usually doing a full clean build > with tests > Hi Carsten Sorry for the inconvenience. The initial error I posted w

[jira] [Updated] (SLING-2789) deploying Sling 7-SNAPSHOT on Karaf fails

[ https://issues.apache.org/jira/browse/SLING-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz updated SLING-2789: Attachment: SLING-2789.2013-07-25.patch adjust/update versions > deploying Sling 7

[jira] [Updated] (SLING-2789) deploying Sling 7-SNAPSHOT on Karaf fails

[ https://issues.apache.org/jira/browse/SLING-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz updated SLING-2789: Attachment: SLING-2789.20130725.patch adjust/update versions > deploying Sling 7-S

[jira] [Issue Comment Deleted] (SLING-2789) deploying Sling 7-SNAPSHOT on Karaf fails

[ https://issues.apache.org/jira/browse/SLING-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz updated SLING-2789: Comment: was deleted (was: adjust/update versions) > deploying Sling 7-SNAPSHOT on Karaf fails

[jira] [Updated] (SLING-2789) deploying Sling 7-SNAPSHOT on Karaf fails

[ https://issues.apache.org/jira/browse/SLING-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz updated SLING-2789: Attachment: (was: SLING-2789.20130725.patch) > deploying Sling 7-SNAPSHOT on Karaf fails >

[ide] VLT vs Resource-based (was: [ide] Moving the IDE tools to contrib)

Hi, On 7/24/13 11:42 PM, "Justin Edelson" wrote: > >On Wed, Jul 24, 2013 at 1:54 PM, Robert Munteanu wrote: > >>Once we can use VLT, we'll see what fits best. I admit that I have an >> inclination towards the resource-based API, but it's not my personal >> decision to make. >> > >I think to mak

[jira] [Commented] (SLING-2789) deploying Sling 7-SNAPSHOT on Karaf fails

[ https://issues.apache.org/jira/browse/SLING-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719368#comment-13719368 ] Carsten Ziegeler commented on SLING-2789: - I think we should follow our own conven

[jira] [Commented] (SLING-2666) [Tooling] Checking out resources fails if the DefaultGetServlet does not serve the content

[ https://issues.apache.org/jira/browse/SLING-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719366#comment-13719366 ] Stefan Egli commented on SLING-2666: Hi [~rombert], I like both suggestions, esp the

Re: [ide] Moving the IDE tools to contrib

+1 On Wed, Jul 24, 2013 at 10:42 AM, Robert Munteanu wrote: > On Wed, Jul 24, 2013 at 5:15 PM, Bertrand Delacretaz > wrote: > > On Wed, Jul 24, 2013 at 4:02 PM, Felix Meschberger > wrote: > >> ...create a top level "tooling" (or so) folder and put the "ide" and > "maven" stuff in there ?... >

Re: [ide] Moving the IDE tools to contrib

In general I think we can move the stuff to trunk as long as it doesn't break the build for everyone, even if the stuff is in flux and might be completely changed over time. We ahve consensus that we want to do this in the Sling project and having it in trunk gives it more visibility and the sooner