[
https://issues.apache.org/jira/browse/SLING-7140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16208825#comment-16208825
]
ASF GitHub Bot commented on SLING-7140:
---
Github user ieb closed the pull request at:
Github user ieb closed the pull request at:
https://github.com/apache/sling/pull/252
---
[
https://issues.apache.org/jira/browse/SLING-6850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16208602#comment-16208602
]
ASF GitHub Bot commented on SLING-6850:
---
Github user auniverseaway closed the pull request at:
Github user auniverseaway closed the pull request at:
https://github.com/apache/sling/pull/233
---
On Tue, Oct 17, 2017 at 10:19 PM, Stefan Seifert wrote:
>
>
>>-Original Message-
>>From: Justin Edelson [mailto:jus...@justinedelson.com]
>>Sent: Tuesday, October 17, 2017 3:04 PM
>>To: dev@sling.apache.org
>>Subject: Re: [git] Migration scheduled for 18 Oct, 22:00
>-Original Message-
>From: Justin Edelson [mailto:jus...@justinedelson.com]
>Sent: Tuesday, October 17, 2017 3:04 PM
>To: dev@sling.apache.org
>Subject: Re: [git] Migration scheduled for 18 Oct, 22:00 CEST and final
>notes
>
>On Tue, Oct 17, 2017 at 8:49 AM Robert Munteanu
On Tue, 2017-10-17 at 16:22 +0300, Robert Munteanu wrote:
> On Tue, 2017-10-17 at 13:03 +, Justin Edelson wrote:
> > On Tue, Oct 17, 2017 at 8:49 AM Robert Munteanu > >
> > wrote:
> >
> > >
> > >
> > > Perhaps the people that actually work with these multi-project
> >
Robert Munteanu created SLING-7204:
--
Summary: OSGi R6 annotations: default value of an empty array is
propagated as null
Key: SLING-7204
URL: https://issues.apache.org/jira/browse/SLING-7204
[
https://issues.apache.org/jira/browse/SLING-7171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Peltier resolved SLING-7171.
Resolution: Fixed
Assignee: Nicolas Peltier
Fix Version/s: pipes 1.2.0
+1
[
https://issues.apache.org/jira/browse/SLING-7185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16207739#comment-16207739
]
ASF GitHub Bot commented on SLING-7185:
---
GitHub user JEBailey opened a pull request:
[
https://issues.apache.org/jira/browse/SLING-7203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16207730#comment-16207730
]
Justin Edelson commented on SLING-7203:
---
One thing which could work would be to unwind the request
[
https://issues.apache.org/jira/browse/SLING-7203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16207721#comment-16207721
]
Justin Edelson commented on SLING-7203:
---
Thinking about this some more, unwinding the wrapping would
[
https://issues.apache.org/jira/browse/SLING-7185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16207713#comment-16207713
]
ASF GitHub Bot commented on SLING-7185:
---
Github user JEBailey closed the pull request at:
Github user JEBailey closed the pull request at:
https://github.com/apache/sling/pull/260
---
Justin Edelson created SLING-7203:
-
Summary: Sling Model Request-Scoped Caching Not Effective Across
Script Include Boundaries
Key: SLING-7203
URL: https://issues.apache.org/jira/browse/SLING-7203
On Tue, 2017-10-17 at 13:03 +, Justin Edelson wrote:
> On Tue, Oct 17, 2017 at 8:49 AM Robert Munteanu
> wrote:
>
> >
> >
> > Perhaps the people that actually work with these multi-project
> > extensions would like to comment? By a quick check we have:
> >
> > - models
On Tue, Oct 17, 2017 at 8:49 AM Robert Munteanu wrote:
>
>
> Perhaps the people that actually work with these multi-project
> extensions would like to comment? By a quick check we have:
>
> - models
>
>
The models bundles can be released independently, i.e. I've done a number
I see the main issues with a tighter coupling of API and Impl with the
according IT module or test-services bundle.
In the best case every bugfix or new feature should also be reflected in the
ITs.
So after thinking a bit more about it, I think it is fine to derive from our
general 1 module = 1
[
https://issues.apache.org/jira/browse/SLING-7181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert closed SLING-7181.
-
> Maven Sling Plugin: Add Incremental Build Support for Validation Mojo
>
[
https://issues.apache.org/jira/browse/SLING-7196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert closed SLING-7196.
-
> sling-mock: Make sure SlingContext.registerAdapter can overlay built-in
> adaptions
>
[
https://issues.apache.org/jira/browse/SLING-6976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert closed SLING-6976.
-
> ContentLoader.binaryFile() and ContentLoader.binaryResource() should try to
> derive mimetype from
[
https://issues.apache.org/jira/browse/SLING-6962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert closed SLING-6962.
-
> Sling Mock 1.x: Add support for further SlingHttpServletRequestMethods
>
[
https://issues.apache.org/jira/browse/SLING-7189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert closed SLING-7189.
-
> Misleading Artifact Coordinates message for ResourceResolverType.JCR_OAK
>
[
https://issues.apache.org/jira/browse/SLING-7193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert closed SLING-7193.
-
> osgi-mock: MockServiceReferences.compareTo reverses ordering
>
[
https://issues.apache.org/jira/browse/SLING-6986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert closed SLING-6986.
-
> The ResourceResolver mock does not test the resource type hierarchy in
> isResourceType
>
[
https://issues.apache.org/jira/browse/SLING-7089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert closed SLING-7089.
-
> MockNode should support getProperties(String[] nameGlob)
>
[
https://issues.apache.org/jira/browse/SLING-6947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert closed SLING-6947.
-
> MockHttpServletRequest incorrectly calculates pathInfo for path-bound servlets
>
[
https://issues.apache.org/jira/browse/SLING-6948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert closed SLING-6948.
-
> HttpServletResponse.getOutput() and getOutputAsString() return different
> information
>
Hi Christian,
Thanks for bringing this to the dev list. I have seen part of this
argument from various people, but until now no one has decided to
actually write about it :-)
On Tue, 2017-10-17 at 13:49 +0200, Christian Schneider wrote:
> I am bit concerned about the number of repositories we
Hi,
The vote has passed with the following result :
+1 (binding): Stefan Seifert, Daniel Klco, Robert Munteanu
I will copy this release to the Sling dist directory and
promote the artifacts to the central Maven repository.
stefan
Hi,
The vote has passed with the following result :
+1 (binding): Stefan Seifert, Robert Munteanu, Karl Pauls
I will copy this release to the Sling dist directory and
promote the artifacts to the central Maven repository.
stefan
Hi,
The vote passed with 3 binding votes.
I'll proceed with pushing out the release.
Cheers,
Stefan
On 10/10/17 14:49, "Stefan Egli" wrote:
>Hi,
>
>We solved 1 issue in this release:
>https://issues.apache.org/jira/browse/SLING/fixforversion/12341054
>
>Staging
+1
>-Original Message-
>From: Julian Sedding [mailto:jsedd...@gmail.com]
>Sent: Tuesday, October 17, 2017 12:30 PM
>To: Sling Developers List
>Subject: Re: [git] Migration scheduled for 18 Oct, 22:00 CEST and final notes
>
>Please go ahead with the migration.
>
+1
regards,
Karl
On Tuesday, October 17, 2017, Robert Munteanu wrote:
> On Tue, 2017-10-17 at 07:53 +, Radu Cotescu wrote:
> > Please vote to approve this release:
>
> +1
>
> Robert
--
Karl Pauls
karlpa...@gmail.com
I am bit concerned about the number of repositories we are about to create
on git and the relation between them.
Lets take an extension as an example:
validation
- reactor
- api
- core
- examples
- test-services
If I understand correctly then we plan to create one git repo for each
module
On Tue, 2017-10-17 at 12:28 +0100, Ian Boston wrote:
> Hi,
>
> On 17 October 2017 at 12:12, Robert Munteanu
> wrote:
>
> > On Tue, 2017-10-17 at 12:08 +0100, Ian Boston wrote:
> > > Hi,
> > > Could travis be used ?
> > >
> > >
Hi,
On 17 October 2017 at 12:12, Robert Munteanu wrote:
> On Tue, 2017-10-17 at 12:08 +0100, Ian Boston wrote:
> > Hi,
> > Could travis be used ?
> >
> > https://github.com/apache/sling/blob/trunk/.travis.yml
> >
> > I dont think that need personal access tokens or a
On Tue, 2017-10-17 at 13:15 +0200, Konrad Windszus wrote:
> Great, thanks for that. Is it possible to directly expose the last
> build result in the Github PR though? I guess the according Jenkins
> Plugin should support that Ootb.
The result is exposed, but for merged pull requests it's a bit
Great, thanks for that. Is it possible to directly expose the last build result
in the Github PR though? I guess the according Jenkins Plugin should support
that Ootb.
Konrad
> Am 17.10.2017 um 13:00 schrieb Robert Munteanu :
>
> Hi,
>
> In order to validate that we are
On Tue, 2017-10-17 at 12:08 +0100, Ian Boston wrote:
> Hi,
> Could travis be used ?
>
> https://github.com/apache/sling/blob/trunk/.travis.yml
>
> I dont think that need personal access tokens or a special technical
> uses
> as it uses OAuth.
>
> From memory the main problem with Travis +
Hi,
Could travis be used ?
https://github.com/apache/sling/blob/trunk/.travis.yml
I dont think that need personal access tokens or a special technical uses
as it uses OAuth.
>From memory the main problem with Travis + Sling is a) the size of the log
file (fixed for Sling see yml file) and b)
[
https://issues.apache.org/jira/browse/SLING-7185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16207497#comment-16207497
]
Jason E Bailey commented on SLING-7185:
---
Kept it Java 7 based, thanks for pointing out the IS08601
Hi,
In order to validate that we are able to validate pull requests without
nagging infra I added experimental pull request validation to the sling
site repo.
The results are visible in the jenkins job [1] and in an example pull
request [2].
The Jenkins job is multi-branch pipeline and it's
[
https://issues.apache.org/jira/browse/SLING-7185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16207276#comment-16207276
]
ASF GitHub Bot commented on SLING-7185:
---
GitHub user JEBailey opened a pull request:
GitHub user JEBailey opened a pull request:
https://github.com/apache/sling/pull/260
SLING-7185 Added support for ISO8601 parsing
Parsing is of a relatively strict format, requiring date, time, and offset.
Milliseconds to 3 decimals are required.
You can merge this pull request
Please go ahead with the migration.
Thanks
Julian
On Tue, Oct 17, 2017 at 12:12 PM, Bertrand Delacretaz
wrote:
> On Tue, Oct 17, 2017 at 11:52 AM, Robert Munteanu wrote:
>> ...I want to make
>> sure though that everyone is aware of these and and
On Tue, Oct 17, 2017 at 11:52 AM, Robert Munteanu wrote:
> ...I want to make
> sure though that everyone is aware of these and and considers that the
> SVN to Git migration can proceed...
I'm fine with that, thanks!
-Bertrand
Hi,
The discussions with infra are settling and I would like to schedule
the migration for tomorrow evening at 22:00 CEST. I am not sure of the
"downtime", but hopefully it won't be more than a couple of hours.
Some final notes:
- there is no access to features that require administrative
Hi,
I really do not think that my mistake trying to get a feature into Oak then
Sling warrants the extra work of experimental branches. I am certain those
waiting for the feature, can wait a little longer, failing that I am
reasonably certain that I can find a different way of introducing the
GitHub user cschneider opened a pull request:
https://github.com/apache/sling/pull/259
Update testing clients to newest snapshot
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cschneider/sling fix-testing-dependencies
Github user cschneider closed the pull request at:
https://github.com/apache/sling/pull/258
---
GitHub user cschneider opened a pull request:
https://github.com/apache/sling/pull/258
Fixing sightly dependencies and small test improvement
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cschneider/sling
[
https://issues.apache.org/jira/browse/SLING-7170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16207150#comment-16207150
]
Nicolas Peltier commented on SLING-7170:
fixed in r1812362, note intermittent, unrelated (but
GitHub user cschneider opened a pull request:
https://github.com/apache/sling/pull/257
Update old snapshot deps to current snapshots
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cschneider/sling fix-hc-samples-deps
On Tue, 2017-10-17 at 07:53 +, Radu Cotescu wrote:
> Please vote to approve this release:
+1
Robert
signature.asc
Description: This is a digitally signed message part
GitHub user cschneider opened a pull request:
https://github.com/apache/sling/pull/256
Update old snapshot deps to current releases and snapshots
Dependencies point to old snapshots that are not available anymore.
Updated to release where possible and to newest snapshot where no
[
https://issues.apache.org/jira/browse/SLING-7170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Peltier resolved SLING-7170.
Resolution: Fixed
Fix Version/s: pipes 1.2.0
> Add PipeModel
> -
>
>
[
https://issues.apache.org/jira/browse/SLING-7202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Peltier updated SLING-7202:
---
Attachment: success-fail-logs.tar
> o.a.j.o.j.o.ObservationManagerImpl times out eventually
On Mon, 2017-10-16 at 20:36 -0700, Chetan Mehrotra wrote:
> I think we should seriously consider the branching option and then
> release Sling bundles under some qualifier version like
> 1.4.7-BETA/1.4.7-EXPERIMENTAL.
>
> Similar approaches were used earlier in Felix to work on new in
>
[
https://issues.apache.org/jira/browse/SLING-7202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Peltier updated SLING-7202:
---
Attachment: (was: success-tests.log)
> o.a.j.o.j.o.ObservationManagerImpl times out
[
https://issues.apache.org/jira/browse/SLING-7202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Peltier updated SLING-7202:
---
Attachment: (was: failing-test.log)
> o.a.j.o.j.o.ObservationManagerImpl times out
[
https://issues.apache.org/jira/browse/SLING-7202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Peltier updated SLING-7202:
---
Attachment: success-tests.log
failing-test.log
pax exam logs when test fails
Hi,
We solved 1 issue in this release:
https://issues.apache.org/jira/projects/SLING/versions/12341679
Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-1803/
You can use this UNIX script to download the release and verify the
signatures:
Nicolas Peltier created SLING-7202:
--
Summary: o.a.j.o.j.o.ObservationManagerImpl times out eventually
in pax container init
Key: SLING-7202
URL: https://issues.apache.org/jira/browse/SLING-7202
> @Chetan. THere are 4-5 bundles to release. All may need other releases for
> other fixes critical to the current roadmap. I agree that doing an
> internal/experimenta/branched release of a one bundle on the periphery of
> Sling would be ok, but IMHO doing an experimental release of most of the
>
Hi,
@Julian
It would need the Oak S3 DataStore to have an dependency on Sling Adapter
factory and then do a Resource -> URI adaption for Resources that
represented a binary. No new API in Oak.
That said, I think we went down this rabbit hole and concluded that Oak
wasnt willing to have any
On Tue, 2017-10-17 at 08:47 +0200, Bertrand Delacretaz wrote:
> On Sun, Oct 8, 2017 at 7:13 PM, Robert Munteanu
> wrote:
> > ...I will start with bulk creating the repositories,..
>
> I know this has been delayed, but when you do it, are you planning to
> add default tags on
+1
regards,
Karl
On Tue, Oct 17, 2017 at 9:16 AM, Stefan Seifert wrote:
> one (binding) vote is missing... anyone?
>
> stefan
>
>
>>-Original Message-
>>From: Stefan Seifert [mailto:sseif...@pro-vision.de]
>>Sent: Monday, October 16, 2017 9:00 AM
>>To:
one (binding) vote is missing... anyone?
stefan
>-Original Message-
>From: Stefan Seifert [mailto:sseif...@pro-vision.de]
>Sent: Monday, October 16, 2017 9:00 AM
>To: dev@sling.apache.org
>Subject: RE: [VOTE] Release Apache Sling Maven Sling Plugin 2.3.4
>
>one (binding) vote is
On Sun, Oct 8, 2017 at 7:13 PM, Robert Munteanu wrote:
> ...I will start with bulk creating the repositories,..
I know this has been delayed, but when you do it, are you planning to
add default tags on the repositories? If possible I suggest "apache,
sling, apache-sling" as
Hi Ian
How and where was access to the javax.net.URI instance implemented?
To my understanding the problem is consuming the changed Oak API in
Sling. The additional Sling API should be no problem as it does not
create a dependency to Oak. What am I missing?
Regards
Julian
On Mon, Oct 16, 2017
72 matches
Mail list logo