Re: OSGi Installer Configuration - Primitive Arrays

wse/SLING-8314> as "Works as Designed" without merging the attached PR. Also I am gonna document the limitations of the write back (which are the same as the limitations of the .config file format). > On 14. Mar 2019, at 13:27, Karl Pauls wrote: > > On Thu, Mar 14, 2019 a

Re: OSGi Installer Configuration - Primitive Arrays

ache.org/jira/browse/SLING-8316>). Konrad > On 14. Mar 2019, at 14:06, Karl Pauls wrote: > > On Thu, Mar 14, 2019 at 1:53 PM Konrad Windszus <mailto:konra...@gmx.de>> wrote: >> >> To me it felt, like you argued against fixing the documentation and rather >>

Re: [VOTE][PROPOSAL] Promote the ContentPackage2FeatureModel whiteboard component as a regular Sling sub-project

Great and useful tool. Some questions around that: 1. From the readme at https://github.com/apache/sling-whiteboard/tree/master/content-package-2-feature-model#supported-configurations

Re: [RTC] Rename error.log to success.log

+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 >

Re: Travis builds for sling?

Hi Christian, this is explained in https://cwiki.apache.org/confluence/display/SLING/Sling+Jenkins+Setup . Konrad > On 24. Apr 2019, at 17:31, Christian Schneider > wrote: > > I also saw these single line Jenkinsfiles. The

Re: Request for a Sling Repository for the Sling Project Archetype

The check_stage_release.sh is always the same, i.e. you should not modify its URL. Only the parameters need to be modified to check the according staging area in Nexus. Please first run the check script according to your Vote Mail yourself before you send out the mail. Konrad > On 24. Apr 2019

Re: [RESULT] [VOTE] Release Apache Sling Project Archetype 1.0.0

Hi Andy, look at https://sling.apache.org/documentation/development/release-management.html#promoting-the-release , paragraph 2 on how you push to Maven Central. Konorad > On 1. May 2019, at 23:2

Re: Being prepared for "javax"

IMHO there is one other use case which is javax.activation.PostConstruct (https://jira.apache.org/jira/browse/SLING-7312 ) used from Sling Models. But I agree with Carsten that we should not think about this yet, as long as there is no definite pla

Re: [VOTE] Release Sling Default POST Servlets 2.3.30, Sling Form Based Authentication Handler 1.0.14, Sling Starter Content 1.0.4

+1 (checked signatures) Konrad > On 15. May 2019, at 22:58, Georg Henzler wrote: > > Hi, > > We solved 2 issues in this release: > https://issues.apache.org/jira/issues/?jql=project%20%3D%20SLING%20AND%20fixVersion%20in%20(%22Starter%20Content%201.0.4%22%2C%20%22Form%20Based%20Authentication%2

Re: [VOTE] Release Apache Sling Installer Health Checks 2.0.2

+1 Konrad > On 20. May 2019, at 18:25, Robert Munteanu wrote: > > Hi, > > We solved 3 issues in this release: > https://issues.apache.org/jira/browse/SLING/fixforversion/12343031 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-2082/ > > You can use

Re: Sling Hackathon in Berlin - September 2019?

I would like to participate as well. Topics to be discussed: - Current state of the Sling Feature Model - Other Deprecation Candidates Konrad > On 13. May 2019, at 12:46, Stefan Seifert wrote: > > this year's adaptTo() conference in berlin is from september 2nd-4th. we have > again the possib

Re: June board report draft

I kind of missed those steps as well in the past. I thought that this would be automatically done as soon as you push something to dist. Can we aim for a better automation here? Also from the script https://github.com/apache/sling-tooling-release/blob/master/update_reporter.sh

Re: Release automation (was: June board report draft)

tml>. I will definitely try that the next time I do a release. Konrad > On 13. Jun 2019, at 16:40, Robert Munteanu wrote: > > Hi Konrad, > > On Wed, 2019-06-12 at 16:33 +0200, Konrad Windszus wrote: >> I kind of missed those steps as well in the past. I thought that this >

OSGi DS 1.4 run time dependency with latest bundle parent

The latest sling bundle parent defines version 1.4.0 of the dependency "org.osgi:org.osgi.service.component.annotations" (https://github.com/apache/sling-parent/blob/e9b6c950b577172cd613fbcbe06a9120bcd789c2/sling-bundle-parent/pom.xml#L287). Once you use that you get a requirement like following

Re: Travis builds for sling?

ky you can try and apply the changes yourself, something > like: > > - generate patch file > - apply patch file to all repos > - commit all repos > - push all repos > > should work. For running commands on top of all repositories you can > use > > $ repo forall -c

Re: Updating javax.json APIs version

Also according to https://johnzon.apache.org/#Get_started you should reference the geronimo-json_1.1_spec for the API dependency (don't know though for which reason). But I would follow the advice from Apache Johnzon... Konrad > On 3. Jul 2019, at 13:38

Adding Resource Filter to Sling Starter

Hi, in the context of https://issues.apache.org/jira/browse/SLING-8271 I became aware of https://github.com/apache/sling-org-apache-sling-resource-filter . I really like those hel

Re: nodejs based sling packager

Hi Ruben, very nice, but wouldn't it make more sense to contribute that to Apache Jackrabbit (next to the https://github.com/apache/jackrabbit-filevault-package-maven-plugin ) rather than to Sling? AFAICS there is no dependenc

Re: [VOTE] Release Apache Sling Content Parser API 2.0.0, Apache Sling Content Parser JSON 2.0.0, Apache Sling Content Parser XML 2.0.0, Apache Sling Content Parser XML JCR 2.0.0, Apache Sling Content

IMHO it is the other way around: If only few/one bundle are supposed to implement the interface rather annotate with ProviderType (compare with https://osgi.org/javadoc/osgi.annotation/7.0.0/org/osgi/annotation/versioning/ProviderType.html

Re: Sling Authenticator issue on Sling 11

Hi Andy, the sling.auth.requirements don’t mingle with the access rights. This configuration only influences whether the user should be redirected to the login page (in case he is not yet logged in) or not. Hope this helps Konrad > Am 31.07.2019 um 17:47 schrieb Andreas Schaefer : > > Hi > We

Re: [Features] Merging Configurations

Hi, I would actually refuse to merge if the same PID occurs. It might be unexpected (and incompatible) if you do transparent merging on the property level. It is just important that it is easy to resolve those conflict without touching the feature, i.e. some force option which enforces merging (w

Re: [VOTE] Release Apache Sling Health Check Core 2.0.0, Sling Health Check Web Console 2.0.0

Hi Georg, wouldn't it make sense to add a relocation section to this last release (https://maven.apache.org/guides/mini/guide-relocation.html )? That way it would be even more obvious on how to migrate... Konrad > On 22. Aug 2019, at 1

Re: [VOTE] Release Apache Sling Health Check Core 2.0.0, Sling Health Check Web Console 2.0.0

ment - which > is not the case with sling HC -> felix HC? > > stefan > >> -----Original Message- >> From: Konrad Windszus [mailto:konra...@gmx.de] >> Sent: Monday, August 26, 2019 9:51 AM >> To: dev@sling.apache.org >> Subject: Re: [VOTE] Release Ap

Re: [VOTE] Accept the donation of the Sling Packager tool, SLING-8584

I fully agree with that statement. Actually there is already a task at FileVault to have an installation endpoint (accompanied by a branch): https://issues.apache.org/jira/browse/JCRVLT-151 For all those reasons I would also rather like to see t

Re: [VOTE] Accept the donation of the Sling Packager tool, SLING-8584

For me the situation looks a bit slightly different: I raised a concern in https://lists.apache.org/thread.html/7699b02a090d0397d661721f47a6d70b72fb83ff372fafb7d45e6f5e@%3Cdev.sling.apache.org%3E

Re: [VOTE] Release Apache Sling Health Check Core 2.0.0, Sling Health Check Web Console 2.0.0

che-sling-hc-core/blob/b0cfe3c8f7fdc1790f8c16bc075967f12ce33686/src/main/java/org/apache/sling/hc/core/impl/NoopHcCore.java#L33 > > [4] > https://sling.apache.org/documentation/bundles/sling-health-check-tool.html > > On 2019-08-26 10:04, Konrad Windszus wrote: >> Yes

Re: htl-maven-plugin - default value for sourceDirectory

Hi, The logic in the filevault-package-maven-plugin is as follows: It looks for the first found directory below any of the following: ${project.basedir}/jcr_root,${project.basedir}/src/main/jcr_root,${project.basedir}/src/main/content/jcr_root,${project.basedir}/src/content/jcr_root,${project.buil

Re: [VOTE] Release Apache Sling Tooling Support Install 1.0.6

+1 (checked signatures and build) Konrad > On 9. Sep 2019, at 11:04, Robert Munteanu wrote: > > On Thu, 2019-09-05 at 10:50 +, Robert Munteanu wrote: >> This majority vote is open for at least 72 hours. > > We are missing two binding votes, can anyone else please check+vote? > > Thanks, > Rob

Re: Why get rid of the rewriter?

The new url rewriter SPI will be perfectly supporting AOP. Konrad > Am 10.09.2019 um 16:09 schrieb Justin Edelson : > > I see that the same assumptions are being made here that were made a year > ago when this was discussed. I would strongly caution against assuming that > the "aspect developer"

Re: Why get rid of the rewriter?

rkup directly? That should (for HTL) allow > getting rid of the processing overhead. Just a thought on how to solve > the underlying issue while keeping the rewriter (maybe by allowing it > to be hooked in differently). > > Regards > Julian > > > > > > >

Re: [hackathon] maven archetypes

Definitely +1 on having only one archetype. In case D is too much effort, we could even leave it out. A maintained archetype is better than what we currently have. And it should be pretty easy for every developer to just copy over from a blueprint project created from the archetype only the desi

Re: [hackathon] CI experience

> On 5. Sep 2019, at 16:28, Stefan Seifert wrote: > > - Challenge: Building non-committer PRs with Jenkins is no longer allowed > - problem described in SLING-7245 - Validate pull requests using Jenkins > Resolved >- reason are security issues, see also INFRA-18973 >- we assume it wi

Missing horizontal scroll bars on Sling Website

I just noticed that the horizontal scroll bars are missing (at least in Chrome 77 on Mac OS X) e.g. in https://sling.apache.org/documentation/bundles/scripting/scripting-htl.html#javascript-use-provider

Re: Missing horizontal scroll bars on Sling Website

te: >>> Didn't notice that before, and whether it's the css I added or not. >>> I'll go ahead and see what I can do to fix it since I was the last one >>> playing with it. >>> >>> -- >>> Jason >>> >>> On Mon, Sep

Re: Missing horizontal scroll bars on Sling Website

> On Mon, Sep 16, 2019, at 12:56 PM, Konrad Windszus wrote: >> For me the same issue happens with Firefox 69.0 on Mac OS. >> It only appears for width above 768px (so Mobile is not affected). >> Konrad >> >>> On 16. Sep 2019, at 18:53, Eric Norman wrote: >

Re: bnd baselining and development versions

That would officially violate https://www.osgi.org/developer/white-papers/semantic-versioning/bundles-and-fragments/ and the warning come from bnd itself. https://github.com/bndtools/bnd/blob/abdf289ce7599d

Re: bnd baselining and development versions

org/apache/sling/installer/core/impl/tasks/BundleTaskCreator.java#L235> Konrad > On 20. Sep 2019, at 12:32, Radu Cotescu wrote: > > Hi Konrad, > >> On 20 Sep 2019, at 11:34, Konrad Windszus wrote: >> >> a) adjust the bundle version accordingly (and rather get

Re: bnd baselining and development versions

version baselining. Konrad > On 20. Sep 2019, at 15:53, Radu Cotescu wrote: > > >> On 20 Sep 2019, at 12:36, Konrad Windszus wrote: >> >> I am not aware of any more places (e.g. OSGi Installer or Felix Web Console) >> where changes from SNAPSHOT to non SNAPSHOT v

Re: bnd baselining and development versions

Well, after having a second thought I don't think that -SNAPSHOT ever appears in the bundle version. The bnd-maven-plugin will instead always rely on a timestamp as qualifier. As long as we keep the same timestamp as qualifier also during the release we have a nice order of bundle versions (irre

Re: bnd baselining and development versions

Not at all, but AFAIK OSGi version qualifiers don't have special support for SNAPSHOTS. Therefore -SNAPSHOT should never appear in bundle versions. Compare with https://osgi.org/javadoc/r4v43/core/org/osgi/framework/Version.html#compareTo(org.osgi.framework.Version)

Re: bnd baselining and development versions

shot or a > released one if we append timestamps as qualifiers to all versions? > >> On 20 Sep 2019, at 16:08, Konrad Windszus wrote: >> >> As long as we keep the same timestamp as qualifier also during the release >> we have a nice order of bundle versions (irrespective of SNAPSHOT or >> release). >

Re: bnd baselining and development versions

Well I think the baselining issue only appears with the latest bnd-maven-plugin and not the maven-bundle-plugin. So the bundles we have migrated to the latest parent do no longer need to follow odd/even release versions, right? Konrad > On 20. Sep 2019, at 17:09, Radu Cotescu wrote: > > Right

Re: bnd baselining and development versions

A workaround has been suggested by the bnd people and I have opened https://issues.apache.org/jira/browse/SLING-8735 to track implementation of this workaround in the next bundle parent. Konrad > On 23. Sep 2019, at 11:41, Robert Munteanu wro

Re: Changing the resource to render and the handling servlet in a request

Nice, can you add this to https://sling.apache.org/documentation/bundles/rendering-content-default-get-servlets.html? Thanks, Konrad > On 15. Oct 2019, at 11:19, Robert Munteanu wrote: > > Hi Julian,

Re: Dynamic Class Loader Manager causes lots of service restarts

Hi Julian, thanks a lot for bringing up this topic. Indeed the restart cascade causes some issues for me as well. Just invalidating the cache of the DCLM without restarting it fully sounds reasonable to me, but I am not that familiar with class loader insights. I vaguely remember that the restar

Re: Dynamic Class Loader Manager causes lots of service restarts

of the pain would already be resolved in case something like https://issues.apache.org/jira/browse/JCRVLT-151 <https://issues.apache.org/jira/browse/JCRVLT-151> would be implemented in a way which doesn't rely on scripts (but rather on precompiled servlets). Konrad > On 22. Oct 20

Re: [VOTE] Release Apache Sling Thread Support 3.2.14

+1 Konrad > On 25. Jan 2018, at 14:42, Robert Munteanu wrote: > > > Hi, > > We solved 3 issues in this release: > https://issues.apache.org/jira/browse/SLING/fixforversion/12342655 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-1861 > > You can u

Re: New i18n release and basename handling (was: [VOTE] Release Apache Sling Starter 10 + associated testing projects and archetypes (take 2))

he.org/jira/browse/SLING-7429 <https://issues.apache.org/jira/browse/SLING-7429>. > On 23. Jan 2018, at 13:28, Robert Munteanu wrote: > > Hi Konrad, > > On Tue, 2018-01-23 at 13:13 +0100, Konrad Windszus wrote: >> But before spinning a new release I would like to get some

Re: [VOTE] Release Apache Sling I18N Support 2.5.12

> On 25. Jan 2018, at 15:16, Robert Munteanu wrote: > > Please vote to approve this release: +1 Konrad

Re: [VOTE] Release Apache Sling I18N Support 2.5.12

That is the general issue which is used for tracking the upgrade to parent 33 for multiple modules. For i18n this is finished but other modules will follow... > On 25. Jan 2018, at 15:27, Jason E Bailey wrote: > > One of the issues shows in progress? > > > - Jason > > On Thu, Jan 25, 2018, a

Re: apache/sling as github landing repository

Thanks, maybe we can use the branch from https://github.com/apache/sling-site/tree/scm-project-url-list (mentioned in https://issues.apache.org/jira/browse/SLING-7161 ) as a basis

Re: [VOTE] Release Apache Sling Thread Support 3.2.16

+1 Konrad > On 29. Jan 2018, at 10:03, Robert Munteanu wrote: > > Hi, > > We solved 5 issues in this release: > https://issues.apache.org/jira/projects/SLING/versions/12342668 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-1863 > > You can use this

Re: [DISCUSSION] Rename Launchpad Starter

+1 Konrad Von meinem iPhone gesendet > Am 09.02.2018 um 05:43 schrieb Daniel Klco : > > All, > > In https://issues.apache.org/jira/browse/SLING-7484 we're going to be > moving the existing Launchpad Content into a sub-directory of /content to > enable restricting access to / by default. As part

Re: wiki access

Yes, I can confirm that in the past the individual users have been given access (not based on group memberships). If this is no longer accurate we need to fix https://sling.apache.org/documentation.html#the-public-wiki as well. Konrad

Minimum JCR access rights for a path-based Sling servlet

Although it is currently stated at https://sling.apache.org/documentation/the-sling-engine/servlets.html#caveats-when-binding-servlets-by-path that no JCR repository acls are evaluated

Re: Minimum JCR access rights for a path-based Sling servlet

Sorry for the noise, actually no right is necessary as correctly stated in the wiki. I had an issue with the user provisioning process. Konrad > On 19. Feb 2018, at 18:01, Konrad Windszus wrote: > > Although it is currently stated at > https://sling.apache.org/documentation/the-

Re: [Maven] Updating to parent pom 33 breaks all projects

Actually Oli switched to individual spec chapter artifacts and there was also some discussion triggered by me in the comments (e.g. https://issues.apache.org/jira/browse/SLING-7384?focusedCommentId=16327408&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16327408).

Re: [Maven] Updating to parent pom 33 breaks all projects

@Carsten: Which dependency exactly to you want to declare now? The aggregate one for annotations or the individual ones per annotation definition? But I rather tend to agree with Oli here. We should really force every project to declare all(!) its dependencies. Having a dirty classpath for non-O

Re: [Maven] Updating to parent pom 33 breaks all projects

This is true for every other managed dependency in parent as well. We do maintain a certain baseline with parent and I think this is good. Projects deliberately supporting older versions of the baseline cannot upgrade to the most recent parent then! > On 26. Feb 2018, at 14:01, Carsten Ziegeler

Re: [Maven] Updating to parent pom 33 breaks all projects

> > Maybe we can have a compromise and require a property in the pom, e.g. > > >true > > > That property will activate the OSGi-related profile from the parent > pom. > > Not ideal but still better than copy/pasting considerably more > dependency versions. > This is not supported b

Re: [CANCELLED][VOTE] Release Apache Sling Scripting HTL Engine 1.0.50-1.3.1

Would you consider including https://issues.apache.org/jira/browse/SLING-7516 in the upcoming release? The attached PR is IMHO pretty straight-forward. Thanks, Konrad > On 7. Mar 2018, at 17:15, Radu Cotescu wrote: > > Sorry for the blunder -

Re: Google Summer of Code 2018 Mentor Registration

Very much +1 on SLING-7231. > On 8. Mar 2018, at 14:03, Radu Cotescu wrote: > > Hi, > > Is this something we could try this year? I've recently stumbled (again) > upon an issue that could be an interesting summer project: > https://issues.apache.org/jira/browse/SLING-7231 > The issue in questio

Re: [VOTE] Release Apache Sling Testing Clients version 1.2.0 and Apache Sling Testing Rules 1.0.8

+1 Konrad > On 2. Apr 2018, at 12:30, Andrei Dulvac wrote: > > Bump. > > On Fri, Mar 30, 2018, 09:41 Andrei Dulvac wrote: > >> Hi Robert. >> >> There were no issues specifically fixed in the rules, just a commit to >> update to this version of the clients. >> >> >> On Thu, Mar 29, 2018, 14

Bundle version for SNAPSHOTs generated by bnd-maven-plugin

I am just migrating the OSGi Installer HC (https://github.com/apache/sling-org-apache-sling-installer-hc/) to the bnd-maven-plugin and I observed one difference to the maven-bundle-plugin: The bundle version for SNAPSHOTs by default looks like "1.0.1." instead of "1.0.1.SNAPSHOT" (as it was wit

[VOTE] Release Apache Sling Installer Health Checks version 2.0.0

Hi, We solved 2 issues in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12339841 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1893/ You can use this UNIX script to download the release and verify the signatures: https://gitbox.ap

Re: Bundle version for SNAPSHOTs generated by bnd-maven-plugin

a timestamp, it isn't needed since the bundle > versions would be constantly increasing. > > Now there could be a problem if the timestamp somehow not taking timezones > into account, but assuming it is UNIX epoch based, then this won't be an > issue. > > Regard

Re: Bundle version for SNAPSHOTs generated by bnd-maven-plugin

gt; > On Mon, Apr 9, 2018 at 10:28 AM Konrad Windszus wrote: > >> By default the timestamp is having the format "MMddHHmm" ( >> http://bnd.bndtools.org/macros/tstamp.html < >> http://bnd.bndtools.org/macros/tstamp.html>), this could be a problem in

Re: [PROPOSAL] replace sling committer list with link to apache phonebook

+1 maybe we can use the homepage url in LDAP to maintain the organization (compare with https://people.apache.org/phonebook-about.html ). Unfortunately that is not yet exposed in the Apache Phonebook. > On 10. Apr 2018, at 15:01, Stefan Seifert

[RESULT] [VOTE] Release Apache Sling Installer Health Checks version 2.0.0

Hi, The vote has passed with the following result : +1 (binding): Radu, Dan, Oli I will copy this release to the Sling dist directory and promote the artifacts to the central Maven repository. Thanks for voting, Konrad

Re: [LAZY] Removing .md5 digest files in our releases folder

In general I agree with that. We should just defer the actual deletion until we figured out how to prevent MD5 generation for new releases in the first place. Konrad > Am 12.04.2018 um 17:34 schrieb Bertrand Delacretaz : > > Hi, > > Now that http://sling.apache.org/downloads.cgi points to sha1

Re: [VOTE] Release Apache Sling Commons Log 5.1.16

You must be logged in for that. I already reported that in https://issues.apache.org/jira/browse/INFRA-15862 but it seems this is a JIRA issue Atlassian doesn't want to fix to sell more licenses :-( > On 24. Apr 2018, at 17:08, David Bosschaert

Teleporter: deploy a test bundle, then use it from the client(!) side, afterwards undeploy it

Hi, since in general I very much like to keep related things together in most of the cases want to execute the IT in the same Maven module where the actual implementation is. Therefore, teleporter rules are very handy, because they transparently create bundles only for the IT purpose and execut

Re: [Dev][GSoC2018][OpenIDConnect] Using Apache Oltu OpenID Connect as a maven dependency

Maybe it is worth to consider using https://bitbucket.org/connect2id/oauth-2.0-sdk-with-openid-connect-extensions/overview . It is having an Apache 2.0 license and seems to be quite actively maintained. All r

XSS API: Don't modify certain unicode escape characters in the input string, e.g. for emojis

If I understand the XSS API correctly, the only supported methods for HTML contexts are encodeForHtml (https://github.com/apache/sling-org-apache-sling-xss/blob/257e7096dad689a46d474d1f251d504ca5508db7/src/main/java/org/apache/sling/xss/impl/XSSAPIImpl.java#L419) and encodeForHtmlAttr (https://

Re: XSS API: Don't modify certain unicode escape characters in the input string, e.g. for emojis

Thanks for your input. I created https://issues.apache.org/jira/browse/SLING-7658 <https://issues.apache.org/jira/browse/SLING-7658>. Konrad > On 8. May 2018, at 17:45, Carsten Ziegeler wrote: > > Sounds like a bug to me > > Carsten > > > Konrad Windszus wrote

Re: [VOTE] Release Apache Slingstart Maven Plugin version 1.8.0

-1 from my side. I think I found a regression. Compare with https://issues.apache.org/jira/browse/SLING-7662?focusedCommentId=16471979&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16471979

Re: JSR 305 annotations (nullability)

There are some ideas in https://issues.apache.org/jira/browse/SLING-7312 but not yet a solution, as even the proposed alternative spotbugs-annotations is not yet JSR-305 free (which might be problematic from a licensing point of view). But IMHO

Re: JSR 305 annotations (nullability)

s even been started). Now they are actively maintained by the spotbugs community. I currently fail to see a better alternative, but I am open to other suggestions. Konrad > On 15. May 2018, at 17:12, Julian Reschke wrote: > > On 2018-05-15 16:39, Konrad Windszus wrote: >> There ar

Depending on SNAPSHOT parent pom

Hi, does anyone have any idea, why the Jenkins cannot resolve the latest parent SNAPSHOT (https://builds.apache.org/view/S-Z/view/Sling/job/sling-org-apache-sling-servlets-annotations-it-1.8/3/

Re: Depending on SNAPSHOT parent pom

Found it, it was tracked in https://issues.apache.org/jira/browse/INFRA-15815 <https://issues.apache.org/jira/browse/INFRA-15815>. > On 29. May 2018, at 19:24, Konrad Windszus wrote: > > Hi, does anyone have any idea, why the Jenkins cannot resolve the latest > parent

Re: Depending on SNAPSHOT parent pom

at 19:30, Konrad Windszus wrote: > > Found it, it was tracked in https://issues.apache.org/jira/browse/INFRA-15815 > <https://issues.apache.org/jira/browse/INFRA-15815>. > >> On 29. May 2018, at 19:24, Konrad Windszus wrote: >> >> Hi, does anyone have any id

Plan to release servlet annotations (https://issues.apache.org/jira/browse/SLING-7624)

Since the discussion around the servlet annotations in https://issues.apache.org/jira/browse/SLING-7624 settled a bit I would like to do a first release soon. Please raise your voice now if you have any concerns with the annotations how they ar

Re: Committer access to sling-dist (Was: Re: [RESULT][VOTE] Release Apache Sling Feature, Feature-IO, Feature-Analyser and Feature-ModelConverter 0.1.2)

+1 on letting committers copy to dist as well. We have release votes so any PMC member can express concerns previously! Also since most of the artifacts are anyhow consumed via Maven Central it would not be a very wise decision to not publish a released artifact to dist (for whatever reason!) >

Re: Using declarative services in sling-commons-mime?

I am in favor of applying your PR. It simplifies the code and I fail to see any regressions/drawbacks. Konrad > Am 11.06.2018 um 18:13 schrieb Christian Schneider : > > Some time ago I proposed a change in sling-commons-mime to use declarative > services instead of BundleActivator for registerin

[VOTE] Release Apache Sling Servlet Annotations 1.0.0

Hi, We solved 1 issue in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12343444 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1915/ You can use this UNIX script to download the release and verify the signatures: https://gitbox.apa

Re: [VOTE] Release Apache Sling Thread Support 3.2.18

+1 Konrad > On 13. Jun 2018, at 17:04, Robert Munteanu wrote: > > Hi, > > We solved 2 issues in this release: > https://issues.apache.org/jira/issues/?jql=project%20%3D%20SLING%20AND%20fixVersion%20%3D%20%22Commons%20Threads%203.2.18%22 > > Staging repository: > https://repository.apache.org/

Sling IDE Tooling: Debugging does no longer work with the provided launcher configuration

I tried to work on some Sling IDE Tooling issues and for that need to start Eclipse with the tooling included in debug mode. There is even a laucher for that included in https://github.com/apache/sling-ide-tooling/blob/42a964b8961c4951f68053b9ac455abadd8595d6/eclipse/target-definition/Sling%20ID

Re: Sling IDE Tooling: Debugging does no longer work with the provided launcher configuration

m to IntelliJ as they are only considered in Eclipse and should make setting up the project much easier for all developers in Eclipse. > On 15. Jun 2018, at 14:40, Konrad Windszus wrote: > > I tried to work on some Sling IDE Tooling issues and for that need to start > Eclipse with the too

[RESULT] [VOTE] Release Apache Sling Servlet Annotations 1.0.0

Hi, The vote has passed with the following result : +1 (binding): Dan, Radu, Robert I will copy this release to the Sling dist directory and promote the artifacts to the central Maven repository. Thanks for voting, Konrad

JBake Build has error java.lang.ArrayIndexOutOfBoundsException: 3 for downloads.html

When building locally the Sling Site I get the following error: ... [ERROR] Rendering [/Users/konradwindszus/git/sling-site/target/sling-site-0.1-SNAPSHOT/downloads.html]... failed! org.jbake.template.RenderingException: java.lang.ArrayIndexOutOfBoundsException: 3 at org.jbake.template.Groo

Configuration File Format for OSGi Installer: https://issues.apache.org/jira/browse/SLING-7757

Currently the OSGi Installer is relying on the ConfigurationHandler from the ConfigAdmin to parse *.config files (https://github.com/apache/sling-org-apache-sling-installer-core/blob/0a34e33dd26092437be5180e34979abbf9a88300/src/main/java/org/apache/sling/installer/core/impl/InternalResource.java#

Re: Configuration File Format for OSGi Installer: https://issues.apache.org/jira/browse/SLING-7757

> On 2. Jul 2018, at 11:40, Bertrand Delacretaz wrote: > > Hi, > > On Thu, Jun 28, 2018 at 4:57 PM Konrad Windszus wrote: >> ...Does anything speak against switching from the CA one to the Felix Utils >> one (https://issues.apache.org/jira/browse/SLING-7757)? >>

Re: [Proposal] Default compiler should be changed to JRE8 in parent pom

I would recommend to not provide a default compiler class version at all but rather force each inheriting module to set that explicitly via a property. There is even a Maven enforcer rule which makes Maven builds fail in case that property is not set. That way each module must define the compa

Re: Where is OSGi Configuration read Sling JCR?

This is more a question for the Sling Users mailing list, but http://sling.apache.org/documentation/bundles/osgi-installer.html should contain some information about that. > On 9. Jul 2018, at 16:32, Andreas Schaefer wrote: >

Re: Sling Hackathon Sept. 13th, 2018 in Berlin

I would like to join as well. Konrad > On 18. May 2018, at 15:07, Stefan Seifert wrote: > > same as last year, we have the possibility to host a "Sling Hackathon" in > berlin in september. > > the date is thursday 13.09.18 which is directly after the adaptTo() which > takes place 10-12.9.18 i

Re: [PROPOSAL] Donating a tool able to generate markdown documentation from annotations

Hi Simone, this looks great. Just some comments: > > How it works: it is a plain Java8 annotations processor, able to generate > documentations for: > > * SlingServlet annotated components; > * (Deprecated) Felix SCR annotations (we still have lot of components in > the repo which use such annota

Re: [VOTE] Switch from JSR-305 annotations to Jetbrains Annotations for all Sling Models

+1 > On 2. Aug 2018, at 10:55, Stefan Seifert wrote: > > as recently discussed in SLING-7312 and the mailing list the JSR-305 > annotations for null-analysis (javax.annotations) we are currently using > break our compatibility with Java 9. the problem is that JSR-305 was never > accepted and

Re: [VOTE] Switch from JSR-305 annotations to Jetbrains Annotations for all Sling Models

> However, I wanted to point out option b). IIRC, there is nothing > preventing us to just provide the package ourselves and then it would be > problem solved, no? Unfortunately not, due to potential split-packages: https://blog.codefx.org/java/jsr-305-java-9/

Re: [VOTE] Switch from JSR-305 annotations to Jetbrains Annotations for all Sling Models

nnotation and be done with it think. > > regards, > > Karl > > On Thursday, August 2, 2018, Konrad Windszus wrote: > >> >>> However, I wanted to point out option b). IIRC, there is nothing >>> preventing us to just provide the package ourselves and then

Re: [VOTE] Switch from JSR-305 annotations to Jetbrains Annotations for all Sling Models

arlpa...@gmail.com>> wrote: > >> >> >> On Thursday, August 2, 2018, Konrad Windszus wrote: >> >>> At Sling we use other classes from javax.annotation as well (compare with >>> https://issues.apache.org/jira/browse/SLING-7135 < >>> ht

<    3   4   5   6   7   8   9   10   11   12   >