dantran wrote: > > filed at https://issues.apache.org/jira/browse/KARAF-524 > > > I also notice that, thru TRACE logger, I can see for each > features:refreshUrl, Karaf makes several attempts to refresh ( it > reaching out to all configured maven repositories ). Is it another > bug? > > Thanks > > -Dan > > On Thu, Mar 17, 2011 at 9:50 AM, karafman <[email protected]> > wrote: >> >> Guillaume Nodet wrote: >>> >>> I'll experiment to see if it is possible to find if the snapshot has >>> changed. >>> Could you please raise a JIRA issue for that ? >>> >>> On Thu, Mar 17, 2011 at 17:27, Guillaume Nodet <[email protected]> >>> wrote: >>>> First refreshUrl only reload the features descriptors. It doesn't >>>> update the features. We've added the dev:watch command in karaf 2.2.0 >>>> which can automatically update bundles if newer snapshots are >>>> available in your local repo. I guess the problem is to detect when >>>> snapshots have actually changed, but I suppose it could be done by >>>> looking at the maven metadata. >>>> Though it might be a bit more costly than checking the local file >>>> system as this would need several http requests for each snapshot, so >>>> a sufficient delay should be used between polls. >>>> >>>> On Thu, Mar 17, 2011 at 17:12, Dan Tran <[email protected]> >>>> wrote: >>>>> Hello, >>>>> >>>>> I am able to install my snaphot features from my company maven >>>>> repository. When there is new snapshot on my repo, >>>>> features:refreshUrl is able to identify the latest snapshot >>>>> ..-features.xml ( via latest timestamp file ), however after that >>>>> nothing happens. I am expecting all my SNAPSHOT bundles belong to my >>>>> features.xml to get downloaded and restart. >>>>> >>>>> is this a bug? >>>>> >>>>> -Dan >>>>> >>>> >>>> >>>> >>>> -- >>>> Cheers, >>>> Guillaume Nodet >>>> ------------------------ >>>> Blog: http://gnodet.blogspot.com/ >>>> ------------------------ >>>> Open Source SOA >>>> http://fusesource.com >>>> >>> >>> >>> >>> -- >>> Cheers, >>> Guillaume Nodet >>> ------------------------ >>> Blog: http://gnodet.blogspot.com/ >>> ------------------------ >>> Open Source SOA >>> http://fusesource.com >>> >> >> Guillaume, >> >> I think the dev:watch command is a great idea. However, I can see how it >> could possibly introduce problems if left on, or forgotten about by the >> developer. Perhaps as part of adding the new functionality to >> automatically >> update snapshots when they are refreshed in the maven repository, you >> could >> send something to the console to indicate an automatic update is being >> performed? >> >> ----- >> Karafman >> Slayer of the JEE >> Pounder of the Perl Programmer >> >> -- >> View this message in context: >> http://karaf.922171.n3.nabble.com/How-does-features-refreshUrl-handles-snapshot-tp2694125p2694314.html >> Sent from the Karaf - User mailing list archive at Nabble.com. >> >
Dan, This may be a result of how you are provisioning. Basically, when Karaf deploys a feature, if any bundles within that feature already exist inside of Karaf, it will refresh them. It does this to ensure all the appropriate wiring from that dependent bundle take place. Additionally, if a feature fails to deploy, Karaf will uninstall that entire feature, and perform refreshes on bundles that are affected. So, in short, to answer your question, no this is not a bug. It is working as it should. ----- Karafman Slayer of the JEE Pounder of the Perl Programmer -- View this message in context: http://karaf.922171.n3.nabble.com/How-does-features-refreshUrl-handles-snapshot-tp2694125p2694455.html Sent from the Karaf - User mailing list archive at Nabble.com.
