[jira] Assigned: (KARAF-130) Allow a repository URL to be added to feature repository URL list even though it is an invalid one
[ https://issues.apache.org/jira/browse/KARAF-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned KARAF-130: -- Assignee: Freeman Fang > Allow a repository URL to be added to feature repository URL list even though > it is an invalid one > -- > > Key: KARAF-130 > URL: https://issues.apache.org/jira/browse/KARAF-130 > Project: Karaf > Issue Type: Improvement >Reporter: Freeman Fang >Assignee: Freeman Fang > > so that using features:listUrl we can see the invalid url also, probably we > can add "invalid" suffix to the invalid url to let customer know the url > status -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (KARAF-130) Allow a repository URL to be added to feature repository URL list even though it is an invalid one
Allow a repository URL to be added to feature repository URL list even though it is an invalid one -- Key: KARAF-130 URL: https://issues.apache.org/jira/browse/KARAF-130 Project: Karaf Issue Type: Improvement Reporter: Freeman Fang so that using features:listUrl we can see the invalid url also, probably we can add "invalid" suffix to the invalid url to let customer know the url status -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (KARAF-60) Improve history support by using the !
[ https://issues.apache.org/jira/browse/KARAF-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned KARAF-60: - Assignee: Jean-Baptiste Onofré > Improve history support by using the ! > --- > > Key: KARAF-60 > URL: https://issues.apache.org/jira/browse/KARAF-60 > Project: Karaf > Issue Type: Improvement >Reporter: Guillaume Nodet >Assignee: Jean-Baptiste Onofré > Attachments: SMX4KNL-237.patch > > > the history command is cool but it would be nice to be able to use things > like: > * !142 (run the command from the history with index 142) > * !os (run last command starting with "os") > = > See http://www.gnu.org/software/bash/manual/html_node/Event-Designators.html > = > with this patch, we can access history command list with > ! indext > ! commandPrefix > for example, history we get > 345 osgi/list > then > "! 345" or "! os" we get "osgi/list" execute again > seems we have to add a whitespace between ! and the index number or > commandPrefix, so the syntax is not exactly same as bash (which no whitespace > between ! and index number) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (KARAF-40) Create a maven archetype for creating shell commands
[ https://issues.apache.org/jira/browse/KARAF-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ioannis Canellos updated KARAF-40: -- Attachment: command-archetype-patch.txt I am attaching a patch for a simple maven shell commands archetype. This archetype can be used to create a bundle with a single command. The scope, the command & the description of the command can be passed as parameters during project generation like: mvn archetype:generate -DarchetypeGroupId=org.apache.karaf.shell \ -DarchetypeArtifactId=org.apache.karaf.shell.command.archetype \ -DarchetypeVersion=1.99.0-SNAPSHOT \ -DgroupId=org.apache.shell.test \ -DartifactId=test.commands \ -Dscope=test \ -Dcommand=TestCommand \ -Ddescription=An example command for demonstrating the command archetype. > Create a maven archetype for creating shell commands > > > Key: KARAF-40 > URL: https://issues.apache.org/jira/browse/KARAF-40 > Project: Karaf > Issue Type: Task >Reporter: Guillaume Nodet > Attachments: command-archetype-patch.txt > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (KARAF-9) The config/edit command changes does not takes precedence over configuration files in the etc folder at restart
[ https://issues.apache.org/jira/browse/KARAF-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12889861#action_12889861 ] Ioannis Canellos commented on KARAF-9: -- I think that this issue should be closed, since that functionality has been implemented for quite some time now. > The config/edit command changes does not takes precedence over configuration > files in the etc folder at restart > --- > > Key: KARAF-9 > URL: https://issues.apache.org/jira/browse/KARAF-9 > Project: Karaf > Issue Type: Bug >Reporter: Guillaume Nodet > > If you do the following > servicemix config> edit org.ops4j.pax.logging > servicemix config> log4j.appender.out.file /tmp/servicemix.log > servicemix config> update > It does create my servicemix.log file in the /tmp directory and will log > stuff there but if I shut the instance down > and restart it - it redirects back to the original location for the > servicemix.log file in the data directory. > = > Guillaume Nodet: > Actually, this is the currently designed behavior. Configuration updates do > not take precedence over the configuration files. So each time the > configuration file is changed or reloaded due to a server restart, the > changes done via the console are lost. > However, this may be improved by saving the changes to the properties file > instead of saving the changes directly into the ConfigAdmin service. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (KARAF-9) The config/edit command changes does not takes precedence over configuration files in the etc folder at restart
[ https://issues.apache.org/jira/browse/KARAF-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet closed KARAF-9. --- Resolution: Fixed > The config/edit command changes does not takes precedence over configuration > files in the etc folder at restart > --- > > Key: KARAF-9 > URL: https://issues.apache.org/jira/browse/KARAF-9 > Project: Karaf > Issue Type: Bug >Reporter: Guillaume Nodet > > If you do the following > servicemix config> edit org.ops4j.pax.logging > servicemix config> log4j.appender.out.file /tmp/servicemix.log > servicemix config> update > It does create my servicemix.log file in the /tmp directory and will log > stuff there but if I shut the instance down > and restart it - it redirects back to the original location for the > servicemix.log file in the data directory. > = > Guillaume Nodet: > Actually, this is the currently designed behavior. Configuration updates do > not take precedence over the configuration files. So each time the > configuration file is changed or reloaded due to a server restart, the > changes done via the console are lost. > However, this may be improved by saving the changes to the properties file > instead of saving the changes directly into the ConfigAdmin service. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (KARAF-106) Provide a more minimal / static disitrbution of karaf
[ https://issues.apache.org/jira/browse/KARAF-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ioannis Canellos updated KARAF-106: --- Attachment: patchfile.txt I am attaching a patch for this issue that provides 2 new distributions unix-minimal & windows-minimal. Currently the minimal distributions exclude (SSH, Administrator & Deployer bundles from /system & startup). The changes this patch makes are: 1) Added 2 assembly executions (unix-minimal-bin & windows-minimal-bin). 2) For these executions added 2 new descriptors that exclude SSH, Administration & Deployer bundles under the /system repository & startup.properties. 3) Added 2 new features for Administration & Deployer bundles (SSH prexisted) for all distributions. 4) Removed SSH, Administration & Deployer from startup.properties (affects only minimal distributions) 5) Removed SSH from featuresBoot (affects only minimal distributions) 6) Under filtered resources folder folder etc split to etc, etc-normal & etc-minimal so that normal & minimal distributions can have different startup.properties & If you would like to exclude additional bundles, let me know. > Provide a more minimal / static disitrbution of karaf > - > > Key: KARAF-106 > URL: https://issues.apache.org/jira/browse/KARAF-106 > Project: Karaf > Issue Type: Improvement >Reporter: Guillaume Nodet > Attachments: patchfile.txt > > > Servers that are mostly static (thinking about activemq, directory, james, > etc...) usually don't require the deploy folder, the admin stuff and all. > I think we should provide a slightly more lightweight distribution without > the added bits. For example, ssh could be added through a feature, but not > included by default, etc... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
