[
https://issues.apache.org/jira/browse/KARAF-6601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17018570#comment-17018570
]
Julian Feinauer commented on KARAF-6601:
----------------------------------------
I like the idea and I guess the implementation could be similar to bundle
watch. I'm trying to do a first implementation of it as example. @jbonofre I
agree with you that feature repo watch makes more sense than feature watch
alone (and does a red fresh then).
> New Command - feature:watch
> ---------------------------
>
> Key: KARAF-6601
> URL: https://issues.apache.org/jira/browse/KARAF-6601
> Project: Karaf
> Issue Type: New Feature
> Components: karaf
> Reporter: Thomas Driessen
> Priority: Trivial
> Labels: features
>
> A new command that should be added to the karaf console: feature:watch
> It's the feature counterpart to bundle:watch and watches not only one bundle,
> but a whole feature for updates.
> Rational: When adding a new dependency to a bundle that is watched by karaf,
> then usually the resolver complains about a missing dependency. The usual
> workflow for a developer is then:
> * refresh feature repositories
> * refresh feature
> In order to streamline this workflow there should be a command that, given a
> feature, watches all bundles/resources of it and if something changes
> executes those two commands.
>
> Benefit: One is not confronted with ugly resolver error messages ;) , faster
> development workflow.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
