Re: [ANN] Welcome Georg Henzler as our latest Sling committer!

Welcome, Georg! Looking forward to more free time now that you can commit your own patches :-) Robert On Fri, 2016-09-30 at 21:42 +0530, Chetan Mehrotra wrote: > Welcome Georg! > Chetan Mehrotra > > > On Fri, Sep 30, 2016 at 9:24 PM, Stefan Seifert de> wrote: > >

Re: sling attic / cleanup

On Fri, 2016-09-30 at 12:55 +, Stefan Seifert wrote: > i assume in samples/ there are also some candidates. I think it would be a good time to make a distinction between 'real' samples, i.e. here's how you do X with Sling and demos, which are complete applications. For samples I see for

[jira] [Commented] (SLING-6079) commons.messaging.mail build fails on Jenkins

[ https://issues.apache.org/jira/browse/SLING-6079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15537235#comment-15537235 ] Robert Munteanu commented on SLING-6079: Works here locally as well, not sure why it did not work

RE: moving sling to git

Hello, This seems like just the thing that Git Submodules may be useful for: https://git-scm.com/book/en/v2/Git-Tools-Submodules IF each sling module is its own repo there could conceivably still be one parent repo of some kind, which has a submodule for each other repo. Hope that helps the

Re: sling attic / cleanup

On Friday 30 September 2016 10:11:28 Carsten Ziegeler wrote: > Stefan Seifert wrote > > > discussed at the Sling Committer Round Table @ adaptTo() 2016 > > > > before taking steps like migration sling svn to git we should check if we > > have modules that are no longer relevant and maintained,

[jira] [Commented] (SLING-6079) commons.messaging.mail build fails on Jenkins

[ https://issues.apache.org/jira/browse/SLING-6079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15536565#comment-15536565 ] Oliver Lietz commented on SLING-6079: - [~rombert], please have a look. Adding {{apache-snapshots}}

Re: [ANN] Welcome Georg Henzler as our latest Sling committer!

Welcome Georg! Chetan Mehrotra On Fri, Sep 30, 2016 at 9:24 PM, Stefan Seifert wrote: > welcome, georg! > > stefan > >>-Original Message- >>From: Bertrand Delacretaz [mailto:bdelacre...@apache.org] >>Sent: Friday, September 30, 2016 3:41 PM >>To: dev >>Subject:

RE: [ANN] Welcome Georg Henzler as our latest Sling committer!

welcome, georg! stefan >-Original Message- >From: Bertrand Delacretaz [mailto:bdelacre...@apache.org] >Sent: Friday, September 30, 2016 3:41 PM >To: dev >Subject: [ANN] Welcome Georg Henzler as our latest Sling committer! > >Hi, > >I'm pleased to announce that the Sling PMC has elected

[jira] [Updated] (SLING-6083) htl-maven-plugin should not fail when source directory not found

[ https://issues.apache.org/jira/browse/SLING-6083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert updated SLING-6083: -- Fix Version/s: (was: HTL Maven Plugin 1.0.0) HTL Maven Plugin 1.0.2 >

[jira] [Created] (SLING-6084) htl-maven-plugin should provide skip parameter

Stefan Seifert created SLING-6084: - Summary: htl-maven-plugin should provide skip parameter Key: SLING-6084 URL: https://issues.apache.org/jira/browse/SLING-6084 Project: Sling Issue Type:

[jira] [Resolved] (SLING-6084) htl-maven-plugin should provide skip parameter

[ https://issues.apache.org/jira/browse/SLING-6084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert resolved SLING-6084. --- Resolution: Fixed Completed: At revision: 1762922 > htl-maven-plugin should provide skip

[jira] [Resolved] (SLING-6083) htl-maven-plugin should not fail when source directory not found

[ https://issues.apache.org/jira/browse/SLING-6083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert resolved SLING-6083. --- Resolution: Fixed Completed: At revision: 1762917 > htl-maven-plugin should not fail when

[jira] [Created] (SLING-6083) htl-maven-plugin should not fail when source directory not found

Stefan Seifert created SLING-6083: - Summary: htl-maven-plugin should not fail when source directory not found Key: SLING-6083 URL: https://issues.apache.org/jira/browse/SLING-6083 Project: Sling

[ANN] Welcome Georg Henzler as our latest Sling committer!

Hi, I'm pleased to announce that the Sling PMC has elected Georg as our new Sling committer, and he has accepted, please welcome ghenz...@apache.org ! Georg we do know you a bit already but if you want to honor the old tradition of new committers briefly introducing themselves to the list, feel

Re: job configuration rights at builds.apache.org jenkins

On Fri, 2016-09-30 at 11:59 +, Stefan Seifert wrote: > who can grant my user (sseifert) the appropriate rights in our > jenkins to configure jobs? > > they are now created automatically so I will not need to change them, > but at least for looking into the current configuration this would be

RE: Baseline Error When Building Sling

i assume you need to update the package version to 1.4 in this file [1] stefan [1] https://svn.apache.org/repos/asf/sling/trunk/bundles/commons/classloader/src/main/java/org/apache/sling/commons/classloader/package-info.java >-Original Message- >From: Daniel Klco

[context-aware config] context path strategy depending on request information?

on the adaptTo() conference there was feedback from one participant after my talk [1]: - he asked if it is possible to provide different context-aware configuration for different hostnames, but with the same content path - i assume this is some tenant-specific solution where all tenants share

Re: Preparing Launchpad 9 Release

Okay, that should be very doable. I'm 80-90% sure all of the code changes are there. I'm just running into a wall trying to test it out, I opened another email thread to discuss that issue. On Fri, Sep 30, 2016 at 9:18 AM, Carsten Ziegeler wrote: > Daniel Klco wrote > >

Baseline Error When Building Sling

Hey All, Maybe, I'm missing something completely obvious, but why am I getting the following baseline error when I attempt to build the Sling reactor? I've made a couple uncommitted changes there and have updated the snapshot version to 1.4.0-SNAPSHOT, but it still is bombing out the build. Any

Re: sling attic / cleanup

Daniel Klco wrote > I think we should make this a table instead of a list. This lets us keep > track for each dependency we're proposing to put into the attic: > >- Last update (excluding pom.xml or license changes) >- Where the code is referenced (if anywhere) > > Otherwise, it's going

Re: Preparing Launchpad 9 Release

Daniel Klco wrote > I'd also like to include the changes I've been meaning to make for > normalizing the scripting cache clear. Affected modules are: > >- org.apache.sling.commons.classloader >- org.apache.sling.commons.fsclassloader >- org.apache.sling.scripting.jsp > > What's the

[jira] [Updated] (SLING-5900) Improve create agents API handling of duplicate IDs

[ https://issues.apache.org/jira/browse/SLING-5900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simone Tripodi updated SLING-5900: -- Attachment: SLING-5900.patch Hi there [~teofili], please find in attachment a first proposal to

Re: Preparing Launchpad 9 Release

I'd also like to include the changes I've been meaning to make for normalizing the scripting cache clear. Affected modules are: - org.apache.sling.commons.classloader - org.apache.sling.commons.fsclassloader - org.apache.sling.scripting.jsp What's the target release date for Launchpad

Re: sling attic / cleanup

I think we should make this a table instead of a list. This lets us keep track for each dependency we're proposing to put into the attic: - Last update (excluding pom.xml or license changes) - Where the code is referenced (if anywhere) Otherwise, it's going to be really difficult for

RE: Preparing Launchpad 9 Release

>I'm wondering about sub system support. I think this never really took >off, so I personally would rather remove all subsystem support for now. +1 stefan

RE: sling attic / cleanup

looks good to me, some comments on the current list: - contrib/extensions/bgservlets => serveral releases on it this year - contrib/scripting/groovy => last release this year - contrib/sling-s3 => is not so old, perhaps move below crankstart as it belongs to it? i assume in samples/ there are

Re: Preparing Launchpad 9 Release

On Fri, 2016-09-30 at 14:40 +0200, Carsten Ziegeler wrote: > Looking at the snapshot references from our launchpad project, I > think > there are only a few things to be done. (List is below) > > I think it should be doable to release all these things in the near > future and then get launchpad 9

[jira] [Resolved] (SLING-5642) Remove use of deprecated methods and update code to R6

[ https://issues.apache.org/jira/browse/SLING-5642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-5642. - Resolution: Fixed This has been done already, therefore resolving > Remove use of

Preparing Launchpad 9 Release

Looking at the snapshot references from our launchpad project, I think there are only a few things to be done. (List is below) I think it should be doable to release all these things in the near future and then get launchpad 9 out. I'm wondering about sub system support. I think this never

[jira] [Commented] (SLING-5685) Upgrade Commons IO to 2.5

[ https://issues.apache.org/jira/browse/SLING-5685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15535871#comment-15535871 ] Carsten Ziegeler commented on SLING-5685: - [~olli] Is there anything open here? > Upgrade Commons

[jira] [Commented] (SLING-5603) Upgrade Commons Lang to 3.4

[ https://issues.apache.org/jira/browse/SLING-5603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15535872#comment-15535872 ] Carsten Ziegeler commented on SLING-5603: - [~olli] Is there anything open here? > Upgrade Commons

[jira] [Resolved] (SLING-6079) commons.messaging.mail build fails on Jenkins

[ https://issues.apache.org/jira/browse/SLING-6079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz resolved SLING-6079. - Resolution: Fixed [r1762888|https://svn.apache.org/r1762888] > commons.messaging.mail build

[jira] [Comment Edited] (SLING-6081) Sling Content Package Maven Plugin

[ https://issues.apache.org/jira/browse/SLING-6081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15535853#comment-15535853 ] Stefan Seifert edited comment on SLING-6081 at 9/30/16 12:30 PM: - in the

[jira] [Closed] (SLING-6017) Streaming Uploads detection of request parameters is wrong.

[ https://issues.apache.org/jira/browse/SLING-6017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-6017. --- > Streaming Uploads detection of request parameters is wrong. >

[jira] [Commented] (SLING-6081) Sling Content Package Maven Plugin

[ https://issues.apache.org/jira/browse/SLING-6081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15535853#comment-15535853 ] Stefan Seifert commented on SLING-6081: --- in the mail thread there was a discussion about simplifying

[jira] [Commented] (SLING-6061) Create per-module Jenkins jobs

[ https://issues.apache.org/jira/browse/SLING-6061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15535848#comment-15535848 ] Robert Munteanu commented on SLING-6061: Definitely, I intend to do the same for contrib and

Re: Resource packaging/content packaging in Sling

Stefan Seifert wrote > i've created a new ticket for further discussion about a "sling content > package plugin" > https://issues.apache.org/jira/browse/SLING-6081 > > open in this thread is the "receiver part" to deploy content packages on > sling instances which is currently not possible

[jira] [Created] (SLING-6082) Add installer factory for content packages

Carsten Ziegeler created SLING-6082: --- Summary: Add installer factory for content packages Key: SLING-6082 URL: https://issues.apache.org/jira/browse/SLING-6082 Project: Sling Issue Type:

RE: Resource packaging/content packaging in Sling

i've created a new ticket for further discussion about a "sling content package plugin" https://issues.apache.org/jira/browse/SLING-6081 open in this thread is the "receiver part" to deploy content packages on sling instances which is currently not possible without 3rdparty applications.

[jira] [Created] (SLING-6081) Sling Content Package Maven Plugin

Stefan Seifert created SLING-6081: - Summary: Sling Content Package Maven Plugin Key: SLING-6081 URL: https://issues.apache.org/jira/browse/SLING-6081 Project: Sling Issue Type: New Feature

RE: Sling Launchpad and Sling Karaf features

>This all leads me to the suggestion that we keep the provisioning model >and generate the karaf features xml out of this. As the provisioning >model supports features already we can directly create the features in >the launchpad provisioning model as they are currently defined for karaf. +1

[jira] [Commented] (SLING-6061) Create per-module Jenkins jobs

[ https://issues.apache.org/jira/browse/SLING-6061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15535804#comment-15535804 ] Stefan Seifert commented on SLING-6061: --- this is cool, thanks a lot for the work robert. do we plan

Re: Sling Launchpad and Sling Karaf features

Stefan Seifert wrote > discussed at the Sling Committer Round Table @ adaptTo() 2016 > > currently we have Slind launchpad with a quite monolithic configuration [1] > one big list of all sling bundles), and we have a karaf feature repository > [2] with nicely cut features for different aspects

job configuration rights at builds.apache.org jenkins

who can grant my user (sseifert) the appropriate rights in our jenkins to configure jobs? they are now created automatically so I will not need to change them, but at least for looking into the current configuration this would be helpful. stefan

Re: sling attic / cleanup

Started a wiki page to collect the modules: https://cwiki.apache.org/confluence/display/SLING/Module+Cleanup -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org

[jira] [Commented] (SLING-3987) move from Subversion to Git

[ https://issues.apache.org/jira/browse/SLING-3987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15535733#comment-15535733 ] Stefan Seifert commented on SLING-3987: --- we discussed this topic again this week, new mail thread

Re: Streaming uploads.

Hi Ian, On Thu, Sep 8, 2016 at 2:12 PM, Ian Boston wrote: > ...Any objections if I cut a release of [1] and [2]. Sling Engine 2.6.4 and > Sling Post Servlets 2.3.14 with Streaming upload support I realize this is now released and that's fine, but are these new features

[jira] [Commented] (SLING-6078) add a fluent api to generate a sling pipe

[ https://issues.apache.org/jira/browse/SLING-6078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15535725#comment-15535725 ] Bertrand Delacretaz commented on SLING-6078: FWIW my initial idea was to allow using pipes

Re: Resource packaging/content packaging in Sling

On Fri, 2016-09-30 at 10:16 +0200, Carsten Ziegeler wrote: > Robert Munteanu wrote > > On Wed, 2016-09-28 at 21:49 +, Stefan Seifert wrote: > > > wcm.io also has a content package plugin [4] which already > > > replaces > > > parts oft he adobe content package maven plugin (upload/download > >

Re: Replace sling launchpad with karaf?

I think in general, this issue is a little bit more complex and actually consists of different issues. One of them is the other thread about "Sling Launchpad and Sling Karaf features". So we have to separate the discussion about the format we use to define an instance (provisioning model vs karaf

Re: Resource packaging/content packaging in Sling

Robert Munteanu wrote > On Wed, 2016-09-28 at 21:49 +, Stefan Seifert wrote: >> wcm.io also has a content package plugin [4] which already replaces >> parts oft he adobe content package maven plugin (upload/download >> package part), but not yet the part building the ZIP package from the >>

Re: sling attic / cleanup

Stefan Seifert wrote > discussed at the Sling Committer Round Table @ adaptTo() 2016 > > before taking steps like migration sling svn to git we should check if we > have modules that are no longer relevant and maintained, and moving them to > the "attic" (perhaps creating a new one for this). >

Re: pipes release 0.0.10

Hi, +1 this would be clearer indeed Thanks, Nicolas > On Sep 29, 2016, at 9:08 PM, Oliver Lietz wrote: > > On Thursday 29 September 2016 18:39:31 Nicolas Peltier wrote: >> Hi Oliver, >> >> fine with me :-) > > Looking closer... I *wonder* if not all pipes but BasePipe,