Re: Programmatically create a logger

[Chetan Mehrotra]

On Fri, May 19, 2017 at 9:38 PM, Nicolas Peltier
 wrote:
> org.osgi.service.cm.Configuration.update(dict) from sling pipes bundle does 
> not trigger LoggerManagedServiceFactory.updated

How are you creating the config instance from ConfigurationAdmin
instance? You should use the listConfiguration approach [1] otherwise
the config instance would get "bound" to the calling bundle [2] which
would prevent that config from getting used by the Commons Log bundle


Chetan Mehrotra
[1] 
https://github.com/apache/sling/blob/trunk/installer/factories/configuration/src/main/java/org/apache/sling/installer/factories/configuration/impl/ConfigUtil.java#L191
[2] 
https://osgi.org/javadoc/r4v42/org/osgi/service/cm/ConfigurationAdmin.html#getConfiguration(java.lang.String)

[jira] [Resolved] (SLING-6869) fsresource: Avoid NPE when content fragment file contains invalid JSON

[Stefan Seifert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Seifert resolved SLING-6869.
---
Resolution: Fixed

Completed: At revision: 1795848   (1.x)
Completed: At revision: 1795847  (2.x)


> fsresource: Avoid NPE when content fragment file contains invalid JSON
> --
>
> Key: SLING-6869
> URL: https://issues.apache.org/jira/browse/SLING-6869
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: File System Resource Provider 1.4.0, File System 
> Resource Provider 2.1.0
>Reporter: Stefan Seifert
>Assignee: Stefan Seifert
>Priority: Minor
> Fix For: File System Resource Provider 1.4.2, File System 
> Resource Provider 2.1.2
>
>
> a NPE in 
> {{org.apache.sling.fsprovider.internal.mapper.ContentFile#getContent()}} my 
> be thrown when the underlying JSON content fragment file contains invalid 
> JSON that leads to a parsing error.
> this should be handled gently (an warning to the log is already written).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (SLING-6869) fsresource: Avoid NPE when content fragment file contains invalid JSON

[Stefan Seifert (JIRA)]

Stefan Seifert created SLING-6869:
-

 Summary: fsresource: Avoid NPE when content fragment file contains 
invalid JSON
 Key: SLING-6869
 URL: https://issues.apache.org/jira/browse/SLING-6869
 Project: Sling
  Issue Type: Bug
  Components: Extensions
Affects Versions: File System Resource Provider 2.1.0, File System Resource 
Provider 1.4.0
Reporter: Stefan Seifert
Assignee: Stefan Seifert
Priority: Minor
 Fix For: File System Resource Provider 1.4.2, File System Resource 
Provider 2.1.2


a NPE in 
{{org.apache.sling.fsprovider.internal.mapper.ContentFile#getContent()}} my be 
thrown when the underlying JSON content fragment file contains invalid JSON 
that leads to a parsing error.
this should be handled gently (an warning to the log is already written).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Build failed in Jenkins: sling-launchpad-builder-1.8 #10567

[Robert Munteanu]

On Mon, 2017-05-22 at 17:16 +, Apache Jenkins Server wrote:
> Could not find artifact
> org.apache.sling:org.apache.sling.launchpad.content:jar:2.0.13-
> SNAPSHOT in Nexus (http://repository.apache.org/snapshots) -> [Help
> 1]

I've re-trigerred a build of the launchpad/content module, the build
should be fixed soon (TM).

Robert

Re: [VOTE] Release Apache Sling Launchpad Content 2.0.12

[Chris Millar]

If you would like to see a demo of the content changes without
building the bundle, I've put together a static demo here:
https://auniverseaway.github.io/sling-9-launchpad-demo

Note: Some links will attempt to hit http://localhost:8080

On Mon, May 22, 2017 at 10:14 AM, Stefan Egli  wrote:
> +1
>
> Cheers,
> Stefan
>
> On 22/05/17 17:23, "Robert Munteanu"  wrote:
>
>>Hi,
>>
>>Note that I skipped the 2.0.10 version number due to starting the
>>release process before committing all the required changes.
>>
>>We solved 3 issues in this release:
>>https://issues.apache.org/jira/browse/SLING/fixforversion/12328242
>>
>>Staging repository:
>>https://repository.apache.org/content/repositories/orgapachesling-1726
>>
>>You can use this UNIX script to download the release and verify the
>>signatures:
>>http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh
>>
>>Usage:
>>sh check_staged_release.sh 1726 /tmp/sling-staging
>>
>>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.
>
>

Re: [VOTE] Release Apache Sling Launchpad Content 2.0.12

[Stefan Egli]

+1

Cheers,
Stefan

On 22/05/17 17:23, "Robert Munteanu"  wrote:

>Hi,
>
>Note that I skipped the 2.0.10 version number due to starting the
>release process before committing all the required changes.
>
>We solved 3 issues in this release:
>https://issues.apache.org/jira/browse/SLING/fixforversion/12328242
>
>Staging repository:
>https://repository.apache.org/content/repositories/orgapachesling-1726
>
>You can use this UNIX script to download the release and verify the
>signatures:
>http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh
>
>Usage:
>sh check_staged_release.sh 1726 /tmp/sling-staging
>
>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.

RE: [VOTE] Release Apache Sling Launchpad Content 2.0.12

[Stefan Seifert]

+1

Re: [VOTE] Release Apache Sling Launchpad Content 2.0.12

[Robert Munteanu]

On Mon, 2017-05-22 at 18:23 +0300, Robert Munteanu wrote:
> Please vote to approve this release:

+1

Robert

signature.asc
Description: This is a digitally signed message part

[VOTE] Release Apache Sling Launchpad Content 2.0.12

[Robert Munteanu]

Hi,

Note that I skipped the 2.0.10 version number due to starting the
release process before committing all the required changes.

We solved 3 issues in this release:
https://issues.apache.org/jira/browse/SLING/fixforversion/12328242

Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-1726

You can use this UNIX script to download the release and verify the
signatures:
http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh

Usage:
sh check_staged_release.sh 1726 /tmp/sling-staging

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.

[jira] [Resolved] (SLING-6850) Address Launchpad homepage information architecture

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu resolved SLING-6850.

Resolution: Fixed
  Assignee: Robert Munteanu

Patch applied in [r1795820|https://svn.apache.org/r1795820], thanks 
[~auniverseaway] for the contribution!

> Address Launchpad homepage information architecture
> ---
>
> Key: SLING-6850
> URL: https://issues.apache.org/jira/browse/SLING-6850
> Project: Sling
>  Issue Type: Improvement
>Reporter: Chris Millar
>Assignee: Robert Munteanu
>Priority: Minor
> Fix For: Launchpad Content 2.0.10
>
> Attachments: Launchpad - Current Design.png, Launchpad - Proposed 
> Design.png
>
>
> The launchpad homepage could use some love...
> # The page is not responsive.
> # Design is dated.
> # The page has several links that are either out of date (composum always 
> installed now), repeated (OSGi console), or not helpful (sign up).
> # Does not speak to audiences of different skill levels.
> *My proposal addresses these concerns with the following updates:*
> # Page is responsive
> # Page is designed to address three audiences:
> ## Brand new developer - Why did I just type `java -jar org.apache.sling`?
> ## Experienced developer - Give me a list of the guts in this site / app. 
> Give me external resources to help keep me going.
> ## Potential Contributor - How do I get involved?
> # Bad / duplicated / unused links have been removed. - I'm looking at you 
> signup page and client test page (which 500s in snapshot).
> # Apache logo has been added.
> # Retained most of the excellent welcome text (with updated links to Oak and 
> Felix).
> # Friendlier colors have been used.
> # Custom font (Open Sans, AL 2.0) has been used instead of Tahoma (not AL 2.0)
> # Slightly larger typography to meet current trends.
> # Used old yellow / blue horizontal rule as the design inspiration for the 
> left rail rule (that uses feather color palette).
> # Built out concise list of top resources for both the current site as well 
> as external resources.
> *Items worth discussing:*
> # Should the first heading under "Resources" be "This Site" or "This 
> Application"?
> # Should the HTL REPL be included in the list of links.
> # Should the Bootstrap clientlibs (used in HTL REPL) be used to build the 
> page even though they are MIT? If not, should we refactor the clientlibs 
> folder so REPL can be self contained and other libraries can also use 
> /etc/clientlibs?
> ## I have a flexbox based grid system I'd be willing to donate / use / 
> document.
> # Other things I'm not thinking of that may be contentious...



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Sling post servlet import

[Ruben Reusser]

Hi there,

A couple of days ago I posted on the users list about the sling post servlet 
and import command. There seem to be some odd issues

1) order at reimport is not preserved
2) replace import merges sub nodes instead of replacing them

https://lists.apache.org/thread.html/58295987e9b13fd93424c183674316c0eb986b30d85cfb63e9bd1004@%3Cusers.sling.apache.org%3E

Not sure if thats just me not understanding the intent of the import command or 
if there is really something wrong there.

Ruben

[jira] [Commented] (SLING-6850) Address Launchpad homepage information architecture

[Chris Millar (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-6850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16019623#comment-16019623
 ] 

Chris Millar commented on SLING-6850:
-

[~rombert]

README has been updated. Let me know if you have any questions or suggestions.

Thanks!

> Address Launchpad homepage information architecture
> ---
>
> Key: SLING-6850
> URL: https://issues.apache.org/jira/browse/SLING-6850
> Project: Sling
>  Issue Type: Improvement
>Reporter: Chris Millar
>Priority: Minor
> Fix For: Launchpad Content 2.0.10
>
> Attachments: Launchpad - Current Design.png, Launchpad - Proposed 
> Design.png
>
>
> The launchpad homepage could use some love...
> # The page is not responsive.
> # Design is dated.
> # The page has several links that are either out of date (composum always 
> installed now), repeated (OSGi console), or not helpful (sign up).
> # Does not speak to audiences of different skill levels.
> *My proposal addresses these concerns with the following updates:*
> # Page is responsive
> # Page is designed to address three audiences:
> ## Brand new developer - Why did I just type `java -jar org.apache.sling`?
> ## Experienced developer - Give me a list of the guts in this site / app. 
> Give me external resources to help keep me going.
> ## Potential Contributor - How do I get involved?
> # Bad / duplicated / unused links have been removed. - I'm looking at you 
> signup page and client test page (which 500s in snapshot).
> # Apache logo has been added.
> # Retained most of the excellent welcome text (with updated links to Oak and 
> Felix).
> # Friendlier colors have been used.
> # Custom font (Open Sans, AL 2.0) has been used instead of Tahoma (not AL 2.0)
> # Slightly larger typography to meet current trends.
> # Used old yellow / blue horizontal rule as the design inspiration for the 
> left rail rule (that uses feather color palette).
> # Built out concise list of top resources for both the current site as well 
> as external resources.
> *Items worth discussing:*
> # Should the first heading under "Resources" be "This Site" or "This 
> Application"?
> # Should the HTL REPL be included in the list of links.
> # Should the Bootstrap clientlibs (used in HTL REPL) be used to build the 
> page even though they are MIT? If not, should we refactor the clientlibs 
> folder so REPL can be self contained and other libraries can also use 
> /etc/clientlibs?
> ## I have a flexbox based grid system I'd be willing to donate / use / 
> document.
> # Other things I'm not thinking of that may be contentious...



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: sling 9 very large - reducing the size?

[Ioan Eugen Stan]

Hi Robert,


Thank you for the clarification and the link. All I have to do is figure
out if I need tika or not. It's still a huge bundle and maybe the tika
guys could do something to improve that, but it's another discussion.

It makes sens to be like this. I imagine some hints for using sling in
production would be welcomed and this should be there.

Have a great day,


On 22.05.2017 14:09, Robert Munteanu wrote:
> Hi Eugen,
>
> On Sat, 2017-05-20 at 21:24 +0300, Ioan Eugen Stan wrote:
>> Hello Sling ,
>>
>> I've noticed sling 9 is quite big. The latest snapshot jar is about
>> 107 MB.
>>
>> - ~40MB of this is occupied by install/10/tike-bundle-1.14.jar . Is
>> this
>> bundle always required?
> This (IIRC) is required for full-text search to function in Oak.
>
>
>> - removing install/0/org.apache.sling.samples.slingshot-0.8.0.jar can
>> shave another 5MB
> Yes, but it's explicitly in there because we want to include a demo of
> an application with the default download.
>
>
>> Reducing the sling-launchpad image size should make the platform
>> easier
>> to work with.
> For more context, we see the Sling Launchpad as a 'demo' platform which
> allows you to quickly get your feet wet and understand how Sling works.
>
> For production usage, I would expect most people would define their own
> launchpad, potentially from an existing Launchpad. There's also support
> for dynamically removing artifacts from an existing launchpad, see [1],
> but I'm not sure how many use it for that exact purpose.
>
> HTH,
>
> Robert
>
> [1]: http://sling.apache.org/documentation/development/slingstart.html#
> removing-and-changing-of-artifacts
>
>>
>> Regards,
>>
>>
>>
>>
>>
>>
>>




signature.asc
Description: OpenPGP digital signature

Re: sling 9 very large - reducing the size?

[Robert Munteanu]

Hi Eugen,

On Sat, 2017-05-20 at 21:24 +0300, Ioan Eugen Stan wrote:
> Hello Sling ,
> 
> I've noticed sling 9 is quite big. The latest snapshot jar is about
> 107 MB.
> 
> - ~40MB of this is occupied by install/10/tike-bundle-1.14.jar . Is
> this
> bundle always required?

This (IIRC) is required for full-text search to function in Oak.


> - removing install/0/org.apache.sling.samples.slingshot-0.8.0.jar can
> shave another 5MB

Yes, but it's explicitly in there because we want to include a demo of
an application with the default download.


> Reducing the sling-launchpad image size should make the platform
> easier
> to work with.

For more context, we see the Sling Launchpad as a 'demo' platform which
allows you to quickly get your feet wet and understand how Sling works.

For production usage, I would expect most people would define their own
launchpad, potentially from an existing Launchpad. There's also support
for dynamically removing artifacts from an existing launchpad, see [1],
but I'm not sure how many use it for that exact purpose.

HTH,

Robert

[1]: http://sling.apache.org/documentation/development/slingstart.html#
removing-and-changing-of-artifacts

> 
> 
> Regards,
> 
> 
> 
> 
> 
> 
> 

[RESULT][VOTE] Release Apache Sling Service User Mapper 1.3.2, Apache Sling JCR Base Bundle 3.0.2, Apache Sling Web Console Branding 1.0.2, Apache Sling Engine Implementation 2.6.8

[Robert Munteanu]

Hi,

The vote has passed with the following reuslt:

+1 (binding): Carsten Ziegeler, Stefan Seifert, Robert Munteanu


I will copy this release to the Sling dist directory and promote the
artifacts to the central Maven repository.

Thanks,

Robert

[jira] [Updated] (SLING-6866) HTL doesn't allow to overwrite the context for data-sly-text

[Radu Cotescu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu updated SLING-6866:

Reporter: Radu Cotescu  (was: Konrad Windszus)

> HTL doesn't allow to overwrite the context for data-sly-text
> 
>
> Key: SLING-6866
> URL: https://issues.apache.org/jira/browse/SLING-6866
> Project: Sling
>  Issue Type: Bug
>  Components: Scripting
>Affects Versions: Scripting HTL Compiler 1.0.0
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
> Fix For: Scripting HTL Compiler 1.0.10
>
>
> When using the following expression
> {code:html}
> 
> {code}
> the output is escaped.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (SLING-6868) Initial content should use more specific path or be migrated to bundle resources

[Carsten Ziegeler (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carsten Ziegeler updated SLING-6868:

Summary: Initial content should use more specific path or be migrated to 
bundle resources  (was: Initial content should use more specific path)

> Initial content should use more specific path or be migrated to bundle 
> resources
> 
>
> Key: SLING-6868
> URL: https://issues.apache.org/jira/browse/SLING-6868
> Project: Sling
>  Issue Type: Bug
>  Components: HApi
>Affects Versions: HApi 1.0.0
>Reporter: Carsten Ziegeler
> Fix For: HApi 1.0.2, HApi 2.0.0
>
>
> Currently the initial content in the hapi bundle does not specify a path, 
> which means it is using "/".
> When applied at the wrong time, it potentially could wipe the whole 
> repository. In addition initial content should always be specified with the 
> most specific path (the tree the bundle is owning)
> So the path is something like /libs/sling/hapi
> or even
> /libs/sling/hapi/components



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SLING-6868) Initial content should use more specific path or be migrated to bundle resources

[Carsten Ziegeler (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-6868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16019339#comment-16019339
 ] 

Carsten Ziegeler commented on SLING-6868:
-

As these resources are static, I think it is even better to use bundle 
resources (using the Sling-Bundle-Resources) header. This way the resources are 
served directly from within the bundle and no content needs to be installed
[~andrei.dulvac]

> Initial content should use more specific path or be migrated to bundle 
> resources
> 
>
> Key: SLING-6868
> URL: https://issues.apache.org/jira/browse/SLING-6868
> Project: Sling
>  Issue Type: Bug
>  Components: HApi
>Affects Versions: HApi 1.0.0
>Reporter: Carsten Ziegeler
> Fix For: HApi 1.0.2, HApi 2.0.0
>
>
> Currently the initial content in the hapi bundle does not specify a path, 
> which means it is using "/".
> When applied at the wrong time, it potentially could wipe the whole 
> repository. In addition initial content should always be specified with the 
> most specific path (the tree the bundle is owning)
> So the path is something like /libs/sling/hapi
> or even
> /libs/sling/hapi/components



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (SLING-6868) Initial content should use more specific path

[Carsten Ziegeler (JIRA)]

Carsten Ziegeler created SLING-6868:
---

 Summary: Initial content should use more specific path
 Key: SLING-6868
 URL: https://issues.apache.org/jira/browse/SLING-6868
 Project: Sling
  Issue Type: Bug
  Components: HApi
Affects Versions: HApi 1.0.0
Reporter: Carsten Ziegeler
 Fix For: HApi 1.0.2, HApi 2.0.0


Currently the initial content in the hapi bundle does not specify a path, which 
means it is using "/".
When applied at the wrong time, it potentially could wipe the whole repository. 
In addition initial content should always be specified with the most specific 
path (the tree the bundle is owning)
So the path is something like /libs/sling/hapi
or even
/libs/sling/hapi/components



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)