[
https://issues.apache.org/jira/browse/SLING-8340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simone Tripodi resolved SLING-8340.
---
Resolution: Fixed
Fix Version/s: slingfeature-maven-plugin 1.0.0
Fixed in
Simone Tripodi created SLING-8340:
-
Summary: APIs jar MOJO doesn't handle OSGi wrapper bundles
Key: SLING-8340
URL: https://issues.apache.org/jira/browse/SLING-8340
Project: Sling
Issue
[
https://issues.apache.org/jira/browse/SLING-8325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert closed SLING-8325.
-
> sling-mock: Overlay ContentBuilder.resource methods with variants to create
> child resources
>
[
https://issues.apache.org/jira/browse/SLING-8330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert closed SLING-8330.
-
> sling-mock: JUnit 5 Extension - Support setting context member field in super
> classes
>
[
https://issues.apache.org/jira/browse/SLING-8061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert closed SLING-8061.
-
> sling-mocks: Make compatible when Johnzon is managed to version 1.1
>
Hi,
The vote has passed with the following result :
+1 (binding): Stefan Seifert, Radu Cotescu, Nicolas Peltier
I will copy this release to the Sling dist directory and
promote the artifacts to the central Maven repository.
stefan
+1
Le lun. 1 avr. 2019 à 21:15, Radu Cotescu a écrit :
> +1
>
> > On 29 Mar 2019, at 18:58, Stefan Seifert wrote:
> >
> > Please vote to approve this release:
> >
> > [ ] +1 Approve the release
> > [ ] 0 Don't care
> > [ ] -1 Don't release, because ...
> >
> > This majority vote is open
rombert commented on issue #12: SLING-8335 :StringIndexOutOfBoundsException
from resolver.map with no…
URL:
https://github.com/apache/sling-org-apache-sling-resourceresolver/pull/12#issuecomment-478693582
A SonarQube report for the changes added _only by this pull request_ was
generated.
[
https://issues.apache.org/jira/browse/SLING-8339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu resolved SLING-8339.
Resolution: Fixed
Fixed with [sling-whiteboard commit
[
https://issues.apache.org/jira/browse/SLING-8339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu updated SLING-8339:
---
Attachment: sling-cli-error-thread-dump.txt
> CLI hangs when an unhandled exception occurs
>
Robert Munteanu created SLING-8339:
--
Summary: CLI hangs when an unhandled exception occurs
Key: SLING-8339
URL: https://issues.apache.org/jira/browse/SLING-8339
Project: Sling
Issue Type:
[
https://issues.apache.org/jira/browse/SLING-8328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu closed SLING-8328.
---
> The XSSFilterImpl component cannot start on Jboss 7 deployments
>
[
https://issues.apache.org/jira/browse/SLING-8321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu closed SLING-8321.
---
> The XSSFilterImpl component cannot start on IBM's J9 JVM
>
Hi,
The vote has passed with the following result:
+1 (binding): Karl Pauls, Stefan Seifert, Robert Munteanu
I will copy this release to the Sling dist directory and
promote the artifacts to the central Maven repository.
Regards,
Radu Cotescu
+1
> On 29 Mar 2019, at 18:58, Stefan Seifert wrote:
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] 0 Don't care
> [ ] -1 Don't release, because ...
>
> This majority vote is open for at least 72 hours.
Hi all,
this email to propose to continue a tool development I started from
the whiteboard[1] as a regular sub-project.
The subject APIs are to simplify the `api-regions` Feature extensions
manipulation, currently used in the ApisJarMojo[2] to produce APIs
JARs , but soon useful in other analysis
I also like sling.log.
It is is neutral in respect to error or not and clearly communicates the
purpose.
Christian
Am Mo., 1. Apr. 2019 um 13:30 Uhr schrieb Konrad Windszus :
> +1 to sling.log
> -1 to success.log (because errors are still contained in there)
>
> Konrad
>
> > On 1. Apr 2019, at
On Mon, 2019-04-01 at 07:57 -0400, Daniel Klco wrote:
> I'm assuming the timing of this announcement is not accidental.
> Having just
> returned from Adobe Summit and knowing they are one of the largest
> users of
> Apache Sling, why not aligning with what I heard at the event:
>
>
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 -
>
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
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 binding votes, individuals are REQUIRED to download
all signed source code
[INFO]
[INFO] [jenkins-event-spy] Generated
/home/jenkins/jenkins-slave/workspace/sling-launchpad-testing_master_2@tmp/withMaven63613a91/maven-spy-20190401-132810-45112928182256598521533.log
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-failsafe-plugin:2.21.0:verify (d
On Mon, Apr 1, 2019 at 2:58 PM Robert Munteanu wrote:
> ... org-apache-sling-committer-cli ...
Works for me - my concern, as echoed by others here, was that I'd
naturally think "cli" as being a tool for working *with* Sling, as
opposed to working *on* Sling.
-Bertrand
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
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
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.
I'm against the capricious classification of logging in general. Who are we to
say whether a log message is a success or failure, or whether a log is really
an error? Maybe the error wants to be a debug?
I'd rather go with the more type generic whatever-you-want-to-be.log or just
whatever.log
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
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 definition releases are individual acts in the Apache
Software
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 long as the 'maybe help with other stuff' part of your
Hi,
On 2019-04-01 13:30, Konrad Windszus wrote:
+1 to sling.log
-1 to success.log (because errors are still contained in there)
+1 for sling.log over success.log
...I wonder how many log analysis
scripts will need to be updated by downstream consumers
I'm also a bit worried about that. I
Hi Julian,
good point, it's the same difference as between dev@sling.apache.org and
us...@sling.apache.org, so maybe org-apache-sling-dev-cli would be good?
(although from a general direction I'd rather see this tooling in
Jenkins because it can be better automated there)
-Georg
On
I'm assuming the timing of this announcement is not accidental. Having just
returned from Adobe Summit and knowing they are one of the largest users of
Apache Sling, why not aligning with what I heard at the event:
[
https://issues.apache.org/jira/browse/SLING-8262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16806667#comment-16806667
]
Robert Munteanu commented on SLING-8262:
[~bellingard] - thanks to your PR I was able to progress
+1 to sling.log
-1 to success.log (because errors are still contained in there)
Konrad
> On 1. Apr 2019, at 10:18, Roy Teeuwen wrote:
>
> Hey Robert,
>
> Why not call it sling.log? or status.log? Because it will still log errors /
> exceptions in the success.log this way
>
> Greets,
> Roy
>
It seems no one except me has heared of the latest trend in logging:
logless?
Instead of renaming lets go all the way!
Regards
Carsten
Julian Sedding wrote
+1 One particular benefit of renaming would be the reduced number of
bug reports. That will give us more time to drink coffee.
[
https://issues.apache.org/jira/browse/SLING-8338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu updated SLING-8338:
Description: We should add a new command {{release nexus-release}} which
takes care of releasing
Radu Cotescu created SLING-8338:
---
Summary: Create sub-command to manage the Nexus stage repository
release when promoting a release
Key: SLING-8338
URL: https://issues.apache.org/jira/browse/SLING-8338
+1 One particular benefit of renaming would be the reduced number of
bug reports. That will give us more time to drink coffee.
Regards
Julian
On Mon, Apr 1, 2019 at 10:34 AM Nicolas Peltier
wrote:
>
> +1 i like that spirit.
>
> Le lun. 1 avr. 2019 à 12:49, Robert Munteanu a écrit :
>
> > Hi,
>
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 committers of
Sling?
Regards
Julian
On Fri, Mar 29, 2019 at
+1 i like that spirit.
Le lun. 1 avr. 2019 à 12:49, Robert Munteanu a écrit :
> 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
Neither of those names are accurate though. The file is just logs, there
isn't any reason to conclude that the contents are errors or successes.
The reality is a mix of log messages for lots of different reasons.
-Eric
On Mon, Apr 1, 2019, 12:19 AM Robert Munteanu wrote:
> Hi,
>
> I think for
Hey Robert,
Why not call it 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:
>
> Hi,
>
> I think for some time we have overlooked the operational aspects of
> Apache Sling and
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.
[
https://issues.apache.org/jira/browse/SLING-8335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16806435#comment-16806435
]
Ashok Kumar commented on SLING-8335:
[~rombert] Created the PR -
ashokpanghal opened a new pull request #12: SLING-8335
:StringIndexOutOfBoundsException from resolver.map with no…
URL: https://github.com/apache/sling-org-apache-sling-resourceresolver/pull/12
…n absolute path
check for absolute path at the beginning of the method
46 matches
Mail list logo
