[jira] [Commented] (FELIX-5568) SCR contains compact3 profile code
[
https://issues.apache.org/jira/browse/FELIX-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15936247#comment-15936247
]
Guillaume Nodet commented on FELIX-5568:
Imho, I don't think the problem is about documentation, it's about making sure
the code can run on compact1 profile, which is what the change I suggested
above does. There are tools to check which profile a jar requires, but in this
case, it will report compact3 because of the JMX access. The pom change at
least ensures that all the remaining code is compact1 compliant and gives the
user some confidence.
> SCR contains compact3 profile code
> --
>
> Key: FELIX-5568
> URL: https://issues.apache.org/jira/browse/FELIX-5568
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services (SCR)
>Affects Versions: scr-2.0.8
> Environment: Fedora 25 x64
>Reporter: Ferry Huberts
>Assignee: Carsten Ziegeler
> Fix For: scr-2.1.0
>
>
> {quote}
> $ jdeps -P *.jar |grep compact3
> org.apache.felix.scr-2.0.8.jar ->
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-1.b14.fc25.x86_64/jre/lib/rt.jar
> (compact3)
> -> java.lang.management compact3
> {quote}
> Maybe split off the compact3 part as an optional extension/fragment?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (FELIX-5549) Factory component fails to reactivate after config changes
[ https://issues.apache.org/jira/browse/FELIX-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15936274#comment-15936274 ] Alex Soto commented on FELIX-5549: -- I am sorry I missed the part about the conditions, and there, I think, lies the problem. For me, the configuration _should_ be one of the conditions, same as the references. For example, if I annotate the Worker component with "configurationPolicy = ConfigurationPolicy.REQUIRE", then the Component Factory service is not registered _until_ a configuration is created. Why is this? This behavior makes that the existence of the configuration a necessary condition, perhaps not explicitly listed as such, but in practice it behaves like one. > Factory component fails to reactivate after config changes > -- > > Key: FELIX-5549 > URL: https://issues.apache.org/jira/browse/FELIX-5549 > Project: Felix > Issue Type: Bug > Components: Declarative Services (SCR) > Environment: Karaf 4.0.8 >Reporter: Alex Soto > > A factory component fails to reactive after the configuration changes. > Initially, the component initializes normally. After it is in Active state, > the configuration referenced by the component _configurationPid_ changes, > which causes the component to not activate again. > A minimal application demonstrating this behavior is available here: > https://github.com/lexsoto/blueprint-ds-config-reload -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (FELIX-5549) Factory component fails to reactivate after config changes
[ https://issues.apache.org/jira/browse/FELIX-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15936274#comment-15936274 ] Alex Soto edited comment on FELIX-5549 at 3/22/17 1:18 PM: --- I am sorry I missed the part about the conditions, and there, I think, lies the problem. For me, the configuration _should_ be one of the conditions, same as the references. For example, if I annotate the Worker component with "configurationPolicy = ConfigurationPolicy.REQUIRE", then the Component Factory service is not registered _until_ a configuration is created. Why is this? This behavior makes that the existence of the configuration a necessary condition, perhaps not explicitly listed as such, but in practice it behaves like one. If the existence of the configuration is not one of the conditions, then the Component Factory service should have been registered immediately, but this would not make much sense, since creating instances would result in error. was (Author: alex.soto): I am sorry I missed the part about the conditions, and there, I think, lies the problem. For me, the configuration _should_ be one of the conditions, same as the references. For example, if I annotate the Worker component with "configurationPolicy = ConfigurationPolicy.REQUIRE", then the Component Factory service is not registered _until_ a configuration is created. Why is this? This behavior makes that the existence of the configuration a necessary condition, perhaps not explicitly listed as such, but in practice it behaves like one. > Factory component fails to reactivate after config changes > -- > > Key: FELIX-5549 > URL: https://issues.apache.org/jira/browse/FELIX-5549 > Project: Felix > Issue Type: Bug > Components: Declarative Services (SCR) > Environment: Karaf 4.0.8 >Reporter: Alex Soto > > A factory component fails to reactive after the configuration changes. > Initially, the component initializes normally. After it is in Active state, > the configuration referenced by the component _configurationPid_ changes, > which causes the component to not activate again. > A minimal application demonstrating this behavior is available here: > https://github.com/lexsoto/blueprint-ds-config-reload -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (FELIX-5595) Improve documentation of felix gogo shell
Christian Schneider created FELIX-5595: -- Summary: Improve documentation of felix gogo shell Key: FELIX-5595 URL: https://issues.apache.org/jira/browse/FELIX-5595 Project: Felix Issue Type: Improvement Components: Gogo Shell Reporter: Christian Schneider The current web documentation of the gogo project is very slim. I would like to improve it by describing how to use the shell and some of the basic commands. In a second step I also would like to describe the upcoming feature of adjusting the jline color support. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FELIX-5595) Improve documentation of felix gogo shell
[ https://issues.apache.org/jira/browse/FELIX-5595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider updated FELIX-5595: --- Flags: Patch > Improve documentation of felix gogo shell > - > > Key: FELIX-5595 > URL: https://issues.apache.org/jira/browse/FELIX-5595 > Project: Felix > Issue Type: Improvement > Components: Gogo Shell >Reporter: Christian Schneider > Attachments: FELIX-5595.patch > > > The current web documentation of the gogo project is very slim. > I would like to improve it by describing how to use the shell and some of the > basic commands. > In a second step I also would like to describe the upcoming feature of > adjusting the jline color support. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FELIX-5595) Improve documentation of felix gogo shell
[ https://issues.apache.org/jira/browse/FELIX-5595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider updated FELIX-5595: --- Attachment: FELIX-5595.patch Added a patch with the improved docs > Improve documentation of felix gogo shell > - > > Key: FELIX-5595 > URL: https://issues.apache.org/jira/browse/FELIX-5595 > Project: Felix > Issue Type: Improvement > Components: Gogo Shell >Reporter: Christian Schneider > Attachments: FELIX-5595.patch > > > The current web documentation of the gogo project is very slim. > I would like to improve it by describing how to use the shell and some of the > basic commands. > In a second step I also would like to describe the upcoming feature of > adjusting the jline color support. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (FELIX-5568) SCR contains compact3 profile code
[
https://issues.apache.org/jira/browse/FELIX-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15936358#comment-15936358
]
Carsten Ziegeler commented on FELIX-5568:
-
Well, I think we all inspected the code now and are confident that it runs with
profile1 and doing this in a pom/build time does not help anyone downloading
the final jar. The final jar still tries to use the profile3 code.
I'm not arguing against doing such a check at build time in general, but I
think it does not really help for end users.
> SCR contains compact3 profile code
> --
>
> Key: FELIX-5568
> URL: https://issues.apache.org/jira/browse/FELIX-5568
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services (SCR)
>Affects Versions: scr-2.0.8
> Environment: Fedora 25 x64
>Reporter: Ferry Huberts
>Assignee: Carsten Ziegeler
> Fix For: scr-2.1.0
>
>
> {quote}
> $ jdeps -P *.jar |grep compact3
> org.apache.felix.scr-2.0.8.jar ->
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-1.b14.fc25.x86_64/jre/lib/rt.jar
> (compact3)
> -> java.lang.management compact3
> {quote}
> Maybe split off the compact3 part as an optional extension/fragment?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (FELIX-5593) Specify ARM processor Endianness
[ https://issues.apache.org/jira/browse/FELIX-5593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15936370#comment-15936370 ] ASF GitHub Bot commented on FELIX-5593: --- Github user asfgit closed the pull request at: https://github.com/apache/felix/pull/98 > Specify ARM processor Endianness > > > Key: FELIX-5593 > URL: https://issues.apache.org/jira/browse/FELIX-5593 > Project: Felix > Issue Type: Improvement > Components: Framework >Affects Versions: framework-5.6.1 >Reporter: Kerry Billingham >Assignee: David Bosschaert >Priority: Minor > Fix For: framework-5.6.4 > > > In accordance with OSGi core specification, ver. 6 Table 4.2, specifying > processor type 'ARM' is now deprecated. It is now preferred to use the > processor type 'arm_le' or 'arm_be'. > Felix currently determines the processor type by requesting the system > property "os.arch" however this has been found to return the deprecated 'arm' > processor string for example on the RaspberryPi installed with Raspbian OS > and the latest Oracle JDK8 for ARM. > To meet with the above specification it is proposed that Felix be modified to > appropriately to determine the endianness of ARM processors. A PR with > suggested modifications is to follow this Enhancement proposal. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Work started] (FELIX-5593) Specify ARM processor Endianness
[ https://issues.apache.org/jira/browse/FELIX-5593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on FELIX-5593 started by David Bosschaert. --- > Specify ARM processor Endianness > > > Key: FELIX-5593 > URL: https://issues.apache.org/jira/browse/FELIX-5593 > Project: Felix > Issue Type: Improvement > Components: Framework >Affects Versions: framework-5.6.1 >Reporter: Kerry Billingham >Assignee: David Bosschaert >Priority: Minor > Fix For: framework-5.6.4 > > > In accordance with OSGi core specification, ver. 6 Table 4.2, specifying > processor type 'ARM' is now deprecated. It is now preferred to use the > processor type 'arm_le' or 'arm_be'. > Felix currently determines the processor type by requesting the system > property "os.arch" however this has been found to return the deprecated 'arm' > processor string for example on the RaspberryPi installed with Raspbian OS > and the latest Oracle JDK8 for ARM. > To meet with the above specification it is proposed that Felix be modified to > appropriately to determine the endianness of ARM processors. A PR with > suggested modifications is to follow this Enhancement proposal. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] felix pull request #98: [FELIX-5593] Return endian mode as part of processor...
Github user asfgit closed the pull request at: https://github.com/apache/felix/pull/98 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (FELIX-5593) Specify ARM processor Endianness
[ https://issues.apache.org/jira/browse/FELIX-5593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15936371#comment-15936371 ] David Bosschaert commented on FELIX-5593: - Many thanks for the patch [~jtkb]! It's applied in https://svn.apache.org/viewvc?view=revision&revision=1788110 > Specify ARM processor Endianness > > > Key: FELIX-5593 > URL: https://issues.apache.org/jira/browse/FELIX-5593 > Project: Felix > Issue Type: Improvement > Components: Framework >Affects Versions: framework-5.6.1 >Reporter: Kerry Billingham >Assignee: David Bosschaert >Priority: Minor > Fix For: framework-5.6.4 > > > In accordance with OSGi core specification, ver. 6 Table 4.2, specifying > processor type 'ARM' is now deprecated. It is now preferred to use the > processor type 'arm_le' or 'arm_be'. > Felix currently determines the processor type by requesting the system > property "os.arch" however this has been found to return the deprecated 'arm' > processor string for example on the RaspberryPi installed with Raspbian OS > and the latest Oracle JDK8 for ARM. > To meet with the above specification it is proposed that Felix be modified to > appropriately to determine the endianness of ARM processors. A PR with > suggested modifications is to follow this Enhancement proposal. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (FELIX-5593) Specify ARM processor Endianness
[ https://issues.apache.org/jira/browse/FELIX-5593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Bosschaert resolved FELIX-5593. - Resolution: Fixed > Specify ARM processor Endianness > > > Key: FELIX-5593 > URL: https://issues.apache.org/jira/browse/FELIX-5593 > Project: Felix > Issue Type: Improvement > Components: Framework >Affects Versions: framework-5.6.1 >Reporter: Kerry Billingham >Assignee: David Bosschaert >Priority: Minor > Fix For: framework-5.6.4 > > > In accordance with OSGi core specification, ver. 6 Table 4.2, specifying > processor type 'ARM' is now deprecated. It is now preferred to use the > processor type 'arm_le' or 'arm_be'. > Felix currently determines the processor type by requesting the system > property "os.arch" however this has been found to return the deprecated 'arm' > processor string for example on the RaspberryPi installed with Raspbian OS > and the latest Oracle JDK8 for ARM. > To meet with the above specification it is proposed that Felix be modified to > appropriately to determine the endianness of ARM processors. A PR with > suggested modifications is to follow this Enhancement proposal. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (FELIX-5549) Factory component fails to reactivate after config changes
[ https://issues.apache.org/jira/browse/FELIX-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks reassigned FELIX-5549: --- Assignee: David Jencks > Factory component fails to reactivate after config changes > -- > > Key: FELIX-5549 > URL: https://issues.apache.org/jira/browse/FELIX-5549 > Project: Felix > Issue Type: Bug > Components: Declarative Services (SCR) > Environment: Karaf 4.0.8 >Reporter: Alex Soto >Assignee: David Jencks > > A factory component fails to reactive after the configuration changes. > Initially, the component initializes normally. After it is in Active state, > the configuration referenced by the component _configurationPid_ changes, > which causes the component to not activate again. > A minimal application demonstrating this behavior is available here: > https://github.com/lexsoto/blueprint-ds-config-reload -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (FELIX-5596) Allow to configure the colors for the gogo grep command
Christian Schneider created FELIX-5596: -- Summary: Allow to configure the colors for the gogo grep command Key: FELIX-5596 URL: https://issues.apache.org/jira/browse/FELIX-5596 Project: Felix Issue Type: Improvement Components: Gogo JLine Affects Versions: gogo.jline-1.0.4 Reporter: Christian Schneider Fix For: gogo.jline-1.0.6 The Highlighter as well as the ls command already allow to configure colors but grep does not yet. I will implement such configuration in a way compatible to the unix grep command. See : http://www.gnu.org/software/grep/manual/html_node/Environment-Variables.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (FELIX-5549) Factory component fails to reactivate after config changes
[ https://issues.apache.org/jira/browse/FELIX-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15936668#comment-15936668 ] David Jencks commented on FELIX-5549: - Are you changing what you are complaining about? I don't think your example had ConfigurationPolicy.REQUIRE.Are you now suggesting that the spec would be clearer if it included a third condition, something like If the configurationPolicy is REQUIRE then there are configurations for each of the components pids. I think there may be a different bug, which I suspect is a mistake in the spec. The second condition specifies using the component properties from the component description, i.e. the xml before merging with any configurations, whereas the implementation IIRC uses the properties from merging the xml with configurations. I suspect this is an historical error from not updating the part of the spec dealing with factory components when configuration from config admin was introduced. > Factory component fails to reactivate after config changes > -- > > Key: FELIX-5549 > URL: https://issues.apache.org/jira/browse/FELIX-5549 > Project: Felix > Issue Type: Bug > Components: Declarative Services (SCR) > Environment: Karaf 4.0.8 >Reporter: Alex Soto >Assignee: David Jencks > > A factory component fails to reactive after the configuration changes. > Initially, the component initializes normally. After it is in Active state, > the configuration referenced by the component _configurationPid_ changes, > which causes the component to not activate again. > A minimal application demonstrating this behavior is available here: > https://github.com/lexsoto/blueprint-ds-config-reload -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FELIX-5596) Allow to configure the colors for the gogo grep command
[ https://issues.apache.org/jira/browse/FELIX-5596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider updated FELIX-5596: --- Flags: Patch > Allow to configure the colors for the gogo grep command > --- > > Key: FELIX-5596 > URL: https://issues.apache.org/jira/browse/FELIX-5596 > Project: Felix > Issue Type: Improvement > Components: Gogo JLine >Affects Versions: gogo.jline-1.0.4 >Reporter: Christian Schneider > Fix For: gogo.jline-1.0.6 > > > The Highlighter as well as the ls command already allow to configure colors > but grep does not yet. > I will implement such configuration in a way compatible to the unix grep > command. See : > http://www.gnu.org/software/grep/manual/html_node/Environment-Variables.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (FELIX-5596) Allow to configure the colors for the gogo grep command
[ https://issues.apache.org/jira/browse/FELIX-5596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15936673#comment-15936673 ] ASF GitHub Bot commented on FELIX-5596: --- GitHub user cschneider opened a pull request: https://github.com/apache/felix/pull/100 [FELIX-5596] Allow to configure the colors for the gogo grep command You can merge this pull request into a Git repository by running: $ git pull https://github.com/cschneider/felix FELIX-5596 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/felix/pull/100.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 #100 commit 0347568b3921ac0d717830a2570c53cdb2cacafc Author: Christian Schneider Date: 2017-03-22T16:52:58Z [FELIX-5596] Allow to configure the colors for the gogo grep command > Allow to configure the colors for the gogo grep command > --- > > Key: FELIX-5596 > URL: https://issues.apache.org/jira/browse/FELIX-5596 > Project: Felix > Issue Type: Improvement > Components: Gogo JLine >Affects Versions: gogo.jline-1.0.4 >Reporter: Christian Schneider > Fix For: gogo.jline-1.0.6 > > > The Highlighter as well as the ls command already allow to configure colors > but grep does not yet. > I will implement such configuration in a way compatible to the unix grep > command. See : > http://www.gnu.org/software/grep/manual/html_node/Environment-Variables.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (FELIX-5597) Ctrl-C should not end the gogo shell and felix framework
Christian Schneider created FELIX-5597: -- Summary: Ctrl-C should not end the gogo shell and felix framework Key: FELIX-5597 URL: https://issues.apache.org/jira/browse/FELIX-5597 Project: Felix Issue Type: Bug Components: Gogo JLine Affects Versions: gogo.jline-1.0.4 Reporter: Christian Schneider Fix For: gogo.jline-1.0.6 When starting the felix distro 5.6.2 it uses the gogo jline shell. When I use the tail -f command to watch a log I can not exit the tail without ending the whole framework. Tail -f can only be stopped by pressing Ctrl-C. In Apache Karaf this works. The command is interrupted and your are back in the gogo shell. The same issue of ending the framework can also be reproduced by pressing Ctrl-C while no command is executed. In felix distro it ends the framework, in karaf it only goes to the next line in the shell. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] felix pull request #100: [FELIX-5596] Allow to configure the colors for the ...
GitHub user cschneider opened a pull request: https://github.com/apache/felix/pull/100 [FELIX-5596] Allow to configure the colors for the gogo grep command You can merge this pull request into a Git repository by running: $ git pull https://github.com/cschneider/felix FELIX-5596 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/felix/pull/100.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 #100 commit 0347568b3921ac0d717830a2570c53cdb2cacafc Author: Christian Schneider Date: 2017-03-22T16:52:58Z [FELIX-5596] Allow to configure the colors for the gogo grep command --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (FELIX-5549) Factory component fails to reactivate after config changes
[ https://issues.apache.org/jira/browse/FELIX-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15936746#comment-15936746 ] Alex Soto commented on FELIX-5549: -- OK, maybe I am. The true is, that as a user, I have been very confused by the inconsistent behavior. I am relatively new to this, and I apologize for the confusion. Yes, the conditions as documented, do not match the behavior, but fixing the documentation alone will not be sufficient. The fact that a client of the Factory component (in my case Booter) cannot react to the full component life cycle is a major flaw, and my specific problem. If the Factory Component is deactivated due to configuration change, its clients are unaware and still hold and use a reference to a component instance, without any way of knowing that it has been deactivated. This contrasts with to what happens with references, i.e., the Component Factory Service is unregistered/registered when references become unresolved/resolved, and the Booter is therefore notified, and it can discard the component instance reference correctly. I have a workaround (using modified) but then I need to use thread synchronization, to protect members in case they are modified concurrently, which is not as clean as activation/deactivation. > Factory component fails to reactivate after config changes > -- > > Key: FELIX-5549 > URL: https://issues.apache.org/jira/browse/FELIX-5549 > Project: Felix > Issue Type: Bug > Components: Declarative Services (SCR) > Environment: Karaf 4.0.8 >Reporter: Alex Soto >Assignee: David Jencks > > A factory component fails to reactive after the configuration changes. > Initially, the component initializes normally. After it is in Active state, > the configuration referenced by the component _configurationPid_ changes, > which causes the component to not activate again. > A minimal application demonstrating this behavior is available here: > https://github.com/lexsoto/blueprint-ds-config-reload -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (FELIX-5598) [gogo][jline] Support the JLine ttop function if available
Guillaume Nodet created FELIX-5598: -- Summary: [gogo][jline] Support the JLine ttop function if available Key: FELIX-5598 URL: https://issues.apache.org/jira/browse/FELIX-5598 Project: Felix Issue Type: Improvement Components: Gogo JLine Reporter: Guillaume Nodet Assignee: Guillaume Nodet Fix For: gogo.jline-1.0.6 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (FELIX-5598) [gogo][jline] Support the JLine ttop function if available
[ https://issues.apache.org/jira/browse/FELIX-5598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved FELIX-5598. Resolution: Fixed Committing to https://svn.apache.org/repos/asf/felix/trunk ... M gogo/jline/src/main/java/org/apache/felix/gogo/jline/Posix.java Committed r1788154 > [gogo][jline] Support the JLine ttop function if available > -- > > Key: FELIX-5598 > URL: https://issues.apache.org/jira/browse/FELIX-5598 > Project: Felix > Issue Type: Improvement > Components: Gogo JLine >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > Fix For: gogo.jline-1.0.6 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (FELIX-5598) [gogo][jline] Support the JLine ttop function if available
[ https://issues.apache.org/jira/browse/FELIX-5598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15937006#comment-15937006 ] Guillaume Nodet edited comment on FELIX-5598 at 3/22/17 7:55 PM: - Committing to https://svn.apache.org/repos/asf/felix/trunk ... M gogo/jline/pom.xml M gogo/jline/src/main/java/org/apache/felix/gogo/jline/Posix.java Committed r1788155 was (Author: gnt): Committing to https://svn.apache.org/repos/asf/felix/trunk ... M gogo/jline/src/main/java/org/apache/felix/gogo/jline/Posix.java Committed r1788154 > [gogo][jline] Support the JLine ttop function if available > -- > > Key: FELIX-5598 > URL: https://issues.apache.org/jira/browse/FELIX-5598 > Project: Felix > Issue Type: Improvement > Components: Gogo JLine >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > Fix For: gogo.jline-1.0.6 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (FELIX-5596) Allow to configure the colors for the gogo grep command
[ https://issues.apache.org/jira/browse/FELIX-5596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved FELIX-5596. Resolution: Fixed Assignee: Guillaume Nodet Committing to https://svn.apache.org/repos/asf/felix/trunk ... M gogo/jline/src/main/java/org/apache/felix/gogo/jline/Posix.java Committed r1788154 > Allow to configure the colors for the gogo grep command > --- > > Key: FELIX-5596 > URL: https://issues.apache.org/jira/browse/FELIX-5596 > Project: Felix > Issue Type: Improvement > Components: Gogo JLine >Affects Versions: gogo.jline-1.0.4 >Reporter: Christian Schneider >Assignee: Guillaume Nodet > Fix For: gogo.jline-1.0.6 > > > The Highlighter as well as the ls command already allow to configure colors > but grep does not yet. > I will implement such configuration in a way compatible to the unix grep > command. See : > http://www.gnu.org/software/grep/manual/html_node/Environment-Variables.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (FELIX-5596) Allow to configure the colors for the gogo grep command
[
https://issues.apache.org/jira/browse/FELIX-5596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15937011#comment-15937011
]
Guillaume Nodet commented on FELIX-5596:
Fwiw, I've added support for the other flags...
The ones not supported are {{bn}} (the underlying functionality is not
implemented) and {{ne}}.
> Allow to configure the colors for the gogo grep command
> ---
>
> Key: FELIX-5596
> URL: https://issues.apache.org/jira/browse/FELIX-5596
> Project: Felix
> Issue Type: Improvement
> Components: Gogo JLine
>Affects Versions: gogo.jline-1.0.4
>Reporter: Christian Schneider
>Assignee: Guillaume Nodet
> Fix For: gogo.jline-1.0.6
>
>
> The Highlighter as well as the ls command already allow to configure colors
> but grep does not yet.
> I will implement such configuration in a way compatible to the unix grep
> command. See :
> http://www.gnu.org/software/grep/manual/html_node/Environment-Variables.html
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (FELIX-5593) Specify ARM processor Endianness
[ https://issues.apache.org/jira/browse/FELIX-5593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15937143#comment-15937143 ] Kerry Billingham commented on FELIX-5593: - You're welcome [~bosschaert]. > Specify ARM processor Endianness > > > Key: FELIX-5593 > URL: https://issues.apache.org/jira/browse/FELIX-5593 > Project: Felix > Issue Type: Improvement > Components: Framework >Affects Versions: framework-5.6.1 >Reporter: Kerry Billingham >Assignee: David Bosschaert >Priority: Minor > Fix For: framework-5.6.4 > > > In accordance with OSGi core specification, ver. 6 Table 4.2, specifying > processor type 'ARM' is now deprecated. It is now preferred to use the > processor type 'arm_le' or 'arm_be'. > Felix currently determines the processor type by requesting the system > property "os.arch" however this has been found to return the deprecated 'arm' > processor string for example on the RaspberryPi installed with Raspbian OS > and the latest Oracle JDK8 for ARM. > To meet with the above specification it is proposed that Felix be modified to > appropriately to determine the endianness of ARM processors. A PR with > suggested modifications is to follow this Enhancement proposal. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (FELIX-5596) Allow to configure the colors for the gogo grep command
[ https://issues.apache.org/jira/browse/FELIX-5596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15937809#comment-15937809 ] ASF GitHub Bot commented on FELIX-5596: --- Github user cschneider closed the pull request at: https://github.com/apache/felix/pull/100 > Allow to configure the colors for the gogo grep command > --- > > Key: FELIX-5596 > URL: https://issues.apache.org/jira/browse/FELIX-5596 > Project: Felix > Issue Type: Improvement > Components: Gogo JLine >Affects Versions: gogo.jline-1.0.4 >Reporter: Christian Schneider >Assignee: Guillaume Nodet > Fix For: gogo.jline-1.0.6 > > > The Highlighter as well as the ls command already allow to configure colors > but grep does not yet. > I will implement such configuration in a way compatible to the unix grep > command. See : > http://www.gnu.org/software/grep/manual/html_node/Environment-Variables.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)
