On Wed, 2019-01-23 at 08:28 -0600, Daniel Klco wrote:
> Rolling back to 1.3.3 resolves the issue. I see that it was added
> here:
>
> https://github.com/apache/sling-org-apache-sling-starter/commit/97d95644e9e20c46554fb005614f1a76af4fec60
>
>
> I don't see any other changes going along with that
Hi,
When including content packages in a feature model there are some
depenencies that would be great to check at build time. Both of these
are defined as manifest headers:
1. dependencies to other content pacakges - Content-Package-
Dependencies
2. dependencies to java packages - Import-Package
On Thu, 2019-01-24 at 13:04 +0100, Radu Cotescu wrote:
> Please vote to approve this release:
+1
Robert
signature.asc
Description: This is a digitally signed message part
On Thu, 2019-01-24 at 13:43 +0100, Andrei Dulvac wrote:
> but what's up with
> the non-semver versioning?
Technically speaking it's not non-semver :-)
You can use qualifiers in semantic versions, as it's hinted in item #9
from https://semver.org/ .
---x8---
A pre-release version MAY be denoted
On Fri, 2019-01-25 at 17:28 +0100, Oliver Lietz wrote:
> On Monday 21 January 2019 21:36:02 Oliver Lietz wrote:
> > Hi,
> >
> > We solved 1 issue in this release:
> > https://issues.apache.org/jira/browse/SLING/fixforversion/12344864
> >
> > Staging repository:
> > https://repository.apache.org/c
On Fri, 2019-01-25 at 18:25 +0100, Radu Cotescu wrote:
> Please vote to approve this release:
+1
Robert
signature.asc
Description: This is a digitally signed message part
On Wed, 2019-01-23 at 16:24 +, David Bosschaert wrote:
> I would suggest create a JIRA for it :)
Did just that :-)
https://issues.apache.org/jira/browse/SLING-8251
Robert
On Tue, 2019-01-29 at 15:27 +, dav...@apache.org wrote:
> Please vote to approve this release:
+1
Robert
signature.asc
Description: This is a digitally signed message part
Hi all,
I've finished migrating all the Jenkins jobs to the Multibranch
pipeline model. The builds should work unchanged as they did until now,
with some additions:
- commits and pull requests are validated and the status is set for
commits and pull requests
- email notifications have been disabl
Hi Jason and thanks for looking into the website's layout.
On Tue, 2019-01-29 at 18:12 +, j...@apache.org wrote:
> diff --git a/src/main/jbake/assets/res/css/site.css
> b/src/main/jbake/assets/res/css/site.css
> index 60982e1..1406da7 100644
> --- a/src/main/jbake/assets/res/css/site.css
> +++
Hi Radu,
On Mon, 2019-01-28 at 16:11 +, r...@apache.org wrote:
> added a simple script to update the Apache Reporter service after
> a release
This looks great, one more thing which we automate in the release
process :-)
Could I ask you to also mention it on the release management page,
Hi,
Sometimes we work on tasks that span multiple work items and it would
be good to capture these longer-term tasks under the umbrella of an
'Epic' Jira issue type.
Some examples I can think of:
- project-wide efforts like [1] or [2]
- large tasks like improvements to the Build/CI tooling like
Thanks!
On Thu, 2019-01-31 at 13:30 +0100, Radu Cotescu wrote:
> Hi Robert,
>
> > On 30 Jan 2019, at 12:58, Robert Munteanu
> > wrote:
> > - all jobs are now visible at https://builds.apache.org/job/Sling/
> > ,
> > older URLs are no longer valid
>
> I’ve
Hi Jason,
On Thu, 2019-01-31 at 09:20 -0500, Jason E Bailey wrote:
> So if you're looking at the list of apache projects that are web
> frameworks
> https://projects.apache.org/projects.html?category#web-framework
>
> You won't see us even though in our description we list ourselves as
> a web fr
On Thu, 2019-01-31 at 08:15 -0500, Jason E Bailey wrote:
> No, the breadcrumbs always had a trailing '>>' I don't think it looks
> good either but my initial attempt was structural. The css is
> straightforward to have it show up just between the links. I'll have
> that in place today.
Ah, ok, sor
On Fri, 2019-02-01 at 09:58 +, Apache Jenkins Server wrote:
> [ERROR] Unable to get artifact for Dependency
> {groupId=org.apache.sling,
> artifactId=org.apache.sling.launchpad.test-bundles, version=12-
> SNAPSHOT, type=slingfeature}: Could not find artifact
> org.apache.sling:org.apache.sling.
Hi,
In SLING-8019[1]/SLING-8266[2] and the associated PR [3] we're
discussing moving the XSS encoding utilities from the scripting-jsp-
taglib to a 'compat' bundle, now that we have the XSS bundle.
I propose to move the current 'helpers' package [4] and the esapi
bundle it embeds to a new bundle
Hi Stefan,
On Mon, 2019-02-11 at 20:36 +, Stefan Seifert wrote:
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-[YOUR
> REPOSITORY
> ID]/
I think you're missing the actual repository id here.
I know we can look it up from the nexus notifications but
On Tue, 2019-02-12 at 09:15 +, Stefan Seifert wrote:
> Please vote to approve this release:
+1
Robert
signature.asc
Description: This is a digitally signed message part
I assume that the usual
'This majority vote is open for at least 72 hours.'
still applies, right?
Anyway, building the project procidesc some interesting results:
1. Exported packages warnings
[INFO] --- bnd-maven-plugin:3.5.0:bnd-process (default) @
org.apache.sling.pipes ---
[WARNING]
/tmp
Hi David,
On Tue, 2019-02-12 at 16:44 +, dav...@apache.org wrote:
> new 6d3b2c0 Rename the sling.feature.apiregions.toglobal
> property to sling.feature.apiregions.joinglobal
May I suggest 'joinGlobal' instead of 'joinglobal'? It's subjective,
but I find it much more readable.
Thanks,
Hi,
We solved 5 issues in these releases:
https://issues.apache.org/jira/projects/SLING/versions/12344966
https://issues.apache.org/jira/projects/SLING/versions/12344306
Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-2048
You can use this UNIX script to dow
On Thu, 2019-02-14 at 10:17 +0100, Robert Munteanu wrote:
> Please vote to approve this release:
+1
Robert
signature.asc
Description: This is a digitally signed message part
Hi,
The vote has passed with the following result:
+1 (binding): Robert Munteanu, Carsten Ziegeler, Daniel Klco
I will copy this release to the Sling dist directory and promote the
artifacts to the central Maven repository.
Thanks all for voting.
Robert
On Mon, 2019-02-18 at 13:27 +, Apache Jenkins Server wrote:
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Failures:
> [ERROR] SlingJSPTaglibTest.testTaglib:80-
> >RenderingTestBase.assertContains:3
Failed to push the updated ITs after the latest JSP Taglib release.
Should be fixed now wit
Hi,
We solved 3 issues in this release:
https://issues.apache.org/jira/browse/SLING/fixforversion/12338588
Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-2049
You can use this UNIX script to download the release and verify the
signatures:
https://gitbox.
On Wed, 2019-02-20 at 11:36 +0100, Robert Munteanu wrote:
> Please vote to approve this release:
+1
Robert
signature.asc
Description: This is a digitally signed message part
Hi,
I was looking for the root cause of this failure. It looks like the
Sling repository startup failed once and then it was interrupted. The
interrupt happened during class initialisation and then the
InitialContent Oak class was marked as unavailable ( see stack traces
below ).
1st startup atte
On Fri, 2019-02-22 at 10:47 +, David Bosschaert wrote:
> Hi Robert,
>
> Regarding the question in the subject line "Why does loading classes
> reach
> into the service registry?"
> This is most likely to see if there are any registered weaving hooks
> which
> can weave the class bytes.
>
> Be
On Fri, 2019-02-22 at 12:41 +0100, Karl Pauls wrote:
> On Fri, Feb 22, 2019 at 12:35 PM Robert Munteanu
> wrote:
> > On Fri, 2019-02-22 at 10:47 +, David Bosschaert wrote:
> > > Hi Robert,
> > >
> > > Regarding the question in the subject line &quo
On Fri, 2019-02-22 at 11:46 +, David Bosschaert wrote:
> Hi Robert,
>
> The weaving hooks are potentially (if any are registered) run on the
> class
> bytes between the loading of the bytes and calling defineClass()
> IIRC, not
> sure what static initializers have to do with this as they are r
Hi,
We solved 2 issues in this release:
https://issues.apache.org/jira/browse/SLING/fixforversion/12326444
There are still some outstanding issues:
https://issues.apache.org/jira/browse/SLING/fixforversion/12345007
Staging repository:
https://repository.apache.org/content/repositories/orgapaches
Hi,
We solved 2 issues in this release:
https://issues.apache.org/jira/browse/SLING/fixforversion/12343866
Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-2051
You can use this UNIX script to download the release and verify the
signatures:
https://gitbox.apa
On Wed, 2019-02-20 at 11:36 +0100, Robert Munteanu wrote:
> This majority vote is open for at least 72 hours.
And still open :-) We need at least 2 other PMC votes for this to
go through.
Thanks!
Robert
On Mon, 2019-02-25 at 10:51 +0100, Robert Munteanu wrote:
> On Wed, 2019-02-20 at 11:36 +0100, Robert Munteanu wrote:
> > This majority vote is open for at least 72 hours.
>
> And still open :-) We need at least 2 other PMC votes for this to
> go through.
Let's try
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.
Thanks all for voting!
Robert
Hi,
The vote has passed with the following result :
+1 (binding): Daniel Klco, Carsten Ziegeler, Stefan Seifert
I will copy this release to the Sling dist directory and
promote the artifacts to the central Maven repository.
Thanks all for voting!
Robert
Hi,
The vote has passed with the following result :
+1 (binding): Daniel Klco, Carsten Ziegeler, Stefan Seifert.
I will copy this release to the Sling dist directory and
promote the artifacts to the central Maven repository.
Thanks all for voting!
Robert
On Wed, 2019-02-27 at 13:59 +0100, Karl Pauls wrote:
> Please vote to approve these releases:
+1
Robert
signature.asc
Description: This is a digitally signed message part
Hi Georg,
I think this looks good overall. One minor suggestion I would make
On Mon, 2019-03-04 at 17:50 +0100, Georg Henzler wrote:
> 2. Write a migration guide (replacing most information on page [4])
Maybe the information here should stay and a visible not be added to
the page which would poi
Hi,
Please find the draft board report below. I plan to submit it on
Monday, comments welcome.
## Description:
Apache Sling™ is a framework for RESTful web-applications based on an
extensible content tree.
## Issues:
Business continues as usual with individual module releases.
## Act
Hi,
I have been thinking lately about how we can improve our development
process for contributors/developers/release managers.
I have listed some issues that I perceived as important with proposed
solutions at
https://cwiki.apache.org/confluence/display/SLING/Scaling+Sling+Development
All comme
On Thu, 2019-03-07 at 10:33 +0100, Bertrand Delacretaz wrote:
> Hi
>
> On Wed, Mar 6, 2019 at 7:56 PM Daniel Klco wrote:
> > ...I wonder if a low effort option
> > would be to add a metadata field for the project(s) to link
> > documentation
> > pages in github, something like:..
> ...
> > tags=t
On Wed, 2019-03-06 at 17:19 +, Stefan Seifert wrote:
> > To spot those stale PRs we can consider building a dashboard of
> > open pull requests. Alternatively, an automated email once per
> > week to dev@sling mightalso work (or might get ignored).
>
> i think this would be very helpful. PRs
On Thu, 2019-03-07 at 16:22 +, Stefan Seifert wrote:
> Please vote to approve this release:
+1
Robert
signature.asc
Description: This is a digitally signed message part
On Thu, 2019-03-14 at 10:26 +0100, Carsten Ziegeler wrote:
> Please vote to approve this release:
+1
Robert
signature.asc
Description: This is a digitally signed message part
s 2052
To: "Sling Developers List"
Subject: [RESULT] [VOTE] Release Apache Sling Resource Merger 1.3.10
Hi,
The vote has passed with the following result :
+1 (binding): Robert Munteanu, Carsten Ziegeler, Radu Cotescu, Daniel Klco
I will copy this
On Tue, 2019-03-19 at 21:46 +0100, Karl Pauls wrote:
> Please vote to approve these releases:
+1
Robert
signature.asc
Description: This is a digitally signed message part
On Wed, 2019-03-20 at 14:47 +0100, Radu Cotescu wrote:
> Please vote to approve this release:
+1
> P.S. This mail was generated using the sling-cli tool that Robert
> mentioned yesterday.
+1 :-)
Thanks,
Robert
signature.asc
Description: This is a digitally signed message part
On Thu, 2019-03-21 at 11:57 +0100, Simone Tripodi wrote:
> Hi all,
> this email to propose to continue a tool development I started from
> the whiteboard[1] as a regular sub-project.
>
> The tool I started developing is about converting existing plain old
> JCR content-packages[2] to the new Sling
On Mon, 2019-03-25 at 01:09 +0100, Timothee Maret wrote:
> Please cast your vote.
+1, great to see this brought to Sling!
Thanks,
Robert
signature.asc
Description: This is a digitally signed message part
Hi Andrei,
On Mon, 2019-03-25 at 14:41 +0100, Andrei Dulvac wrote:
> I have a small doubt regarding
> org.apache.sling.distribution.journal.kafka
> and how well it will be maintained.
Well, don't leave us hanging :-) What is your small doubt about the
Kafka module?
Thanks,
Robert
On Mon, 2019-03-25 at 12:46 +0100, Radu Cotescu wrote:
> Please vote to approve this release:
+1
Robert
signature.asc
Description: This is a digitally signed message part
On Wed, 2019-03-27 at 15:42 +0100, Radu Cotescu wrote:
> Please vote to approve this release:
+1
Robert
signature.asc
Description: This is a digitally signed message part
Hi,
Radu and I have been working on a little tool to automate some of the
release work [1] (and maybe help with other stuff). See [2] for
background information.
As it's starting to take shape and become usable we'd like to move it
out of the whiteboard.
I suggest we use 'org.apache.sling.cli' a
On Fri, 2019-03-29 at 10:31 +0100, Bertrand Delacretaz wrote:
> On Fri, Mar 29, 2019 at 10:13 AM Robert Munteanu
> wrote:
> > ...I suggest we use 'org.apache.sling.cli' as the artifactId and
> > 'sling-
> > org-apache-sling-cli' as the repository.
Hi,
I think for some time we have overlooked the operational aspects of
Apache Sling and that it's high time to address this huge gap we have
between developing with Sling and operating with Sling.
One of the things that bothers me the most is that everything is
written in the _error_ log file. T
Hi Ruben,
On Fri, 2019-03-29 at 10:17 -0700, Ruben Reusser wrote:
> Robert,
>
> On 3/29/2019 8:59 AM, Robert Munteanu wrote:
> > Hi Ruben,
> >
> > On Fri, 2019-03-29 at 08:13 -0700, Ruben Reusser wrote:
> > > Robert,
> > >
> > > I think as
On Mon, 2019-04-01 at 12:04 +0200, Julian Sedding wrote:
> I agree with Bertrand that "org-apache-sling-cli" is too generic and
> may even be misleading for users of Sling.
>
> What about "org-apache-sling-committer-cli"? That makes it explicit
> that the tool is not generally useful, but only for
Hi Georg,
On Mon, 2019-04-01 at 14:47 +0200, Georg Henzler wrote:
> (although from a general direction I'd rather see this tooling in
> Jenkins because it can be better automated there)
I'll reply on the 'Scaling Sling Development' thread, since you added a
more comprehensive reply there.
Thank
Hi Georg,
On Fri, 2019-03-29 at 22:40 +0100, Georg Henzler wrote:
> Sorry for the late feedback, in general I really like the idea to
> improve the release process!
>
> The wiki states:
>
> > Many of these must be run by the release manager, since by
> > definition
> > releases are individual
On Mon, 2019-04-01 at 14:58 +0200, Georg Henzler wrote:
> So just out of interest: Is there ASF regulation that totally forces
> releases to be built on personal machines or could this in theory be
> done in an CICD pipeline (if the user identity is correctly
> propagated
> to fulfil "by definit
On Mon, 2019-04-01 at 16:11 +0200, Georg Henzler wrote:
> Hi Robert,
>
> thanks for clarifying!
>
> > ... It's an interesting read, if you have the time.
>
> [2] is a 94 messages thread, impressive.
>
>
> > The current ASF release policy is at [1], and it states that
> >
> > Before casting +1
On Mon, 2019-04-01 at 14:53 +0200, Georg Henzler wrote:
> > ...I wonder how many log analysis
> > scripts will need to be updated by downstream consumers
>
> I'm also a bit worried about that. I think the initial reason for
> error.log to be named like this is that httpd also uses error.log -
> I
sling.log? or status.log? Because it will still
> > > log
> > errors / exceptions in the success.log this way
> > > Greets,
> > > Roy
> > >
> > > > On 1 Apr 2019, at 09:19, Robert Munteanu
> > > > wrote:
> > > >
> >
1 at 09:19 +0200, Robert Munteanu wrote:
> Hi,
>
> I think for some time we have overlooked the operational aspects of
> Apache Sling and that it's high time to address this huge gap we have
> between developing with Sling and operating with Sling.
>
> One of the thi
Hi,
In yesterday's email conversation Roy Teeuwen suggested that we rename
the error.log file with sling.log or status.log, with multiple others
supporting the sling.log name.
I think we should discuss this in more depth. Some information I
collected from the previous threads:
- error.log is pro
Hi,
As per the below email:
- Google is launching the Google Summer of Docs, similar to the Google
Summer of Code
- There will be no umbrella org application from the ASF
- if interested, we can participate as an individual organisation
Do we have concrete tasks/projects where we would welcome a
n -
> redounded[5], so reducing the source of all the knowledge would
> benefit the whole ecosystem.
>
> @Carsten Ziegeler @Robert Munteanu what do you think?
>
> many thanks in advance!
> ~Simo
>
> [1]
> https://github.com/apache/sling-org-apache-sling-feature-
systems as well,
> > > and i
> > assume that on most production systems it's not used to log to INFO
> > level
> > but only for warnings, errors and so on.
> > > and the downstream changes required for this are huge -
> > > infrastructure
> >
On Tue, 2019-04-02 at 14:29 +0530, Nicolas Peltier wrote:
> imho error.log makes sense as a default logger, if the default
> appender's
> level is WARN or ERROR.
> may be we could be changing the default log level?
That is a good point, it contains much more that errors. What I think
we should bal
Hi Andy,
On Mon, 2019-04-08 at 10:23 -0700, Andreas Schaefer wrote:
> Hi
>
> On the AEM 6.5 GA release I encountered an issue where a customer is
> using XSSSupport but that is not in the Uber-jar nor is it in the
> 2.4.0 sling scripting jsp tag lib artifact.
>
> Is there a replacement for XSSSup
Hi Georg,
On Fri, 2019-04-12 at 00:47 +0200, Georg Henzler wrote:
> Hi all,
>
> I'm trying to add a config to the provisioning model [1] that is
> active
> during first startup at startlevel 5. Looking at [2] this does not
> seem
> to be possible (or it's not documented). On second startup it's
Hi Andy,
On Thu, 2019-04-11 at 17:59 -0700, Andreas Schaefer wrote:
> Hi
>
> I updated the Sling Project Archetype for Sling 11 and fixed a few
> issues.
>
> That said I am wondering what I need to do so that this can be
> released?
>
> Cheers - Andy Schaefer
I supposed you mean [1], right? Se
Hi Andreas,
On Thu, 2019-04-11 at 11:53 -0700, Andreas Schaefer wrote:
> Hi all
>
> Are they any plans to move sling starter to Feature Model or doing in
> a new model?
Judging by the silence I guess no one is working on it :-) Based on
some loose discussions with David and Karl this is doable,
On Fri, 2019-04-12 at 10:05 +0100, dav...@apache.org wrote:
> Please vote to approve this release:
+1
Robert
signature.asc
Description: This is a digitally signed message part
Hi Andy,
What are the proposed groupId / repository name?
Thanks,
Robert
On Fri, 2019-04-12 at 10:38 -0700, Andreas Schaefer wrote:
> Hi
>
> I updated the Sling Project Archetype project inside the Sling
> Whitebox project to Sling 11:
>
> https://github.com/apache/sling-whiteboard/tree/featu
On Thu, 2019-04-04 at 22:52 +0200, Timothee Maret wrote:
> The repository names derived from the package names and taking
> conventions
> into account would be the following
>
> sling-org-apache-sling-distribution-journal
> sling-org-apache-sling-distribution-journal-messages
> sling-org-apache-sl
On Mon, 2019-04-15 at 15:57 +0200, Karl Pauls wrote:
> Please vote to approve these releases:
+1
Robert
signature.asc
Description: This is a digitally signed message part
On Mon, 2019-04-15 at 11:49 +0300, Robert Munteanu wrote:
> On Thu, 2019-04-04 at 22:52 +0200, Timothee Maret wrote:
> > The repository names derived from the package names and taking
> > conventions
> > into account would be the following
> >
> > sling-org-
On Tue, 2019-04-16 at 08:19 +0200, Georg Henzler wrote:
> My proposal: We change the provisioning model in a way that all
> mentioned configurations become active exactly with the start level
> of
> org.apache.felix.configadmin. As this is the case from second startup
> on
> anyway, I suppose th
On Mon, 2019-04-01 at 14:58 +0200, Robert Munteanu wrote:
> On Mon, 2019-04-01 at 12:04 +0200, Julian Sedding wrote:
> > I agree with Bertrand that "org-apache-sling-cli" is too generic
> > and
> > may even be misleading for users of Sling.
> >
> >
ct-archetype sounds good to me.
I will create this repository tomorrow unless someone objects.
Thanks!
Robert
>
> At the end I leave this up to the Sling team.
>
> Thanks - Andy
>
> > On Apr 15, 2019, at 12:33 AM, Robert Munteanu
> > wrote:
> >
&g
Hi,
We have finished working on the SonarQube/SonarCloud integration for
Sling projects.
As of now SonarCloud will check and record quality metrics (coverage
included) for all Sling modules. PR analysis is also enabled.
I have documented this at [1], with some open issues:
- PRs seem to be proc
Hi Andy,
On Thu, 2019-04-18 at 18:04 -0700, Andreas Schaefer wrote:
> Hi
>
> Since a few days I try to make Sling Launchpad starting from a
> Feature Model of the Sling Starter kit.
>
> After I converted all the provisioning files to a FM I wanted launch
> it but that does failed due to javax de
Hi Patrique,
On Thu, 2019-04-18 at 14:37 +, Patrique Legault wrote:
> I am wondering if any of the developers have seen this issue?
>
> It is preventing us from logging into Composum and it seems to be
> with respect to the Eclipse Java Compiler within the Sling Compiler
> Bundle. We are runn
Hi Patrique,
On Thu, 2019-04-18 at 14:19 +, Patrique Legault wrote:
> Just out of curiosity will OSGi annotations used within Apache Sling
> integrate with JAX-RS annotations in order to create multiple
> POST/PUT/DELETE or GET endpoints within the same servlet?
>
> I believe this would give
On Thu, 2019-04-18 at 11:25 +0300, Robert Munteanu wrote:
> Hi Andy,
>
> On Mon, 2019-04-15 at 07:11 -0700, Andreas Schaefer wrote:
> > HI Robert
> >
> > As of now it is:
> >
> > org.apache.sling:sling-project-archetype
> >
> > Going alon
Don't care
[ ] -1 Don't release, because ...
This majority vote is open for at least 72 hours.
Regards,
Robert Munteanu
On Fri, 2019-04-19 at 13:37 +0300, Robert Munteanu wrote:
> Please vote to approve this release:
+1
Robert
signature.asc
Description: This is a digitally signed message part
On Fri, 2019-04-19 at 11:23 +0200, Timothee Maret wrote:
> Please vote to approve this release:
+1
Robert
signature.asc
Description: This is a digitally signed message part
> Cheers - Andreas Schaefer
>
> > On Apr 19, 2019, at 1:32 AM, Robert Munteanu
> > wrote:
> >
> > On Thu, 2019-04-18 at 11:25 +0300, Robert Munteanu wrote:
> > > Hi Andy,
> > >
> > > On Mon, 2019-04-15 at 07:11 -0700, Andreas Schaefer wro
or that matter like
> > Composum) leads me to the Starting Up page and it looks like Sling
> > is never getting out of the starting up page.
> >
> > Any help is appreciated.
> >
> > Cheers - Andy Schaefer
> >
> > > On Apr 19, 2019, at 12:27 AM, R
Hi,
The vote has passed with the following result:
+1 (binding): Radu Cotescu, Carsten Ziegeler, Robert Munteanu, Nicolas
Peltier
+1 (non-binding): none
I will copy this release to the Sling dist directory and
promote the artifacts to the central Maven repository.
Regards,
Robert Munteanu
On Wed, 2019-04-24 at 14:47 +0200, Christian Schneider wrote:
> s/jenkiona/jenkins/ :-)
I like Jenkiona :-)
Other that that - you're right, with the pipeline-based builds we
already have the 'build as a code' set up that Travis promises.
Additionally, we are able to have a 'marker' Jenkinsfile o
On Tue, 2019-04-23 at 11:28 -0700, Andreas Schaefer wrote:
> I followed this [1] for to setup the release management but I ran
> into an issue with GPG where the fingerprint is not adhering to the
> listed format in the page: fingerprint = part but it looks like this:
>
> gpg --fingerprint
> /V
On Wed, 2019-04-24 at 10:45 -0700, Andreas Schaefer wrote:
> Please vote to approve this release:
+1
Robert
signature.asc
Description: This is a digitally signed message part
On Thu, 2019-05-02 at 08:34 -0700, Andreas Schaefer wrote:
> The project is still on sling-whiteboard. Shall I delete the project
> from there as it is now its own git repo?
Yes, absolutely.
Robert
Hi Eren,
On Sat, 2019-05-04 at 23:26 +0300, Eren Erdemli wrote:
> Hi There,
>
> I have noticed a performance degration on oak:index/lucene,
>
> this happens when you reindex few times as it seems setting
> reindex=true
> also indexes the index data under /oak:index/lucene/:data which
> basically
1801 - 1900 of 11025 matches
Mail list logo
