[ 
https://issues.apache.org/jira/browse/FELIX-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12702888#action_12702888
 ] 

Richard S. Hall commented on FELIX-1000:
----------------------------------------

I think when you want to update a bundle, you would likely want to update to 
the newest, otherwise you'd likely specify the version you wanted. This is the 
typical "check for updates" type of scenario where you want to update to the 
newest.

Ultimately, I don't disagree that there are different policies available. I 
don't think it is typical people want to upgrade to the next available as 
opposed to the newest, however, I can imagine some people might. One policy 
definitely doesn't fit all. However, either way we are encoding a specific 
policy. With your policy in place then updating to the newest version becomes a 
manual process, with my policy updating to the next available becomes a manual 
process.

So, the real question is what people think the default policy should be?

As for OBR not trying to update, that is not really true. When 
Resolver.deploy() is called, it tries to minimize the number of bundles it 
installs, so if possible it will update an existing bundle to a newer version.

> Updating an bundle which was installed via OBR fails
> ----------------------------------------------------
>
>                 Key: FELIX-1000
>                 URL: https://issues.apache.org/jira/browse/FELIX-1000
>             Project: Felix
>          Issue Type: Bug
>          Components: Bundle Repository (OBR)
>            Reporter: Kristian Koehler
>         Attachments: FELIX-1000-21_04_2009.patch.txt, 
> FELIX-1000-23_04_2009.patch.txt
>
>
> Updating an bundle which was installed via the obr functionality results in 
> an exception (update was triggered via the shell):
> --- 8< ---
> java.net.MalformedURLException: Unknown protocol: obr
>       at java.net.URL.<init>(URL.java:601)
>       at java.net.URL.<init>(URL.java:464)
>       at java.net.URL.<init>(URL.java:413)
>       at 
> org.apache.felix.framework.cache.JarRevision.initialize(JarRevision.java:149)
>       at 
> org.apache.felix.framework.cache.JarRevision.<init>(JarRevision.java:78)
>       at 
> org.apache.felix.framework.cache.JarRevision.<init>(JarRevision.java:56)
>       at 
> org.apache.felix.framework.cache.BundleArchive.createRevisionFromLocation(BundleArchive.java:986)
>       at 
> org.apache.felix.framework.cache.BundleArchive.revise(BundleArchive.java:614)
>       at org.apache.felix.framework.BundleImpl.revise(BundleImpl.java:916)
>       at org.apache.felix.framework.Felix.updateBundle(Felix.java:1592)
>       at org.apache.felix.framework.BundleImpl.update(BundleImpl.java:792)
>       at org.apache.felix.framework.BundleImpl.update(BundleImpl.java:779)
>       at 
> org.apache.felix.shell.impl.UpdateCommandImpl.execute(UpdateCommandImpl.java:96)
>       at 
> org.apache.felix.shell.impl.Activator$ShellServiceImpl.executeCommand(Activator.java:276)
>       at 
> org.apache.felix.shell.tui.Activator$ShellTuiRunnable.run(Activator.java:167)
>       at java.lang.Thread.run(Thread.java:619)
> --- 8< ---

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to