[jira] [Commented] (KARAF-2556) Upgrade to Pax Web 2.1.5
[ https://issues.apache.org/jira/browse/KARAF-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13818027#comment-13818027 ] Jean-Baptiste Onofré commented on KARAF-2556: - Fixed on karaf-2.x: http://svn.apache.org/viewvc?view=revision&revision=1540256 > Upgrade to Pax Web 2.1.5 > > > Key: KARAF-2556 > URL: https://issues.apache.org/jira/browse/KARAF-2556 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-webcontainer >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 2.4.0 > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (KARAF-2556) Upgrade to Pax Web 2.1.5
[ https://issues.apache.org/jira/browse/KARAF-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-2556. - Resolution: Fixed > Upgrade to Pax Web 2.1.5 > > > Key: KARAF-2556 > URL: https://issues.apache.org/jira/browse/KARAF-2556 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-webcontainer >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 2.4.0 > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Work started] (KARAF-2556) Upgrade to Pax Web 2.1.5
[ https://issues.apache.org/jira/browse/KARAF-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KARAF-2556 started by Jean-Baptiste Onofré. > Upgrade to Pax Web 2.1.5 > > > Key: KARAF-2556 > URL: https://issues.apache.org/jira/browse/KARAF-2556 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-webcontainer >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 2.4.0 > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (KARAF-2543) Update to Pax-Web 3.0.3
[ https://issues.apache.org/jira/browse/KARAF-2543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13818025#comment-13818025 ] Jean-Baptiste Onofré commented on KARAF-2543: - Fixed on trunk: http://svn.apache.org/viewvc?view=revision&revision=1540255 > Update to Pax-Web 3.0.3 > --- > > Key: KARAF-2543 > URL: https://issues.apache.org/jira/browse/KARAF-2543 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-webcontainer >Affects Versions: 3.0.0 >Reporter: Achim Nierbeck >Assignee: Jean-Baptiste Onofré > Fix For: 3.0.0 > > > An Important Bugfix is available with Pax-Web 3.0.3, therefore Karaf should > include this for 3.0.0 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (KARAF-2556) Upgrade to Pax Web 2.1.5
Jean-Baptiste Onofré created KARAF-2556: --- Summary: Upgrade to Pax Web 2.1.5 Key: KARAF-2556 URL: https://issues.apache.org/jira/browse/KARAF-2556 Project: Karaf Issue Type: Dependency upgrade Components: karaf-webcontainer Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 2.4.0 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (KARAF-2543) Update to Pax-Web 3.0.3
[ https://issues.apache.org/jira/browse/KARAF-2543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-2543. - Resolution: Fixed > Update to Pax-Web 3.0.3 > --- > > Key: KARAF-2543 > URL: https://issues.apache.org/jira/browse/KARAF-2543 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-webcontainer >Affects Versions: 3.0.0 >Reporter: Achim Nierbeck >Assignee: Jean-Baptiste Onofré > Fix For: 3.0.0 > > > An Important Bugfix is available with Pax-Web 3.0.3, therefore Karaf should > include this for 3.0.0 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (KARAF-2543) Update to Pax-Web 3.0.3
[ https://issues.apache.org/jira/browse/KARAF-2543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13818020#comment-13818020 ] Jean-Baptiste Onofré commented on KARAF-2543: - Pax Web 3.0.3 has been released. I update. > Update to Pax-Web 3.0.3 > --- > > Key: KARAF-2543 > URL: https://issues.apache.org/jira/browse/KARAF-2543 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-webcontainer >Affects Versions: 3.0.0 >Reporter: Achim Nierbeck >Assignee: Jean-Baptiste Onofré > Fix For: 3.0.0 > > > An Important Bugfix is available with Pax-Web 3.0.3, therefore Karaf should > include this for 3.0.0 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Assigned] (KARAF-2543) Update to Pax-Web 3.0.3
[ https://issues.apache.org/jira/browse/KARAF-2543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned KARAF-2543: --- Assignee: Jean-Baptiste Onofré (was: Achim Nierbeck) > Update to Pax-Web 3.0.3 > --- > > Key: KARAF-2543 > URL: https://issues.apache.org/jira/browse/KARAF-2543 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-webcontainer >Affects Versions: 3.0.0 >Reporter: Achim Nierbeck >Assignee: Jean-Baptiste Onofré > Fix For: 3.0.0 > > > An Important Bugfix is available with Pax-Web 3.0.3, therefore Karaf should > include this for 3.0.0 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (KARAF-2555) Upgrade to Felix Metatype 1.0.8
[ https://issues.apache.org/jira/browse/KARAF-2555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-2555. - Resolution: Fixed > Upgrade to Felix Metatype 1.0.8 > --- > > Key: KARAF-2555 > URL: https://issues.apache.org/jira/browse/KARAF-2555 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-webconsole >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 2.4.0, 3.0.0, 2.3.4 > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (KARAF-2555) Upgrade to Felix Metatype 1.0.8
[ https://issues.apache.org/jira/browse/KARAF-2555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13817500#comment-13817500 ] Jean-Baptiste Onofré commented on KARAF-2555: - Fixed on karaf-2.3.x: http://svn.apache.org/viewvc?view=revision&revision=1540135 > Upgrade to Felix Metatype 1.0.8 > --- > > Key: KARAF-2555 > URL: https://issues.apache.org/jira/browse/KARAF-2555 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-webconsole >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 2.4.0, 3.0.0, 2.3.4 > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (KARAF-2555) Upgrade to Felix Metatype 1.0.8
[ https://issues.apache.org/jira/browse/KARAF-2555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13817493#comment-13817493 ] Jean-Baptiste Onofré commented on KARAF-2555: - Fixed on karaf-2.x: http://svn.apache.org/viewvc?view=revision&revision=1540132 > Upgrade to Felix Metatype 1.0.8 > --- > > Key: KARAF-2555 > URL: https://issues.apache.org/jira/browse/KARAF-2555 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-webconsole >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 2.4.0, 3.0.0, 2.3.4 > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (KARAF-2555) Upgrade to Felix Metatype 1.0.8
Jean-Baptiste Onofré created KARAF-2555: --- Summary: Upgrade to Felix Metatype 1.0.8 Key: KARAF-2555 URL: https://issues.apache.org/jira/browse/KARAF-2555 Project: Karaf Issue Type: Dependency upgrade Components: karaf-webconsole Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 2.4.0, 3.0.0, 2.3.4 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (KARAF-2555) Upgrade to Felix Metatype 1.0.8
[ https://issues.apache.org/jira/browse/KARAF-2555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13817479#comment-13817479 ] Jean-Baptiste Onofré commented on KARAF-2555: - Fixed on trunk: http://svn.apache.org/viewvc?view=revision&revision=1540128 > Upgrade to Felix Metatype 1.0.8 > --- > > Key: KARAF-2555 > URL: https://issues.apache.org/jira/browse/KARAF-2555 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-webconsole >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 2.4.0, 3.0.0, 2.3.4 > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (KARAF-2554) Upgrade to Felix ConfigAdmin 1.8.0
[ https://issues.apache.org/jira/browse/KARAF-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13817466#comment-13817466 ] Jean-Baptiste Onofré commented on KARAF-2554: - Fixed on karaf-2.3.x: http://svn.apache.org/viewvc?view=revision&revision=1540120 > Upgrade to Felix ConfigAdmin 1.8.0 > -- > > Key: KARAF-2554 > URL: https://issues.apache.org/jira/browse/KARAF-2554 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 2.4.0, 3.0.0, 2.3.4 > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (KARAF-2554) Upgrade to Felix ConfigAdmin 1.8.0
[ https://issues.apache.org/jira/browse/KARAF-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-2554. - Resolution: Fixed > Upgrade to Felix ConfigAdmin 1.8.0 > -- > > Key: KARAF-2554 > URL: https://issues.apache.org/jira/browse/KARAF-2554 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 2.4.0, 3.0.0, 2.3.4 > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (KARAF-2554) Upgrade to Felix ConfigAdmin 1.8.0
[ https://issues.apache.org/jira/browse/KARAF-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13817439#comment-13817439 ] Jean-Baptiste Onofré commented on KARAF-2554: - Fixed on karaf-2.x: http://svn.apache.org/viewvc?view=revision&revision=1540116 > Upgrade to Felix ConfigAdmin 1.8.0 > -- > > Key: KARAF-2554 > URL: https://issues.apache.org/jira/browse/KARAF-2554 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 2.4.0, 3.0.0, 2.3.4 > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (KARAF-2554) Upgrade to Felix ConfigAdmin 1.8.0
[ https://issues.apache.org/jira/browse/KARAF-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13817419#comment-13817419 ] Jean-Baptiste Onofré commented on KARAF-2554: - Fixed on trunk: http://svn.apache.org/viewvc?view=revision&revision=1540113 > Upgrade to Felix ConfigAdmin 1.8.0 > -- > > Key: KARAF-2554 > URL: https://issues.apache.org/jira/browse/KARAF-2554 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 2.4.0, 3.0.0, 2.3.4 > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (KARAF-2554) Upgrade to Felix ConfigAdmin 1.8.0
Jean-Baptiste Onofré created KARAF-2554: --- Summary: Upgrade to Felix ConfigAdmin 1.8.0 Key: KARAF-2554 URL: https://issues.apache.org/jira/browse/KARAF-2554 Project: Karaf Issue Type: Dependency upgrade Components: karaf-core Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 2.4.0, 3.0.0, 2.3.4 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (KARAF-2553) Upgrade to commons-compress 1.6
[ https://issues.apache.org/jira/browse/KARAF-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13817413#comment-13817413 ] Jean-Baptiste Onofré commented on KARAF-2553: - Fixed on karaf-2.3.x: branch: http://svn.apache.org/viewvc?view=revision&revision=1540109 > Upgrade to commons-compress 1.6 > --- > > Key: KARAF-2553 > URL: https://issues.apache.org/jira/browse/KARAF-2553 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-test >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 2.4.0, 3.0.0, 2.3.4 > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (KARAF-2553) Upgrade to commons-compress 1.6
[ https://issues.apache.org/jira/browse/KARAF-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-2553. - Resolution: Fixed > Upgrade to commons-compress 1.6 > --- > > Key: KARAF-2553 > URL: https://issues.apache.org/jira/browse/KARAF-2553 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-test >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 2.4.0, 3.0.0, 2.3.4 > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (KARAF-2553) Upgrade to commons-compress 1.6
[ https://issues.apache.org/jira/browse/KARAF-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13817392#comment-13817392 ] Jean-Baptiste Onofré commented on KARAF-2553: - Fixed on karaf-2.x branch: http://svn.apache.org/viewvc?view=revision&revision=1540102 > Upgrade to commons-compress 1.6 > --- > > Key: KARAF-2553 > URL: https://issues.apache.org/jira/browse/KARAF-2553 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-test >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 2.4.0, 3.0.0, 2.3.4 > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (KARAF-2545) Add feature:repo-refresh command
[ https://issues.apache.org/jira/browse/KARAF-2545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13817390#comment-13817390 ] Jean-Baptiste Onofré commented on KARAF-2545: - I think it's a bit redundant to have -ra without argument. It would be easier to have: karaf@root()> feature:repo-add For transition purpose, I would add an alias feature:repo-refresh to feature:repo-add: karaf@root()> feature:repo-refresh > Add feature:repo-refresh command > > > Key: KARAF-2545 > URL: https://issues.apache.org/jira/browse/KARAF-2545 > Project: Karaf > Issue Type: New Feature > Components: karaf-shell >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 3.0.0 > > > Previous Karaf versions provided features:refreshurl (to refresh one or all > features URL). > Unfortunately, we don't have the equivalent of features:refreshurl in 3.0.0. > I gonna add feature:repo-refresh command (and the corresponding operatiob on > the Feature MBean). -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (KARAF-2553) Upgrade to commons-compress 1.6
[ https://issues.apache.org/jira/browse/KARAF-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13817384#comment-13817384 ] Jean-Baptiste Onofré commented on KARAF-2553: - Fixed on trunk: http://svn.apache.org/viewvc?view=revision&revision=1540098 > Upgrade to commons-compress 1.6 > --- > > Key: KARAF-2553 > URL: https://issues.apache.org/jira/browse/KARAF-2553 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-test >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 2.4.0, 3.0.0, 2.3.4 > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (KARAF-2553) Upgrade to commons-compress 1.6
Jean-Baptiste Onofré created KARAF-2553: --- Summary: Upgrade to commons-compress 1.6 Key: KARAF-2553 URL: https://issues.apache.org/jira/browse/KARAF-2553 Project: Karaf Issue Type: Dependency upgrade Components: karaf-test Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 2.4.0, 3.0.0, 2.3.4 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (KARAF-2545) Add feature:repo-refresh command
[ https://issues.apache.org/jira/browse/KARAF-2545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13817369#comment-13817369 ] Christian Schneider commented on KARAF-2545: Sounds good > Add feature:repo-refresh command > > > Key: KARAF-2545 > URL: https://issues.apache.org/jira/browse/KARAF-2545 > Project: Karaf > Issue Type: New Feature > Components: karaf-shell >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 3.0.0 > > > Previous Karaf versions provided features:refreshurl (to refresh one or all > features URL). > Unfortunately, we don't have the equivalent of features:refreshurl in 3.0.0. > I gonna add feature:repo-refresh command (and the corresponding operatiob on > the Feature MBean). -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (KARAF-2545) Add feature:repo-refresh command
[ https://issues.apache.org/jira/browse/KARAF-2545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13817367#comment-13817367 ] Jean-Baptiste Onofré commented on KARAF-2545: - Why not, but in that case the argument should be set as required=false (it's required=true for now, so the user has to provide a repository). > Add feature:repo-refresh command > > > Key: KARAF-2545 > URL: https://issues.apache.org/jira/browse/KARAF-2545 > Project: Karaf > Issue Type: New Feature > Components: karaf-shell >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 3.0.0 > > > Previous Karaf versions provided features:refreshurl (to refresh one or all > features URL). > Unfortunately, we don't have the equivalent of features:refreshurl in 3.0.0. > I gonna add feature:repo-refresh command (and the corresponding operatiob on > the Feature MBean). -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (KARAF-2458) Update to Spring 3.2.4.RELEASE
[ https://issues.apache.org/jira/browse/KARAF-2458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-2458. - Resolution: Fixed > Update to Spring 3.2.4.RELEASE > -- > > Key: KARAF-2458 > URL: https://issues.apache.org/jira/browse/KARAF-2458 > Project: Karaf > Issue Type: Bug >Affects Versions: 2.3.2 >Reporter: Jonathan Anstey >Assignee: Jean-Baptiste Onofré > Fix For: 2.4.0, 3.0.0, 2.3.3 > > > A new release of Spring 3.2 is available. Karaf should be updated to this new > release. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (KARAF-2545) Add feature:repo-refresh command
[ https://issues.apache.org/jira/browse/KARAF-2545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13817365#comment-13817365 ] Christian Schneider commented on KARAF-2545: How about -ra for refresh all? > Add feature:repo-refresh command > > > Key: KARAF-2545 > URL: https://issues.apache.org/jira/browse/KARAF-2545 > Project: Karaf > Issue Type: New Feature > Components: karaf-shell >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 3.0.0 > > > Previous Karaf versions provided features:refreshurl (to refresh one or all > features URL). > Unfortunately, we don't have the equivalent of features:refreshurl in 3.0.0. > I gonna add feature:repo-refresh command (and the corresponding operatiob on > the Feature MBean). -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (KARAF-2545) Add feature:repo-refresh command
[ https://issues.apache.org/jira/browse/KARAF-2545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13817355#comment-13817355 ] Jean-Baptiste Onofré commented on KARAF-2545: - Agree, but feature:repo-add only accept one repo (the repo is mandatory). So, the plan is: 1/ add a keywork ALL, to refresh all repositories 2/ add a note in the migration page in the documentation to explain that refreshUrl has been replaced by repo-add. > Add feature:repo-refresh command > > > Key: KARAF-2545 > URL: https://issues.apache.org/jira/browse/KARAF-2545 > Project: Karaf > Issue Type: New Feature > Components: karaf-shell >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 3.0.0 > > > Previous Karaf versions provided features:refreshurl (to refresh one or all > features URL). > Unfortunately, we don't have the equivalent of features:refreshurl in 3.0.0. > I gonna add feature:repo-refresh command (and the corresponding operatiob on > the Feature MBean). -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (KARAF-2458) Update to Spring 3.2.4.RELEASE
[ https://issues.apache.org/jira/browse/KARAF-2458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2458: Summary: Update to Spring 3.2.4.RELEASE (was: Update to Spring 3.2.5.RELEASE) > Update to Spring 3.2.4.RELEASE > -- > > Key: KARAF-2458 > URL: https://issues.apache.org/jira/browse/KARAF-2458 > Project: Karaf > Issue Type: Bug >Affects Versions: 2.3.2 >Reporter: Jonathan Anstey >Assignee: Jean-Baptiste Onofré > Fix For: 2.3.3, 2.4.0, 3.0.0 > > > A new release of Spring 3.2 is available. Karaf should be updated to this new > release. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (KARAF-2545) Add feature:repo-refresh command
[ https://issues.apache.org/jira/browse/KARAF-2545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13817345#comment-13817345 ] Christian Schneider commented on KARAF-2545: When I consolidated the commands for karaf 3 I made the feature:repo-add refresh the feature if it is already present. So I think we do not need a refresh command any more. > Add feature:repo-refresh command > > > Key: KARAF-2545 > URL: https://issues.apache.org/jira/browse/KARAF-2545 > Project: Karaf > Issue Type: New Feature > Components: karaf-shell >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 3.0.0 > > > Previous Karaf versions provided features:refreshurl (to refresh one or all > features URL). > Unfortunately, we don't have the equivalent of features:refreshurl in 3.0.0. > I gonna add feature:repo-refresh command (and the corresponding operatiob on > the Feature MBean). -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (KARAF-1894) Framework's active start level is set to org.osgi.framework.startlevel.beginning too early when launching Karaf with empty bundle cache
[ https://issues.apache.org/jira/browse/KARAF-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13817341#comment-13817341 ] Shrish Srivastava commented on KARAF-1894: -- I am out of office today and will be back on 2nd December.Please contact kkrish...@talend.com or afu...@talend.com for any urgent matter. > Framework's active start level is set to > org.osgi.framework.startlevel.beginning too early when launching Karaf with > empty bundle cache > --- > > Key: KARAF-1894 > URL: https://issues.apache.org/jira/browse/KARAF-1894 > Project: Karaf > Issue Type: Bug >Affects Versions: 2.2.9, 3.0.0 > Environment: Mac 10.8.2/Oracle JDK 1.6.0_35 >Reporter: Jason Montojo >Assignee: Jean-Baptiste Onofré > Fix For: 2.2.12, 2.4.0, 3.0.1, 2.3.4 > > Attachments: slbug.tar-3.0.gz, slbug.tar.gz > > > When launching Karaf 2.2.9 with an empty bundle cache, the framework's active > start level is already set to org.osgi.framework.startlevel.beginning before > all the boot features have been started. The impact is that bundles can be > loaded in the wrong order, and File Install ends up scanning the deploy > folder when it's not supposed to. > This is problematic because we're using boot features to load up our core > infrastructure and the deploy folder to host plugins. If we prepackage any > plugins with our product with an empty bundle cache, the plugins get > installed and started before the core. > The attached tarball contains a set of 3 bundles that reproduce the symptoms. > Simply untar within the apache-karaf-2.2.9 directory. > In the test tarball, there are 3 bundles that do the same thing. When > start() is called, they print out their name and the framework's current > start level, then wait for 1 second. > bundle1 (start-level=60) and bundle2 (start-level=80) are part of a boot > feature. However, bundle2 is listed first in the XML. bundle3 is in the > deploy directory. File Install is configured so that it doesn't scan until > start level 81 (via felix.fileinstall.active.level). > I'm expecting that the bundles are loaded in this order: bundle1, bundle2, > bundle3. > If I clear the bundle cache and start Karaf, I get the following output: > [bundle2] 100 > [bundle3] 100 > [bundle1] 100 > This indicates that when bundle2's start() is called, the framework's start > level is already set to org.osgi.framework.startlevel.beginning (in this > case, 100) before the boot features have started. > If I run Karaf again without clearing the bundle cache, I get the following: > [bundle1] 60 > [bundle2] 80 > [bundle3] 80 > This is better, but felix.fileinstall.active.level is set to 81, so bundle3 > should not be starting at start level 80. This is probably a separate issue. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (KARAF-1894) Framework's active start level is set to org.osgi.framework.startlevel.beginning too early when launching Karaf with empty bundle cache
[ https://issues.apache.org/jira/browse/KARAF-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-1894: Fix Version/s: (was: 3.0.0) 3.0.1 > Framework's active start level is set to > org.osgi.framework.startlevel.beginning too early when launching Karaf with > empty bundle cache > --- > > Key: KARAF-1894 > URL: https://issues.apache.org/jira/browse/KARAF-1894 > Project: Karaf > Issue Type: Bug >Affects Versions: 2.2.9, 3.0.0 > Environment: Mac 10.8.2/Oracle JDK 1.6.0_35 >Reporter: Jason Montojo >Assignee: Jean-Baptiste Onofré > Fix For: 2.2.12, 2.4.0, 3.0.1, 2.3.4 > > Attachments: slbug.tar-3.0.gz, slbug.tar.gz > > > When launching Karaf 2.2.9 with an empty bundle cache, the framework's active > start level is already set to org.osgi.framework.startlevel.beginning before > all the boot features have been started. The impact is that bundles can be > loaded in the wrong order, and File Install ends up scanning the deploy > folder when it's not supposed to. > This is problematic because we're using boot features to load up our core > infrastructure and the deploy folder to host plugins. If we prepackage any > plugins with our product with an empty bundle cache, the plugins get > installed and started before the core. > The attached tarball contains a set of 3 bundles that reproduce the symptoms. > Simply untar within the apache-karaf-2.2.9 directory. > In the test tarball, there are 3 bundles that do the same thing. When > start() is called, they print out their name and the framework's current > start level, then wait for 1 second. > bundle1 (start-level=60) and bundle2 (start-level=80) are part of a boot > feature. However, bundle2 is listed first in the XML. bundle3 is in the > deploy directory. File Install is configured so that it doesn't scan until > start level 81 (via felix.fileinstall.active.level). > I'm expecting that the bundles are loaded in this order: bundle1, bundle2, > bundle3. > If I clear the bundle cache and start Karaf, I get the following output: > [bundle2] 100 > [bundle3] 100 > [bundle1] 100 > This indicates that when bundle2's start() is called, the framework's start > level is already set to org.osgi.framework.startlevel.beginning (in this > case, 100) before the boot features have started. > If I run Karaf again without clearing the bundle cache, I get the following: > [bundle1] 60 > [bundle2] 80 > [bundle3] 80 > This is better, but felix.fileinstall.active.level is set to 81, so bundle3 > should not be starting at start level 80. This is probably a separate issue. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (KARAF-2188) JPA bundle error out at shutdown
[ https://issues.apache.org/jira/browse/KARAF-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2188: Fix Version/s: (was: 3.0.0) 3.0.1 > JPA bundle error out at shutdown > > > Key: KARAF-2188 > URL: https://issues.apache.org/jira/browse/KARAF-2188 > Project: Karaf > Issue Type: Bug >Affects Versions: 2.3.1 > Environment: windows/linux/jdk 1.7 >Reporter: Dan Tran > Fix For: 2.4.0, 3.0.1, 2.3.4 > > > Detail discussion is here > http://karaf.922171.n3.nabble.com/Aries-JPA-error-to-stdout-at-karaf-2-3-1-SNAPSHOT-td4027680.html > Probably from aries upgrade -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (KARAF-2011) dev:watch looks in an incorrect local maven repository
[ https://issues.apache.org/jira/browse/KARAF-2011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2011: Fix Version/s: (was: 3.0.0) 3.0.1 > dev:watch looks in an incorrect local maven repository > -- > > Key: KARAF-2011 > URL: https://issues.apache.org/jira/browse/KARAF-2011 > Project: Karaf > Issue Type: Bug > Components: karaf-shell >Affects Versions: 2.2.9, 2.3.0 >Reporter: Bengt Rodehav >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 2.2.12, 2.4.0, 3.0.1, 2.3.4 > > > If a non-default maven repository is used (by setting the "localRepository" > property in maven's settings.xml), then dev:watch does not work. It seems > like dev:watch does not consider the "localRepository" setting when looking > for a bundle in maven. > Note that other parts of Karaf does take the "localRepository" setting into > account since installing features and using the "update" command works. > This has been discussed on the user mailing list: > http://karaf.922171.n3.nabble.com/dev-watch-problems-td4026725.html#a4026730 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (KARAF-2121) Add Support For Displaying Gogo Commands in Karaf Shell Help
[ https://issues.apache.org/jira/browse/KARAF-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2121: Fix Version/s: (was: 3.0.0) 3.0.1 > Add Support For Displaying Gogo Commands in Karaf Shell Help > > > Key: KARAF-2121 > URL: https://issues.apache.org/jira/browse/KARAF-2121 > Project: Karaf > Issue Type: New Feature > Components: karaf-shell >Affects Versions: 2.3.0 >Reporter: Gareth Collins >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 2.4.0, 3.0.1, 2.3.4 > > Attachments: KARAF-2121.patch > > > Discussion on this originated in this thread: > http://karaf.922171.n3.nabble.com/Gogo-vs-Karaf-Commands-td4027219.html > Whist Gogo commands run in Karaf, these commands do not show up in the Karaf > shell help. For Karaf users potentially needing to target multiple > environments, it would be nice if Karaf could also display help for these > Gogo commands. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (KARAF-2191) Karaf 3.0.x CLONE - Karaf startup fails with NullPointerException when logfile can't be written
[ https://issues.apache.org/jira/browse/KARAF-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-2191. - Resolution: Fixed > Karaf 3.0.x CLONE - Karaf startup fails with NullPointerException when > logfile can't be written > --- > > Key: KARAF-2191 > URL: https://issues.apache.org/jira/browse/KARAF-2191 > Project: Karaf > Issue Type: Bug > Components: karaf-core >Affects Versions: 2.2.9, 2.3.0, 3.0.0 >Reporter: Jamie goodyear >Assignee: Andreas Pieber >Priority: Minor > Fix For: 2.2.12, 2.4.0, 3.0.0 > > > The karaf startup fails with a NullPointerException when the logifle can't be > accessed: > java.io.FileNotFoundException: /opt/karaf/data/log/karaf.log (Permission > denied) > at java.io.FileOutputStream.openAppend(Native Method) > at java.io.FileOutputStream.(FileOutputStream.java:177) > at > org.apache.karaf.main.BootstrapLogManager$SimpleFileHandler.open(BootstrapLogManager.java:115) > at > org.apache.karaf.main.BootstrapLogManager$SimpleFileHandler.(BootstrapLogManager.java:104) > at > org.apache.karaf.main.BootstrapLogManager.getDefaultHandler(BootstrapLogManager.java:83) > at org.apache.karaf.main.Main.launch(Main.java:234) > at org.apache.karaf.main.Main.main(Main.java:429) > Could not create framework: java.lang.NullPointerException > java.lang.NullPointerException > at java.util.logging.Logger.addHandler(Logger.java:1185) > at org.apache.karaf.main.Main.launch(Main.java:234) > at org.apache.karaf.main.Main.main(Main.java:429) > This should be changed to: Output a meaningfull message e.g. "Karaf can't > startup, make sure the logifle can be accessed and written by the user > starting Karaf", > OR > try to allocate a logfile with a different name. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Assigned] (KARAF-1253) No completion on some commands with scope *
[ https://issues.apache.org/jira/browse/KARAF-1253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned KARAF-1253: --- Assignee: Jean-Baptiste Onofré > No completion on some commands with scope * > --- > > Key: KARAF-1253 > URL: https://issues.apache.org/jira/browse/KARAF-1253 > Project: Karaf > Issue Type: Bug > Components: karaf-shell >Affects Versions: 3.0.0 >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 3.0.0 > > > Some commands are not considered by the default completers set. > For instance, we have a help command which doesn't appear in the completer > set. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (KARAF-1701) Parsing of config for a field with cardinality > 1 is incorrectlyprocessed and displayed on Admin Console
[
https://issues.apache.org/jira/browse/KARAF-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-1701:
Fix Version/s: (was: 3.0.0)
3.0.1
> Parsing of config for a field with cardinality > 1 is incorrectlyprocessed
> and displayed on Admin Console
> -
>
> Key: KARAF-1701
> URL: https://issues.apache.org/jira/browse/KARAF-1701
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
>Affects Versions: 2.2.7
> Environment: Windows 7
>Reporter: Hugh Rodgers
> Fix For: 2.2.12, 2.4.0, 3.0.1, 2.3.4
>
> Attachments: DDF_Custom_Mime_Type_Resolver.png
>
>
> I have a feature where the configuration is embedded in it like follows:
>description=Custom MimeTypes Resolver.">
>start-level='75'>mvn:ddf.mime/custom-mime-type-resolver/1.0
>
> name = NITF Content Resolver
> priority = 10
> customMimeTypes = nitf=image/nitf,ntf=image/nitf
>
>
> The bundle in this feature has a metatype XML file describing the Admin
> Console interface to configure it. This metatype XML includes an attribute
> with a cardinality="100", hence a text field will be displayed on the console
> with +/- buttons to add extra text fields for more values up to a max of 100.
> http://www.osgi.org/xmlns/metatype/v1.0.0";>
>id="DDF_Custom_Mime_Type_Resolver">
>
>type="String" />
>
>type="Integer" />
>
> required="true"
> type="String" cardinality="100"
> description="List of key/value pairs where key is the file extension
> and value is the mime type, e.g., nitf=image/nitf"/>
>
>factoryPid="DDF_Custom_Mime_Type_Resolver">
>
>
>
>
> When karaf comes up and instantiates the bundle in this feature and applies
> the configuration (thus creating an instance of the
> DDF_Custom_Mime_Type_Resolver managed service factory), the customMimeTypes
> are displayed in one field as nitf=image/nitf,ntf=image/nitf rather than 2
> separate fields with their values delimited by the comma as I had hoped.
> However, the setCustomMimeTypes(String[] mimeTypes) method in the managed
> service instance is called with a String[] as expected.
> But if I add another mime type mapping via the Admin Console, say
> xyz=image/xyz, when the setCustomMimeTypes(String[]) method is called it no
> longer trats the "," as a delimiter for the "nitf=image/nitf,ntf=image/nitf"
> entry and treats this as a single mime type mapping.
> Here is a log trace of what happens:
> For:
>
> name = NITF Content Resolver
> priority = 10
> customMimeTypes = nitf=image/nitf,ntf=image/nitf
>
> Get:
> ENTERING: setCustomMimeTypes
> nitf=image/nitf
> Creating fileExtensions array for mime type: image/nitf
> Adding file extension: nitf for mime type: image/nitf
> ntf=image/nitf
> Adding file extension: ntf for mime type: image/nitf
> customFileExtensionsToMimeTypesMap = {nitf=image/nitf, ntf=image/nitf}
> customMimeTypesToFileExtensionsMap = {image/nitf=[nitf, ntf]}
> EXITING: setCustomMimeTypes
> Add a new mime type xyz=image/xyz via Admin Console:
> ENTERING: setCustomMimeTypes
> nitf=image/nitf,ntf=image/nitf
> Creating fileExtensions array for mime type: image/nitf,ntf
> Adding file extension: nitf for mime type: image/nitf,ntf
> xyz=image/xyz
> Creating fileExtensions array for mime type: image/xyz
> Adding file extension: xyz for mime type: image/xyz
> customFileExtensionsToMimeTypesMap = {nitf=image/nitf,ntf, xyz=image/xyz}
> customMimeTypesToFileExtensionsMap = {image/xyz=[xyz], image/nitf,ntf=[nitf]}
> EXITING: setCustomMimeTypes
> If I cut/paste the ntf=image/nitf from the entry with
> "nitf=image/nitf,ntf=image/nitf"
> into its own text field (by hitting "+" button) I get (which is correct):
> ENTERING: setCustomMimeTypes
> nitf=image/nitf
> Creating fileExtensions array for mime type: image/nitf
> Adding file extension: nitf for mime type: image/nitf
> xyz=image/xyz
> Creating fileExtensions array for mime type: image/xyz
> Adding file extension: xyz for mime type: image/xyz
> ntf=image/nitf
> Adding file extension: ntf for mime type: image/nitf
> customFileExtensionsToMimeTypesMap = {nitf=image/nitf, ntf=image/nitf,
> xyz=image/xyz}
> customMimeTypesToFileExtensionsMap = {image/nitf=[nitf, ntf], image/xyz=[xyz]}
> EXITING: setCustomMimeTypes
> Tried this variation on the in the feature but it did not work:
>
> name = NITF Content Resolver
> priority = 10
> customMimeTypes = nitf=image/nitf
>
[jira] [Assigned] (KARAF-711) Add documentation how to update Karaf
[ https://issues.apache.org/jira/browse/KARAF-711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned KARAF-711: -- Assignee: Jean-Baptiste Onofré > Add documentation how to update Karaf > - > > Key: KARAF-711 > URL: https://issues.apache.org/jira/browse/KARAF-711 > Project: Karaf > Issue Type: Improvement > Components: karaf-documentation >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 3.0.0 > > > For the users having an existing Karaf version, it could be helpful to > provide a documentation section how to update to a new Karaf version. > For instance, I have Karaf 2.2.0 running and I would like to update to 2.2.2: > what's the step to update, which folders have to be updated, etc. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (KARAF-1560) config:update throws ClassCastException when used on a Configuration with boolean fields created in the web console
[ https://issues.apache.org/jira/browse/KARAF-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-1560: Fix Version/s: (was: 3.0.0) 3.0.1 > config:update throws ClassCastException when used on a Configuration with > boolean fields created in the web console > --- > > Key: KARAF-1560 > URL: https://issues.apache.org/jira/browse/KARAF-1560 > Project: Karaf > Issue Type: Bug > Components: karaf-config >Affects Versions: 2.2.5 >Reporter: Hugh Rodgers >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 2.2.12, 2.4.0, 3.0.1, 2.3.4 > > Attachments: demo_validation.png, karaf_config_propset.png, > karaf_log.png, metatype.xml > > > I am using Karaf v2.2.5 on Windows 7. I start Karaf (using the karaf.bat > script) and create a configuration that has one or more fields that are > checkboxes (i.e., Boolean). > I then go to the Karaf command line console and issue the following > commands: > config:edit > config:propset true > config:update > When I submit the config"update command I get this exception: > 09:52:19,658 | INFO | l Console Thread | Console | > araf.shell.console.jline.Console 242 | 14 - org.apache.karaf.shell.console > - 2.2.5 | Exception caught while executing command > java.lang.ClassCastException: java.lang.Boolean cannot be cast to > java.lang.String >at > org.apache.karaf.shell.config.ConfigCommandSupport.persistConfiguration(ConfigCommandSupport.java:161)[41:org.apache.karaf.shell.config:2.2.5] >at > org.apache.karaf.shell.config.ConfigCommandSupport.update(ConfigCommandSupport.java:129)[41:org.apache.karaf.shell.config:2.2.5] >at > org.apache.karaf.shell.config.UpdateCommand.doExecute(UpdateCommand.java:38)[41:org.apache.karaf.shell.config:2.2.5] >at > org.apache.karaf.shell.config.ConfigCommandSupport.doExecute(ConfigCommandSupport.java:63)[41:org.apache.karaf.shell.config:2.2.5] >at > org.apache.karaf.shell.console.OsgiCommandSupport.execute(OsgiCommandSupport.java:38)[14:org.apache.karaf.shell.console:2.2.5] >at > org.apache.felix.gogo.commands.basic.AbstractCommand.execute(AbstractCommand.java:35)[14:org.apache.karaf.shell.console:2.2.5] >at > org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:78)[14:org.apache.karaf.shell.console:2.2.5] >at > org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:474)[14:org.apache.karaf.shell.console:2.2.5] >at > org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:400)[14:org.apache.karaf.shell.console:2.2.5] >at > org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)[14:org.apache.karaf.shell.console:2.2.5] >at > org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)[14:org.apache.karaf.shell.console:2.2.5] >at > org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)[14:org.apache.karaf.shell.console:2.2.5] >at > org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89)[14:org.apache.karaf.shell.console:2.2.5] >at > org.apache.karaf.shell.console.jline.Console.run(Console.java:221)[14:org.apache.karaf.shell.console:2.2.5] >at java.lang.Thread.run(Thread.java:662)[:1.6.0_29] > And the configuration is not saved. > Configuration completely created/updated in the Admin Console work fine. > Likewise, configurations completely created in the command line console work > fine. The issue arises only with boolean fields and what mechanism is used > to initially create the configuration. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (KARAF-2289) AJAX Error when editing some configurations in webconsole
[
https://issues.apache.org/jira/browse/KARAF-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-2289:
Fix Version/s: (was: 3.0.0)
3.0.1
> AJAX Error when editing some configurations in webconsole
> -
>
> Key: KARAF-2289
> URL: https://issues.apache.org/jira/browse/KARAF-2289
> Project: Karaf
> Issue Type: Bug
> Components: webconsole
>Affects Versions: 2.3.1
> Environment: Windows 7 Pro x64
>Reporter: Jeff Clark
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: 2.4.0, 3.0.1, 2.3.4
>
>
> I was working through Christian Schneider's Karaf tutorial #3
> (http://www.liquid-reality.de/display/liquid/2011/09/26/Karaf+Tutorial+Part+3+-+Improving+configuration+editing+using+the+OSGI+Metatype+Service+and+the+Felix+Webconsole).
> After presenting my findings to Christian, he believes this is a bug in the
> webconsole for this version of Karaf, and asked me if I could open an issue
> here.
> The problem is that after building his ConfigAdmin project & installing in
> Karaf, if you attempt to edit that project's configuration (ConfigApp.cfg)
> file through the webconsole, the following error is raised:
> AJAX Error
> The request failed:
> {"PID":"ConfigAdmin"
> If I uninstall the configapp & configapp-blueprint features, I can then edit
> the remaining ConfigApp.cfg file through the webconsole, receiving the
> message that the form was automatically generated because no property
> descriptors are available (which makes sense because I uninstalled the
> associated features).
> His tutorial references Karaf 2.2.4 which did not have this problem, and he
> has tested in 3.0.0.RC1 without seeing this problem. 2.3.1 however seems to
> have this issue.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (KARAF-2366) Cannot Update Factory Configuration Not Backed By A File With The "config:" Command
[ https://issues.apache.org/jira/browse/KARAF-2366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2366: Fix Version/s: (was: 3.0.0) 3.0.1 > Cannot Update Factory Configuration Not Backed By A File With The "config:" > Command > --- > > Key: KARAF-2366 > URL: https://issues.apache.org/jira/browse/KARAF-2366 > Project: Karaf > Issue Type: Bug > Components: karaf-config >Affects Versions: 2.3.1 >Reporter: Gareth Collins >Assignee: Jean-Baptiste Onofré > Fix For: 2.4.0, 3.0.1, 2.3.4 > > > This is related to this thread in the mailing list: > http://karaf.922171.n3.nabble.com/Updating-Managed-Service-Factory-Config-Via-quot-config-quot-commands-td4028322.html#a4028325 > In summary, it does not appear to be possible to update a factory > configuration not backed by a file (e.g. one created via a karaf feature > file). > If I have a configuration like this: > Pid:com.mycompany.myservice.327d4cd4-4704-4190-9e51-26f5f0b91435 > FactoryPid: com.mycompany.myservice > BundleLocation: mvn:com.mycompany/mycompany/1.0.0-SNAPSHOT > Properties: >myservice.host = 0.0.0.0 >myservice.port = 8080 >org.apache.karaf.features.configKey = com.mycompany.myservice-healthcheck >service.factoryPid = com.mycompany.myservice >service.pid = com.mycompany.myservice.327d4cd4-4704-4190-9e51-26f5f0b91435 > and try to edit the configuration. e.g.: > config:edit com.mycompany.myservice-healthcheck > config:propset myservice.port = 8081 > config:update > I get a new config: > Pid:com.mycompany.myservice.8cbfea87-f66e-44b4-b94a-11fdb14c235f > FactoryPid: com.mycompany.myservice > BundleLocation: > mvn:com.antennasoftware/gravity.clientAP.blueprint/1.0.0-SNAPSHOT > Properties: >service.pid = com.mycompany.myservice.8cbfea87-f66e-44b4-b94a-11fdb14c235f >myservice.port = 8081 >service.factoryPid = com.mycompany.myservice >felix.fileinstall.filename = > file:/home/karaf/apache-karaf-2.3.1/etc/com.mycompany.myservice-healthcheck.cfg > > If I go and specify the pid exactly: > > config:edit com.mycompany.myservice.327d4cd4-4704-4190-9e51-26f5f0b91435 > > config:propset myservice.port 8081 > > config:update > Nothing happens. > If I try the "-f" option (which I understand should create a file) I get a > NullPointerException: > 2013-03-26 21:10:08,231 | INFO | []:[] | Thread-8220 | Console > | araf.shell.console.jline.Console 198 | 14 - > org.apache.karaf.shell.console - 2.3.1 | Exception caught while executing > command > java.lang.NullPointerException > at > org.apache.karaf.shell.config.ConfigCommandSupport.findConfigurationByFileName(ConfigCommandSupport.java:115) > > at > org.apache.karaf.shell.config.EditCommand.doExecute(EditCommand.java:50) > at > org.apache.karaf.shell.config.ConfigCommandSupport.doExecute(ConfigCommandSupport.java:68) > > at > org.apache.karaf.shell.console.OsgiCommandSupport.execute(OsgiCommandSupport.java:38) > > at > org.apache.felix.gogo.commands.basic.AbstractCommand.execute(AbstractCommand.java:35) > > at > org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:78) > at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:474) > at > org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:400) > at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108) > at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183) > at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120) > at > org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89) > > at org.apache.karaf.shell.console.jline.Console.run(Console.java:174) > at java.lang.Thread.run(Unknown Source)[:1.7.0_05] > at > org.apache.karaf.shell.ssh.ShellFactoryImpl$ShellImpl$4.doRun(ShellFactoryImpl.java:144)[28:org.apache.karaf.shell.ssh:2.3.1] > > at > org.apache.karaf.shell.ssh.ShellFactoryImpl$ShellImpl$4$1.run(ShellFactoryImpl.java:135) > > at java.security.AccessController.doPrivileged(Native > Method)[:1.7.0_05] > at javax.security.auth.Subject.doAs(Unknown Source)[:1.7.0_05] > at > org.apache.karaf.shell.ssh.ShellFactoryImpl$ShellImpl$4.run(ShellFactoryImpl.java:133)[28:org.apache.karaf.shell.ssh:2.3.1] > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (KARAF-2390) Fix namespace handlers provided service header
[ https://issues.apache.org/jira/browse/KARAF-2390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2390: Fix Version/s: (was: 3.0.0) 3.0.1 > Fix namespace handlers provided service header > -- > > Key: KARAF-2390 > URL: https://issues.apache.org/jira/browse/KARAF-2390 > Project: Karaf > Issue Type: Bug >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > Fix For: 2.4.0, 3.0.1, 2.3.4 > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (KARAF-2315) The check for jvm.dll happens to early in the bat file
[ https://issues.apache.org/jira/browse/KARAF-2315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2315: Fix Version/s: (was: 3.0.0) 3.0.1 > The check for jvm.dll happens to early in the bat file > -- > > Key: KARAF-2315 > URL: https://issues.apache.org/jira/browse/KARAF-2315 > Project: Karaf > Issue Type: Bug >Affects Versions: 2.3.2, 2.4.0, 3.0.0 >Reporter: Heath Kesler >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 2.4.0, 3.0.1, 2.3.4 > > > When running karaf without JAVA_HOME set, but having the JDK installed > returns the following warning: > WARNING: Running karaf on a Java HotSpot Client VM because server-mode is not > av > ailable. > Install Java Developer Kit to fix this. > For more details see > http://java.sun.com/products/hotspot/whitepaper.html#client > But since the JDK is installed and found via a reg query, karaf will still > startup. I think this check should be moved to after the JAVA_HOME > validation is done to avoid this warning. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (KARAF-2295) features deployer is useless for dynamic updates
[ https://issues.apache.org/jira/browse/KARAF-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2295: Fix Version/s: 3.0.1 > features deployer is useless for dynamic updates > > > Key: KARAF-2295 > URL: https://issues.apache.org/jira/browse/KARAF-2295 > Project: Karaf > Issue Type: Bug > Components: karaf-feature >Affects Versions: 3.0.0.RC1 >Reporter: Andrei Pozolotin >Assignee: Jean-Baptiste Onofré > Fix For: 3.0.1 > > > use cases which do not work: > suppose old and new repository contain overlapping set of bundles. > 1) same name, new version: > a) install > * drop repo-1.0-features.xml > b) update > * kill repo-1.0-features.xml > * drop repo-1.1-features.xml > 2) same name, no version: > a) install > * drop repo-features.xml > b) update > * drop repo-features.xml > result: total corruption of repository, feature, bundle install state > workaround: clean bundle cache, restart karaf. > description why it does not work: > https://github.com/barchart/barchart-service/wiki/Features-Problems > re-implementation of features deployer > https://github.com/barchart/barchart-karaf-deployer-features -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (KARAF-2391) Add generic capabilities provided by the framework
[ https://issues.apache.org/jira/browse/KARAF-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2391: Fix Version/s: (was: 3.0.0) 3.0.1 > Add generic capabilities provided by the framework > -- > > Key: KARAF-2391 > URL: https://issues.apache.org/jira/browse/KARAF-2391 > Project: Karaf > Issue Type: Bug >Affects Versions: 2.3.2 >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > Fix For: 2.4.0, 3.0.1, 2.3.4 > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (KARAF-2313) The feature:list command does not support multiple versions of the same feature
[ https://issues.apache.org/jira/browse/KARAF-2313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2313: Fix Version/s: (was: 3.0.0) 3.0.1 > The feature:list command does not support multiple versions of the same > feature > --- > > Key: KARAF-2313 > URL: https://issues.apache.org/jira/browse/KARAF-2313 > Project: Karaf > Issue Type: Bug > Components: karaf-shell >Affects Versions: 3.0.0.RC1 >Reporter: Frank Lyaruu >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 2.4.0, 3.0.1, 2.3.4 > > > When updating a feature to a new version, I can add the new feature > repository. > After that there are multiple versions of some of the features. The web > console shows them properly, but the feature:list command always shows only > the latest. > In that situation there _is_ an older installed version of the feature which > is pretty much invisible in the shell. I think that isn't the desired > behavior, I suggest that all versions of all features are shown. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (KARAF-2367) Config Not Released When Declarative Services Bundle Stopped
[ https://issues.apache.org/jira/browse/KARAF-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2367: Fix Version/s: (was: 3.0.0) 3.0.1 > Config Not Released When Declarative Services Bundle Stopped > > > Key: KARAF-2367 > URL: https://issues.apache.org/jira/browse/KARAF-2367 > Project: Karaf > Issue Type: Bug > Components: karaf-config >Affects Versions: 2.3.1 >Reporter: Gareth Collins >Assignee: Jean-Baptiste Onofré > Fix For: 2.4.0, 3.0.1, 2.3.4 > > > If I have a declarative services bundle which has config associated with it. > i.e.: > karaf@root> list -t 0 -s | grep myservice > [ 234] [Active ] [] [ 80] com.mycompany.myservice > (1.0.0.20130530-jenkins-383) > karaf@root> config:list "(service.pid=com.mycompany.myservice)" > > Pid:com.mycompany.myservice > BundleLocation: mvn:com.mycompany/myservice/1.0.0-SNAPSHOT > Properties: > . > . > If I stop or uninstall this bundle, the config does not get released: > karaf@root> stop 234 > karaf@root> config:list "(service.pid=com.mycompany.myservice)" > > Pid:com.mycompany.myservice > BundleLocation: mvn:com.mycompany/myservice/1.0.0-SNAPSHOT > Properties: > . > . > This is problematic because it stops you from uninstalling the bundle and > installing a new bundle at a new location which will reuse the config. To get > around this issue I currently must delete the old config and recreate it. > This problem persists across karaf restarts. > I know I can also do this: > karaf@root> update 234 > But that doesn't always work (once I can reproduce this "update" failure > consistently, I will open another defect) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (KARAF-2295) features deployer is useless for dynamic updates
[ https://issues.apache.org/jira/browse/KARAF-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2295: Fix Version/s: (was: 3.0.0) > features deployer is useless for dynamic updates > > > Key: KARAF-2295 > URL: https://issues.apache.org/jira/browse/KARAF-2295 > Project: Karaf > Issue Type: Bug > Components: karaf-feature >Affects Versions: 3.0.0.RC1 >Reporter: Andrei Pozolotin >Assignee: Jean-Baptiste Onofré > Fix For: 3.0.1 > > > use cases which do not work: > suppose old and new repository contain overlapping set of bundles. > 1) same name, new version: > a) install > * drop repo-1.0-features.xml > b) update > * kill repo-1.0-features.xml > * drop repo-1.1-features.xml > 2) same name, no version: > a) install > * drop repo-features.xml > b) update > * drop repo-features.xml > result: total corruption of repository, feature, bundle install state > workaround: clean bundle cache, restart karaf. > description why it does not work: > https://github.com/barchart/barchart-service/wiki/Features-Problems > re-implementation of features deployer > https://github.com/barchart/barchart-karaf-deployer-features -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (KARAF-2392) Remove unneeded manifest headers, add service import definitions for blueprint namespaces
[ https://issues.apache.org/jira/browse/KARAF-2392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2392: Fix Version/s: (was: 3.0.0) 3.0.1 > Remove unneeded manifest headers, add service import definitions for > blueprint namespaces > - > > Key: KARAF-2392 > URL: https://issues.apache.org/jira/browse/KARAF-2392 > Project: Karaf > Issue Type: Bug >Affects Versions: 2.3.2 >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > Fix For: 2.4.0, 3.0.1, 2.3.4 > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (KARAF-2458) Update to Spring 3.2.5.RELEASE
[ https://issues.apache.org/jira/browse/KARAF-2458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2458: Summary: Update to Spring 3.2.5.RELEASE (was: Update to Spring 3.2.4.RELEASE) > Update to Spring 3.2.5.RELEASE > -- > > Key: KARAF-2458 > URL: https://issues.apache.org/jira/browse/KARAF-2458 > Project: Karaf > Issue Type: Bug >Affects Versions: 2.3.2 >Reporter: Jonathan Anstey >Assignee: Jean-Baptiste Onofré > Fix For: 2.3.3, 2.4.0, 3.0.0 > > > A new release of Spring 3.2 is available. Karaf should be updated to this new > release. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (KARAF-2513) management boot can not process MBean without implement DynamicMBean interface
[ https://issues.apache.org/jira/browse/KARAF-2513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2513: Fix Version/s: (was: 3.0.0) 3.0.1 > management boot can not process MBean without implement DynamicMBean interface > -- > > Key: KARAF-2513 > URL: https://issues.apache.org/jira/browse/KARAF-2513 > Project: Karaf > Issue Type: Bug > Components: karaf-core >Affects Versions: 3.0.0 >Reporter: ChengRen >Assignee: Jean-Baptiste Onofré > Fix For: 3.0.1 > > > jvm 1| Caused by: java.lang.reflect.UndeclaredThrowableException > jvm 1| at com.sun.proxy.$Proxy0.registerMBean(Unknown Source) > jvm 1| at > org.apache.camel.management.DefaultManagementAgent.registerMBeanWithServer(DefaultManagementAgent. > a:329) > jvm 1| at > org.apache.camel.management.DefaultManagementAgent.register(DefaultManagementAgent.java:226) > jvm 1| at > org.apache.camel.management.DefaultManagementAgent.register(DefaultManagementAgent.java:221) > jvm 1| at > org.apache.camel.management.ManagedManagementStrategy.manageNamedObject(ManagedManagementStrategy. > a:76) > jvm 1| at > org.apache.camel.management.ManagedManagementStrategy.manageObject(ManagedManagementStrategy.java: > jvm 1| at > org.apache.camel.management.DefaultManagementLifecycleStrategy.manageObject(DefaultManagementLifec > eStrategy.java:784) > jvm 1| at > org.apache.camel.management.DefaultManagementLifecycleStrategy.onContextStart(DefaultManagementLif > cleStrategy.java:182) > jvm 1| ... 92 more > jvm 1| Caused by: java.lang.reflect.InvocationTargetException > jvm 1| at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) > jvm 1| at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > jvm 1| at java.lang.reflect.Method.invoke(Method.java:606) > jvm 1| at > org.apache.karaf.management.boot.KarafMBeanServerBuilder$MBeanInvocationHandler.invoke(KarafMBeanS > erBuilder.java:63) > jvm 1| ... 100 more > jvm 1| Caused by: javax.management.NotCompliantMBeanException: MBean > class org.apache.camel.management.mbean.Mana > CamelContext does not implement DynamicMBean, and neither follows the > Standard MBean conventions (javax.management.No > mpliantMBeanException: Class > org.apache.camel.management.mbean.ManagedCamelContext is not a JMX compliant > Standard MB > ) nor the MXBean conventions (javax.management.NotCompliantMBeanException: > org.apache.camel.management.mbean.ManagedC > lContext: Class org.apache.camel.management.mbean.ManagedCamelContext is not > a JMX compliant MXBean) > jvm 1| at > com.sun.jmx.mbeanserver.Introspector.checkCompliance(Introspector.java:173) > jvm 1| at > com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor. > a:317) > jvm 1| at > com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522) > jvm 1| ... 104 more -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (KARAF-2513) management boot can not process MBean without implement DynamicMBean interface
[ https://issues.apache.org/jira/browse/KARAF-2513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13817246#comment-13817246 ] Jean-Baptiste Onofré commented on KARAF-2513: - I disabled the ACL support by default for Karaf 3.0.0 (you can use KARAF_ACL=true env variable to enable it). > management boot can not process MBean without implement DynamicMBean interface > -- > > Key: KARAF-2513 > URL: https://issues.apache.org/jira/browse/KARAF-2513 > Project: Karaf > Issue Type: Bug > Components: karaf-core >Affects Versions: 3.0.0 >Reporter: ChengRen >Assignee: Jean-Baptiste Onofré > Fix For: 3.0.1 > > > jvm 1| Caused by: java.lang.reflect.UndeclaredThrowableException > jvm 1| at com.sun.proxy.$Proxy0.registerMBean(Unknown Source) > jvm 1| at > org.apache.camel.management.DefaultManagementAgent.registerMBeanWithServer(DefaultManagementAgent. > a:329) > jvm 1| at > org.apache.camel.management.DefaultManagementAgent.register(DefaultManagementAgent.java:226) > jvm 1| at > org.apache.camel.management.DefaultManagementAgent.register(DefaultManagementAgent.java:221) > jvm 1| at > org.apache.camel.management.ManagedManagementStrategy.manageNamedObject(ManagedManagementStrategy. > a:76) > jvm 1| at > org.apache.camel.management.ManagedManagementStrategy.manageObject(ManagedManagementStrategy.java: > jvm 1| at > org.apache.camel.management.DefaultManagementLifecycleStrategy.manageObject(DefaultManagementLifec > eStrategy.java:784) > jvm 1| at > org.apache.camel.management.DefaultManagementLifecycleStrategy.onContextStart(DefaultManagementLif > cleStrategy.java:182) > jvm 1| ... 92 more > jvm 1| Caused by: java.lang.reflect.InvocationTargetException > jvm 1| at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) > jvm 1| at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > jvm 1| at java.lang.reflect.Method.invoke(Method.java:606) > jvm 1| at > org.apache.karaf.management.boot.KarafMBeanServerBuilder$MBeanInvocationHandler.invoke(KarafMBeanS > erBuilder.java:63) > jvm 1| ... 100 more > jvm 1| Caused by: javax.management.NotCompliantMBeanException: MBean > class org.apache.camel.management.mbean.Mana > CamelContext does not implement DynamicMBean, and neither follows the > Standard MBean conventions (javax.management.No > mpliantMBeanException: Class > org.apache.camel.management.mbean.ManagedCamelContext is not a JMX compliant > Standard MB > ) nor the MXBean conventions (javax.management.NotCompliantMBeanException: > org.apache.camel.management.mbean.ManagedC > lContext: Class org.apache.camel.management.mbean.ManagedCamelContext is not > a JMX compliant MXBean) > jvm 1| at > com.sun.jmx.mbeanserver.Introspector.checkCompliance(Introspector.java:173) > jvm 1| at > com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor. > a:317) > jvm 1| at > com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522) > jvm 1| ... 104 more -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (KARAF-1287) Check documentation consistent
[ https://issues.apache.org/jira/browse/KARAF-1287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-1287. - Resolution: Duplicate > Check documentation consistent > -- > > Key: KARAF-1287 > URL: https://issues.apache.org/jira/browse/KARAF-1287 > Project: Karaf > Issue Type: Bug > Components: karaf-documentation >Affects Versions: 3.0.0 >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Blocker > Fix For: 3.0.0 > > > On trunk (Karaf 3.0.0), we made a bunch of refactoring and new features (in > the core, in the commands, etc). > I'm not sure that we updated the documentation, and so, the documentation is > sync. > The purpose of this Jira is to check the documentation content, in regards of > the new features, commands, etc. > The "screenshot" should be checked as well. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (KARAF-2511) Review and update documentation for Karaf 3.0.0
[ https://issues.apache.org/jira/browse/KARAF-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2511: Priority: Blocker (was: Major) > Review and update documentation for Karaf 3.0.0 > --- > > Key: KARAF-2511 > URL: https://issues.apache.org/jira/browse/KARAF-2511 > Project: Karaf > Issue Type: Task > Components: karaf-documentation >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Blocker > Fix For: 3.0.0 > > > The documentation (manual) should be reviewed: > - The subshell part should be described (usage and configuration). > - The "code samples"/screenshots have to be updated with Karaf 3.0.0 use cases > - a global polishing, double read -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Work started] (KARAF-2511) Review and update documentation for Karaf 3.0.0
[ https://issues.apache.org/jira/browse/KARAF-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KARAF-2511 started by Jean-Baptiste Onofré. > Review and update documentation for Karaf 3.0.0 > --- > > Key: KARAF-2511 > URL: https://issues.apache.org/jira/browse/KARAF-2511 > Project: Karaf > Issue Type: Task > Components: karaf-documentation >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Blocker > Fix For: 3.0.0 > > > The documentation (manual) should be reviewed: > - The subshell part should be described (usage and configuration). > - The "code samples"/screenshots have to be updated with Karaf 3.0.0 use cases > - a global polishing, double read -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (KARAF-2506) MBeans attributes are "unavailable"
[ https://issues.apache.org/jira/browse/KARAF-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13817144#comment-13817144 ] Jean-Baptiste Onofré commented on KARAF-2506: - I introduced KARAF_ACL environment variable to easily enable the ACL support. Now, by default the ACL support is disabled, the users have to set KARAF_ACL=true. > MBeans attributes are "unavailable" > --- > > Key: KARAF-2506 > URL: https://issues.apache.org/jira/browse/KARAF-2506 > Project: Karaf > Issue Type: Bug > Components: karaf-core >Affects Versions: 3.0.0 >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Blocker > Fix For: 3.0.0 > > > Running Karaf 3.0.0-SNAPSHOT (trunk), and connecting jconsole, all Karaf > MBeans attributes are displayed as "unavailable" in red. > It's the case for: > - bundles in org.apache.karaf:type=bundle > - configs in org.apache.karaf:type=config > - features and repositories in org.apache.karaf:type=feature > - instances in org.apache.karaf:type=instances > - kars in org.apache.karaf:type=kar > - level in org.apache.karaf:type=log > - exports and imports in org.apache.karaf:type=package > - services in org.apache.karaf:type=service > - all attributes in org.apache.karaf:type=system > I'm checking if it's not some ACLs missing (as the JMX ACL check attributes > using some operations name like get/set/is). -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (KARAF-2506) MBeans attributes are "unavailable"
[ https://issues.apache.org/jira/browse/KARAF-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2506: Fix Version/s: (was: 3.0.0) 3.0.1 > MBeans attributes are "unavailable" > --- > > Key: KARAF-2506 > URL: https://issues.apache.org/jira/browse/KARAF-2506 > Project: Karaf > Issue Type: Bug > Components: karaf-core >Affects Versions: 3.0.0 >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Blocker > Fix For: 3.0.1 > > > Running Karaf 3.0.0-SNAPSHOT (trunk), and connecting jconsole, all Karaf > MBeans attributes are displayed as "unavailable" in red. > It's the case for: > - bundles in org.apache.karaf:type=bundle > - configs in org.apache.karaf:type=config > - features and repositories in org.apache.karaf:type=feature > - instances in org.apache.karaf:type=instances > - kars in org.apache.karaf:type=kar > - level in org.apache.karaf:type=log > - exports and imports in org.apache.karaf:type=package > - services in org.apache.karaf:type=service > - all attributes in org.apache.karaf:type=system > I'm checking if it's not some ACLs missing (as the JMX ACL check attributes > using some operations name like get/set/is). -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (KARAF-2506) MBeans attributes are "unavailable"
[ https://issues.apache.org/jira/browse/KARAF-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2506: Priority: Critical (was: Blocker) > MBeans attributes are "unavailable" > --- > > Key: KARAF-2506 > URL: https://issues.apache.org/jira/browse/KARAF-2506 > Project: Karaf > Issue Type: Bug > Components: karaf-core >Affects Versions: 3.0.0 >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Critical > Fix For: 3.0.1 > > > Running Karaf 3.0.0-SNAPSHOT (trunk), and connecting jconsole, all Karaf > MBeans attributes are displayed as "unavailable" in red. > It's the case for: > - bundles in org.apache.karaf:type=bundle > - configs in org.apache.karaf:type=config > - features and repositories in org.apache.karaf:type=feature > - instances in org.apache.karaf:type=instances > - kars in org.apache.karaf:type=kar > - level in org.apache.karaf:type=log > - exports and imports in org.apache.karaf:type=package > - services in org.apache.karaf:type=service > - all attributes in org.apache.karaf:type=system > I'm checking if it's not some ACLs missing (as the JMX ACL check attributes > using some operations name like get/set/is). -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (KARAF-2552) Running log:tail on admin:console causes full CPU usage.
[ https://issues.apache.org/jira/browse/KARAF-2552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13817141#comment-13817141 ] Jean-Baptiste Onofré commented on KARAF-2552: - It's probably linked to the new thread created in log:tail to avoid to be interfered with other key binding. > Running log:tail on admin:console causes full CPU usage. > > > Key: KARAF-2552 > URL: https://issues.apache.org/jira/browse/KARAF-2552 > Project: Karaf > Issue Type: Bug > Components: karaf-shell >Affects Versions: 2.3.3 > Environment: Mac OS X on java version "1.7.0_45" and java version > "1.6.0_65" > Windows 7 on java version "1.6.0_41" >Reporter: Mateo Ramey > > Running log:tail on the admin console causes 100% cpu usage. There were no > logs being shown during the tail, just simply running the tail is causing the > CPU to spike up. > Steps to reproduce: > 1) Download Karaf 2.3.3 distribution. > 2) Start karaf > 3) run log:tail command > 4) Watch CPU monitor (top in *nix or task manager in windows) show full cpu > usage > 5) ctrl-c out of log:tail and CPU usage goes back to idle. > Attaching a profiler to Karaf identified the method taking up CPU as: > org.apache.karaf.shell.console.jline.DelayedStarted.run() > Not sure if that is fully accurate, but might be a place to start. > Note: Was unable to reproduce issue on Karaf 2.3.2 and as a result we have > had to revert back to that version. > Let me know if you have any additional questions. > Thanks! -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (KARAF-1287) Check documentation consistent
[ https://issues.apache.org/jira/browse/KARAF-1287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-1287: Priority: Blocker (was: Major) > Check documentation consistent > -- > > Key: KARAF-1287 > URL: https://issues.apache.org/jira/browse/KARAF-1287 > Project: Karaf > Issue Type: Bug > Components: karaf-documentation >Affects Versions: 3.0.0 >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Blocker > Fix For: 3.0.0 > > > On trunk (Karaf 3.0.0), we made a bunch of refactoring and new features (in > the core, in the commands, etc). > I'm not sure that we updated the documentation, and so, the documentation is > sync. > The purpose of this Jira is to check the documentation content, in regards of > the new features, commands, etc. > The "screenshot" should be checked as well. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Reopened] (KARAF-1287) Check documentation consistent
[ https://issues.apache.org/jira/browse/KARAF-1287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reopened KARAF-1287: - Assignee: Jean-Baptiste Onofré (was: Christian Schneider) > Check documentation consistent > -- > > Key: KARAF-1287 > URL: https://issues.apache.org/jira/browse/KARAF-1287 > Project: Karaf > Issue Type: Bug > Components: karaf-documentation >Affects Versions: 3.0.0 >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 3.0.0 > > > On trunk (Karaf 3.0.0), we made a bunch of refactoring and new features (in > the core, in the commands, etc). > I'm not sure that we updated the documentation, and so, the documentation is > sync. > The purpose of this Jira is to check the documentation content, in regards of > the new features, commands, etc. > The "screenshot" should be checked as well. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (KARAF-1287) Check documentation consistent
[ https://issues.apache.org/jira/browse/KARAF-1287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13817137#comment-13817137 ] Jean-Baptiste Onofré commented on KARAF-1287: - A lot of manual pages should be reviewed and updated to Karaf 3.0.0. I started it and I tackle that. > Check documentation consistent > -- > > Key: KARAF-1287 > URL: https://issues.apache.org/jira/browse/KARAF-1287 > Project: Karaf > Issue Type: Bug > Components: karaf-documentation >Affects Versions: 3.0.0 >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 3.0.0 > > > On trunk (Karaf 3.0.0), we made a bunch of refactoring and new features (in > the core, in the commands, etc). > I'm not sure that we updated the documentation, and so, the documentation is > sync. > The purpose of this Jira is to check the documentation content, in regards of > the new features, commands, etc. > The "screenshot" should be checked as well. -- This message was sent by Atlassian JIRA (v6.1#6144)
