FW: adaptTo() 2018: Tickets now available / Start Call for Papers

2018-02-01 Thread Stefan Seifert 
forgot to mention: there is a discount for apache committers (any project - 
sling, felix, jackrabbit)
see https://adapt.to/conference for details.

stefan

-Original Message-
From: Stefan Seifert [mailto:sseif...@pro-vision.de] 
Sent: Thursday, February 1, 2018 3:58 PM
To: dev@felix.apache.org; us...@felix.apache.org
Subject: adaptTo() 2018: Tickets now available / Start Call for Papers

Dear adaptTo() Community,

the sale of tickets for adaptTo() 2018 is open.

Get your Early-Bird-Ticket here: https://adapt.to/tickets

We also started the Call for Papers today! If you would like to be a speaker, 
please check out https://adapt.to/cfp 

Focusing on Apache Sling, Apache Felix and Apache Jackrabbit, the adaptTo() 
conference in Potsdam (near Berlin) is aimed at developers using some or all if 
this stack.

This year´s conference date is 10 - 12 September; latest information can be 
found on https://adapt.to

Kind regards on behalf of the adaptTo() Team,
Stefan

[jira] [Commented] (FELIX-5782) allow resolver errors to be introspected

2018-02-01 Thread JIRA 

[ 
https://issues.apache.org/jira/browse/FELIX-5782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16348803#comment-16348803
 ] 

Raymond Augé commented on FELIX-5782:
-

There should be no outward change in behavior. This only comes into play when 
(and if) a client of the resolver obtains the ResolutionException and proceeded 
to walk through the "causes".

> allow resolver errors to be introspected
> 
>
> Key: FELIX-5782
> URL: https://issues.apache.org/jira/browse/FELIX-5782
> Project: Felix
>  Issue Type: Improvement
>  Components: Resolver
>Reporter: Raymond Augé
>Assignee: Thomas Watson
>Priority: Minor
>
> The current model for resolver errors does not provide any means of 
> introspecting deeper knowledge that the resolver gained. The information is 
> internal only, which makes user feedback more difficult to produce than 
> necessary.
> I propose to expose the error types by means of an exported package 
> {{org.apache.felix.resolver.error}}. This will allow interested clients to 
> dig more deeply into the reasons for resolution failure in order to provide 
> better feedback to users.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (FELIX-5782) allow resolver errors to be introspected

2018-02-01 Thread Karl Pauls (JIRA) 

[ 
https://issues.apache.org/jira/browse/FELIX-5782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16348794#comment-16348794
 ] 

Karl Pauls commented on FELIX-5782:
---

[~rotty3000], will this require changes to the framework as well?


> allow resolver errors to be introspected
> 
>
> Key: FELIX-5782
> URL: https://issues.apache.org/jira/browse/FELIX-5782
> Project: Felix
>  Issue Type: Improvement
>  Components: Resolver
>Reporter: Raymond Augé
>Assignee: Thomas Watson
>Priority: Minor
>
> The current model for resolver errors does not provide any means of 
> introspecting deeper knowledge that the resolver gained. The information is 
> internal only, which makes user feedback more difficult to produce than 
> necessary.
> I propose to expose the error types by means of an exported package 
> {{org.apache.felix.resolver.error}}. This will allow interested clients to 
> dig more deeply into the reasons for resolution failure in order to provide 
> better feedback to users.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] felix pull request #131: FELIX-5782 allow resolver errors to be introspected

2018-02-01 Thread rotty3000 
GitHub user rotty3000 opened a pull request:

https://github.com/apache/felix/pull/131

FELIX-5782 allow resolver errors to be introspected

Signed-off-by: Raymond Augé 

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/rotty3000/felix trunk

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/felix/pull/131.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #131


commit 07e9f6ccb6be3c9fa193bcfc1ded607a7622eecd
Author: Raymond Augé 
Date:   2018-01-31T20:31:18Z

FELIX-5782 allow resolver errors to be introspected

Signed-off-by: Raymond Augé 




---

adaptTo() 2018: Tickets now available / Start Call for Papers

2018-02-01 Thread Stefan Seifert 
Dear adaptTo() Community,

the sale of tickets for adaptTo() 2018 is open.

Get your Early-Bird-Ticket here: https://adapt.to/tickets

We also started the Call for Papers today! If you would like to be a speaker, 
please check out https://adapt.to/cfp 

Focusing on Apache Sling, Apache Felix and Apache Jackrabbit, the adaptTo() 
conference in Potsdam (near Berlin) is aimed at developers using some or all if 
this stack.

This year´s conference date is 10 - 12 September; latest information can be 
found on https://adapt.to

Kind regards on behalf of the adaptTo() Team,
Stefan

[jira] [Commented] (FELIX-5782) allow resolver errors to be introspected

2018-02-01 Thread JIRA 

[ 
https://issues.apache.org/jira/browse/FELIX-5782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16348678#comment-16348678
 ] 

Raymond Augé commented on FELIX-5782:
-

or [~rickhall] whoever gets to it first!

> allow resolver errors to be introspected
> 
>
> Key: FELIX-5782
> URL: https://issues.apache.org/jira/browse/FELIX-5782
> Project: Felix
>  Issue Type: Improvement
>  Components: Resolver
>Reporter: Raymond Augé
>Assignee: Thomas Watson
>Priority: Minor
>
> The current model for resolver errors does not provide any means of 
> introspecting deeper knowledge that the resolver gained. The information is 
> internal only, which makes user feedback more difficult to produce than 
> necessary.
> I propose to expose the error types by means of an exported package 
> {{org.apache.felix.resolver.error}}. This will allow interested clients to 
> dig more deeply into the reasons for resolution failure in order to provide 
> better feedback to users.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (FELIX-5782) allow resolver errors to be introspected

2018-02-01 Thread JIRA 

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

Raymond Augé reassigned FELIX-5782:
---

Assignee: Thomas Watson  (was: Raymond Augé)

[~tjwatson] when you have a moment could you review this PR and see if it's ok?

[https://github.com/apache/felix/pull/131]

I've ran tests and also used this in bnd with success.

> allow resolver errors to be introspected
> 
>
> Key: FELIX-5782
> URL: https://issues.apache.org/jira/browse/FELIX-5782
> Project: Felix
>  Issue Type: Improvement
>  Components: Resolver
>Reporter: Raymond Augé
>Assignee: Thomas Watson
>Priority: Minor
>
> The current model for resolver errors does not provide any means of 
> introspecting deeper knowledge that the resolver gained. The information is 
> internal only, which makes user feedback more difficult to produce than 
> necessary.
> I propose to expose the error types by means of an exported package 
> {{org.apache.felix.resolver.error}}. This will allow interested clients to 
> dig more deeply into the reasons for resolution failure in order to provide 
> better feedback to users.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (FELIX-5782) allow resolver errors to be introspected

2018-02-01 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/FELIX-5782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16348672#comment-16348672
 ] 

ASF GitHub Bot commented on FELIX-5782:
---

GitHub user rotty3000 opened a pull request:

https://github.com/apache/felix/pull/131

FELIX-5782 allow resolver errors to be introspected

Signed-off-by: Raymond Augé 

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/rotty3000/felix trunk

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/felix/pull/131.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #131


commit 07e9f6ccb6be3c9fa193bcfc1ded607a7622eecd
Author: Raymond Augé 
Date:   2018-01-31T20:31:18Z

FELIX-5782 allow resolver errors to be introspected

Signed-off-by: Raymond Augé 




> allow resolver errors to be introspected
> 
>
> Key: FELIX-5782
> URL: https://issues.apache.org/jira/browse/FELIX-5782
> Project: Felix
>  Issue Type: Improvement
>  Components: Resolver
>Reporter: Raymond Augé
>Assignee: Raymond Augé
>Priority: Minor
>
> The current model for resolver errors does not provide any means of 
> introspecting deeper knowledge that the resolver gained. The information is 
> internal only, which makes user feedback more difficult to produce than 
> necessary.
> I propose to expose the error types by means of an exported package 
> {{org.apache.felix.resolver.error}}. This will allow interested clients to 
> dig more deeply into the reasons for resolution failure in order to provide 
> better feedback to users.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (FELIX-5782) allow resolver errors to be introspected

2018-02-01 Thread JIRA 

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

Raymond Augé updated FELIX-5782:

Description: 
The current model for resolver errors does not provide any means of 
introspecting deeper knowledge that the resolver gained. The information is 
internal only, which makes user feedback more difficult to produce than 
necessary.

I propose to expose the error types by means of an exported package 
{{org.apache.felix.resolver.error}}. This will allow interested clients to dig 
more deeply into the reasons for resolution failure in order to provide better 
feedback to users.

  was:
The current model for resolver errors does not provide any means of 
introspecting deeper knowledge that the resolver gained. The information is 
internal only, which makes user feedback more difficult to produce than 
necessary.

I propose to expose the error types by means of an exported package 
{{org.apache.felix.resolver.errors}}. This will allow interested clients to dig 
more deeply into the reasons for resolution failure in order to provide better 
feedback to users.


> allow resolver errors to be introspected
> 
>
> Key: FELIX-5782
> URL: https://issues.apache.org/jira/browse/FELIX-5782
> Project: Felix
>  Issue Type: Improvement
>  Components: Resolver
>Reporter: Raymond Augé
>Assignee: Raymond Augé
>Priority: Minor
>
> The current model for resolver errors does not provide any means of 
> introspecting deeper knowledge that the resolver gained. The information is 
> internal only, which makes user feedback more difficult to produce than 
> necessary.
> I propose to expose the error types by means of an exported package 
> {{org.apache.felix.resolver.error}}. This will allow interested clients to 
> dig more deeply into the reasons for resolution failure in order to provide 
> better feedback to users.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Work started] (FELIX-5782) allow resolver errors to be introspected

2018-02-01 Thread JIRA 

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

Work on FELIX-5782 started by Raymond Augé.
---
> allow resolver errors to be introspected
> 
>
> Key: FELIX-5782
> URL: https://issues.apache.org/jira/browse/FELIX-5782
> Project: Felix
>  Issue Type: Improvement
>  Components: Resolver
>Reporter: Raymond Augé
>Assignee: Raymond Augé
>Priority: Minor
>
> The current model for resolver errors does not provide any means of 
> introspecting deeper knowledge that the resolver gained. The information is 
> internal only, which makes user feedback more difficult to produce than 
> necessary.
> I propose to expose the error types by means of an exported package 
> {{org.apache.felix.resolver.errors}}. This will allow interested clients to 
> dig more deeply into the reasons for resolution failure in order to provide 
> better feedback to users.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (FELIX-5782) allow resolver errors to be introspected

2018-02-01 Thread JIRA 
Raymond Augé created FELIX-5782:
---

 Summary: allow resolver errors to be introspected
 Key: FELIX-5782
 URL: https://issues.apache.org/jira/browse/FELIX-5782
 Project: Felix
  Issue Type: Improvement
  Components: Resolver
Reporter: Raymond Augé
Assignee: Raymond Augé


The current model for resolver errors does not provide any means of 
introspecting deeper knowledge that the resolver gained. The information is 
internal only, which makes user feedback more difficult to produce than 
necessary.

I propose to expose the error types by means of an exported package 
{{org.apache.felix.resolver.errors}}. This will allow interested clients to dig 
more deeply into the reasons for resolution failure in order to provide better 
feedback to users.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)