[jira] [Commented] (SLING-8136) Analyser fails when javax.*, org.xml.sax.*, org.w3c.dom* or org.ietf.jgss imports are found

2018-11-28 Thread Karl Pauls (JIRA)


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

Karl Pauls commented on SLING-8136:
---

[~rombert], yes.

> Analyser fails when javax.*, org.xml.sax.*, org.w3c.dom* or org.ietf.jgss 
> imports are found
> ---
>
> Key: SLING-8136
> URL: https://issues.apache.org/jira/browse/SLING-8136
> Project: Sling
>  Issue Type: Bug
>  Components: Feature Model
>Reporter: Robert Munteanu
>Priority: Major
> Fix For: Feature Model Analyser 0.8.2
>
>
> I've tried running the {{slingfeature-maven-plugin}} to analyse imports and 
> exports using the {{bundle-packages}} analyser.
> This seems to work just fine, just that some packages - found in the issue 
> title - are not seen as being provided by the framework. Some errors that pop 
> up are:
> {noformat}
> [ERROR] Bundle oak-auth-ldap:1.9.11 is importing package(s) org.ietf.jgss in 
> start level 0 but no bundle is exporting these for that start level.
> [ERROR] Bundle oak-lucene:1.9.11 is importing package(s) 
> [org.xml.sax.helpers, org.xml.sax] in start level 0 but no bundle is 
> exporting these for that start level.
> {noformat}
> These packages are provided using an {{org.osgi.framework.system.packages}} 
> framework property, so I guess there is some glue missing to make this work.



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


[jira] [Commented] (SLING-8136) Analyser fails when javax.*, org.xml.sax.*, org.w3c.dom* or org.ietf.jgss imports are found

2018-11-28 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on SLING-8136:
---

rombert closed pull request #11: SLING-8136 - Analyser fails when javax.*, 
org.xml.sax.*, org.w3c.dom* or org.ietf.jgss imports are found
URL: https://github.com/apache/sling-org-apache-sling-feature-analyser/pull/11
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Analyser fails when javax.*, org.xml.sax.*, org.w3c.dom* or org.ietf.jgss 
> imports are found
> ---
>
> Key: SLING-8136
> URL: https://issues.apache.org/jira/browse/SLING-8136
> Project: Sling
>  Issue Type: Bug
>  Components: Feature Model
>Reporter: Robert Munteanu
>Assignee: Karl Pauls
>Priority: Major
> Fix For: Feature Model Analyser 0.8.2
>
>
> I've tried running the {{slingfeature-maven-plugin}} to analyse imports and 
> exports using the {{bundle-packages}} analyser.
> This seems to work just fine, just that some packages - found in the issue 
> title - are not seen as being provided by the framework. Some errors that pop 
> up are:
> {noformat}
> [ERROR] Bundle oak-auth-ldap:1.9.11 is importing package(s) org.ietf.jgss in 
> start level 0 but no bundle is exporting these for that start level.
> [ERROR] Bundle oak-lucene:1.9.11 is importing package(s) 
> [org.xml.sax.helpers, org.xml.sax] in start level 0 but no bundle is 
> exporting these for that start level.
> {noformat}
> These packages are provided using an {{org.osgi.framework.system.packages}} 
> framework property, so I guess there is some glue missing to make this work.



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


[jira] [Commented] (SLING-8136) Analyser fails when javax.*, org.xml.sax.*, org.w3c.dom* or org.ietf.jgss imports are found

2018-11-28 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on SLING-8136:
---

rombert commented on issue #11: SLING-8136 - Analyser fails when javax.*, 
org.xml.sax.*, org.w3c.dom* or org.ietf.jgss imports are found
URL: 
https://github.com/apache/sling-org-apache-sling-feature-analyser/pull/11#issuecomment-442429819
 
 
   @karlpauls provided a proper fix in 
https://github.com/apache/sling-org-apache-sling-feature-analyser/commit/591bfb9,
 closing


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Analyser fails when javax.*, org.xml.sax.*, org.w3c.dom* or org.ietf.jgss 
> imports are found
> ---
>
> Key: SLING-8136
> URL: https://issues.apache.org/jira/browse/SLING-8136
> Project: Sling
>  Issue Type: Bug
>  Components: Feature Model
>Reporter: Robert Munteanu
>Assignee: Karl Pauls
>Priority: Major
> Fix For: Feature Model Analyser 0.8.2
>
>
> I've tried running the {{slingfeature-maven-plugin}} to analyse imports and 
> exports using the {{bundle-packages}} analyser.
> This seems to work just fine, just that some packages - found in the issue 
> title - are not seen as being provided by the framework. Some errors that pop 
> up are:
> {noformat}
> [ERROR] Bundle oak-auth-ldap:1.9.11 is importing package(s) org.ietf.jgss in 
> start level 0 but no bundle is exporting these for that start level.
> [ERROR] Bundle oak-lucene:1.9.11 is importing package(s) 
> [org.xml.sax.helpers, org.xml.sax] in start level 0 but no bundle is 
> exporting these for that start level.
> {noformat}
> These packages are provided using an {{org.osgi.framework.system.packages}} 
> framework property, so I guess there is some glue missing to make this work.



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


[jira] [Commented] (SLING-8136) Analyser fails when javax.*, org.xml.sax.*, org.w3c.dom* or org.ietf.jgss imports are found

2018-11-28 Thread Robert Munteanu (JIRA)


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

Robert Munteanu commented on SLING-8136:


[~kpauls] - I think you basically solved this with 
[sling-org-apache-sling-feature-analyser commit 
591bfb9|https://github.com/apache/sling-org-apache-sling-feature-analyser/commit/591bfb9],
 right?

> Analyser fails when javax.*, org.xml.sax.*, org.w3c.dom* or org.ietf.jgss 
> imports are found
> ---
>
> Key: SLING-8136
> URL: https://issues.apache.org/jira/browse/SLING-8136
> Project: Sling
>  Issue Type: Bug
>  Components: Feature Model
>Reporter: Robert Munteanu
>Priority: Major
> Fix For: Feature Model Analyser 0.8.2
>
>
> I've tried running the {{slingfeature-maven-plugin}} to analyse imports and 
> exports using the {{bundle-packages}} analyser.
> This seems to work just fine, just that some packages - found in the issue 
> title - are not seen as being provided by the framework. Some errors that pop 
> up are:
> {noformat}
> [ERROR] Bundle oak-auth-ldap:1.9.11 is importing package(s) org.ietf.jgss in 
> start level 0 but no bundle is exporting these for that start level.
> [ERROR] Bundle oak-lucene:1.9.11 is importing package(s) 
> [org.xml.sax.helpers, org.xml.sax] in start level 0 but no bundle is 
> exporting these for that start level.
> {noformat}
> These packages are provided using an {{org.osgi.framework.system.packages}} 
> framework property, so I guess there is some glue missing to make this work.



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


[jira] [Commented] (SLING-8136) Analyser fails when javax.*, org.xml.sax.*, org.w3c.dom* or org.ietf.jgss imports are found

2018-11-27 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on SLING-8136:
---

rombert commented on issue #11: SLING-8136 - Analyser fails when javax.*, 
org.xml.sax.*, org.w3c.dom* or org.ietf.jgss imports are found
URL: 
https://github.com/apache/sling-org-apache-sling-feature-analyser/pull/11#issuecomment-442056390
 
 
   Well, I guess we could always read them from the 
`org.osgi.framework.system.packages` property and make sure we interpolate 
them, but I did not find a good way of doing that.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Analyser fails when javax.*, org.xml.sax.*, org.w3c.dom* or org.ietf.jgss 
> imports are found
> ---
>
> Key: SLING-8136
> URL: https://issues.apache.org/jira/browse/SLING-8136
> Project: Sling
>  Issue Type: Bug
>  Components: Feature Model
>Reporter: Robert Munteanu
>Priority: Major
> Fix For: Feature Model Analyser 0.8.2
>
>
> I've tried running the {{slingfeature-maven-plugin}} to analyse imports and 
> exports using the {{bundle-packages}} analyser.
> This seems to work just fine, just that some packages - found in the issue 
> title - are not seen as being provided by the framework. Some errors that pop 
> up are:
> {noformat}
> [ERROR] Bundle oak-auth-ldap:1.9.11 is importing package(s) org.ietf.jgss in 
> start level 0 but no bundle is exporting these for that start level.
> [ERROR] Bundle oak-lucene:1.9.11 is importing package(s) 
> [org.xml.sax.helpers, org.xml.sax] in start level 0 but no bundle is 
> exporting these for that start level.
> {noformat}
> These packages are provided using an {{org.osgi.framework.system.packages}} 
> framework property, so I guess there is some glue missing to make this work.



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


[jira] [Commented] (SLING-8136) Analyser fails when javax.*, org.xml.sax.*, org.w3c.dom* or org.ietf.jgss imports are found

2018-11-27 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on SLING-8136:
---

bosschaert commented on issue #11: SLING-8136 - Analyser fails when javax.*, 
org.xml.sax.*, org.w3c.dom* or org.ietf.jgss imports are found
URL: 
https://github.com/apache/sling-org-apache-sling-feature-analyser/pull/11#issuecomment-442055861
 
 
   Hi @rombert one thought I have is that it might be an idea to configure the 
packages from the maven plugin configuration rather than hardcoding it? 
Accessing configuration is possible via the 
`AnalyserTaskContext.getConfiguration()` API. 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Analyser fails when javax.*, org.xml.sax.*, org.w3c.dom* or org.ietf.jgss 
> imports are found
> ---
>
> Key: SLING-8136
> URL: https://issues.apache.org/jira/browse/SLING-8136
> Project: Sling
>  Issue Type: Bug
>  Components: Feature Model
>Reporter: Robert Munteanu
>Priority: Major
> Fix For: Feature Model Analyser 0.8.2
>
>
> I've tried running the {{slingfeature-maven-plugin}} to analyse imports and 
> exports using the {{bundle-packages}} analyser.
> This seems to work just fine, just that some packages - found in the issue 
> title - are not seen as being provided by the framework. Some errors that pop 
> up are:
> {noformat}
> [ERROR] Bundle oak-auth-ldap:1.9.11 is importing package(s) org.ietf.jgss in 
> start level 0 but no bundle is exporting these for that start level.
> [ERROR] Bundle oak-lucene:1.9.11 is importing package(s) 
> [org.xml.sax.helpers, org.xml.sax] in start level 0 but no bundle is 
> exporting these for that start level.
> {noformat}
> These packages are provided using an {{org.osgi.framework.system.packages}} 
> framework property, so I guess there is some glue missing to make this work.



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


[jira] [Commented] (SLING-8136) Analyser fails when javax.*, org.xml.sax.*, org.w3c.dom* or org.ietf.jgss imports are found

2018-11-27 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on SLING-8136:
---

rombert opened a new pull request #11: SLING-8136 - Analyser fails when 
javax.*, org.xml.sax.*, org.w3c.dom* or org.ietf.jgss imports are found
URL: https://github.com/apache/sling-org-apache-sling-feature-analyser/pull/11
 
 
   This is more or less a band-aid, but at least it helps in moving forward 
with using the Analyser tasks.
   
   I'd be happy with a more permanent solution, but I can't seem to find it.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Analyser fails when javax.*, org.xml.sax.*, org.w3c.dom* or org.ietf.jgss 
> imports are found
> ---
>
> Key: SLING-8136
> URL: https://issues.apache.org/jira/browse/SLING-8136
> Project: Sling
>  Issue Type: Bug
>  Components: Feature Model
>Reporter: Robert Munteanu
>Priority: Major
> Fix For: Feature Model Analyser 0.8.2
>
>
> I've tried running the {{slingfeature-maven-plugin}} to analyse imports and 
> exports using the {{bundle-packages}} analyser.
> This seems to work just fine, just that some packages - found in the issue 
> title - are not seen as being provided by the framework. Some errors that pop 
> up are:
> {noformat}
> [ERROR] Bundle oak-auth-ldap:1.9.11 is importing package(s) org.ietf.jgss in 
> start level 0 but no bundle is exporting these for that start level.
> [ERROR] Bundle oak-lucene:1.9.11 is importing package(s) 
> [org.xml.sax.helpers, org.xml.sax] in start level 0 but no bundle is 
> exporting these for that start level.
> {noformat}
> These packages are provided using an {{org.osgi.framework.system.packages}} 
> framework property, so I guess there is some glue missing to make this work.



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