[
https://issues.apache.org/jira/browse/FELIX-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12784318#action_12784318
]
Alexander Klimetschek commented on FELIX-1758:
----------------------------------------------
The location semantics seem to be specified here:
http://www.osgi.org/javadoc/r4v42/org/osgi/framework/Bundle.html#getLocation()
I think the web console could at least be more specific about the actual
meaning of Location, by saying: "Location (upon first install):" I guess most
people won't know that specific semantic and rather associate it intuitively
with the location from that last bundle update.
I also found this link:
http://dev.eclipse.org/newslists/news.eclipse.technology.equinox/msg04503.html
saying that location no longer needs to be unique. Maybe that constrained can
be lowered in the next version of the OSGi spec?
> bundle.location not updated when new version of a bundle is 'jcr'-installed
> ---------------------------------------------------------------------------
>
> Key: FELIX-1758
> URL: https://issues.apache.org/jira/browse/FELIX-1758
> Project: Felix
> Issue Type: Bug
> Components: Web Console
> Affects Versions: webconsole-1.2.10
> Reporter: Honwai Wong
> Priority: Trivial
>
> The details view of a bundle shows an outdated location if a newer version of
> the bundle has been deployed using jcrinstall. The version information is
> correct, merely the location points to an old version of the bundle. This
> does not occur when deploying the same bundle directly via the web console.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
