[
https://issues.apache.org/activemq/browse/SMX4KNL-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=41843#action_41843
]
Guillaume Nodet commented on SMX4KNL-25:
----------------------------------------
{quote}
yeah, I think we need to version the features. as it can give users ability to
install a specific version of that feature, I don't know whether it will cause
problems if we add this version attribute?
{quote}
I don't see any problems to that. i agree we should keep the version somewhere
so that we can upgrade features easily.
{quote}
Another thing I saw is that now when we release a feature, take NMR as an
example, we release this features url along with. I am thinking that we can
update the
"http://svn.apache.org/repos/asf/servicemix/smx4/obr-repo/features.xml"; xml
file when we finish a release. So instead of asking users to add/update a
feature url, users can get the released features automatically, and then can
upgrade or keep it as what they want.
{quote}
Yeah, I forgot to update the features.xml I think. I used a single file
somewhere while it was not officially released, but it should go in the main
features.xml.
{quote}
Currently, there is a problem for adding feature url is that after I reboot the
kernel, I can't see any updated/added feature url, since it has not been kept
in the file system.
{quote}
True. We could easily use the preferences services to store such data. It
will also be needed to be able to persist which features/versions have been
installed so that you can uninstall / upgrade those. The preferences services
is needed for the NMR anyway, so it makes sense to include it in the kernel by
default I suppose.
{quote}
A big feature xml file might not a good idea, but my concern is that for users,
mostly, they just need to know the one smx features repository url, and then
don't need to update it most of time. but maybe we can split one big smx
features into several xml fragment, but it should be transparent for users.
{quote}
Good idea. What about adding a <repository url="xxx" /> element in the
<features> element that would be imported when parsed ?
{quote}
I am not sure about the command proxy? do you mean "nmr", this sort of command??
{quote}
Well, once you add a repository xml file, for each feature, a command is
created. This command does nothing but when launched, prompts the user to
install this feature. I'm thinking it makes more sense to let the users list
the available features aso ...
Btw, I will commit my pending modifications. If you want to continue working
on those, tell me so that we don't overlap.
> Feature commands enhancement.
> -----------------------------
>
> Key: SMX4KNL-25
> URL: https://issues.apache.org/activemq/browse/SMX4KNL-25
> Project: ServiceMix Kernel
> Issue Type: Improvement
> Affects Versions: 1.0-m3
> Reporter: Jeff Yu
> Fix For: 1.0-m3
>
>
> When I saw the instruction for installing the NMR feature from the User
> Guide. I think it makes us really easir to install it rather than to copy all
> the jars into the deploy folder manually. and suddenly, it occurs to me that
> this is very similar to "apt-get" utility in Ubuntu or "yum" utility in the
> Fedora distro.
> Put it simply, right now what we need to install an NMR feature is:
> <pre>
> features addUrl
> http://svn.apache.org/repos/asf/servicemix/smx4/obr-repo/features-nmr-1.0-m1.xml
> nmr
> </pre>
> and what I like is that we can do it like this:
> <pre>
> features addUrl
> http://svn.apache.org/repos/asf/servicemix/smx4/obr-repo/features-nmr-1.0-m1.xml
> features install nmr
> </pre>
> and then we can extend following commands:
> features upgrade nmr
> features remove nmr
> features list (for browsing all available features in the repository).
> in this way, we should be easily to install/remove the features, and users
> wouldn't need to consider the dependency issues.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
