felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Klimetschek (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (FELIX-1758) bundle.location not updated when new version of a bundle is 'jcr'-installed
Date Thu, 03 Dec 2009 13:46:20 GMT

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

Alexander Klimetschek edited comment on FELIX-1758 at 12/3/09 1:44 PM:
-----------------------------------------------------------------------

> That link doesn't say the location no longer needs to be unique
I forgot to add "implementation-wise" ;-) But I don't know the Felix codebase too much to
decide upon this.


      was (Author: alexander.klimetschek):
    > That link doesn't say the location no longer needs to be unique
I forgot to add "implementation-wise" ;-) But I don't know the Felix codebase too much to
decide upon this.

Coming back to that: I noticed that if you do an update via the WebConsole, the location string
will change, as opposed to eg. Sling's jcrinstall that was mentioned originally. What is the
difference between these two ways of "updating" the bundle? Uninstall vs. update? Maybe it
requires a change in jcrinstall.
  
> 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.


Mime
View raw message