You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Erwin Hogeweg (JIRA)" <ji...@apache.org> on 2018/03/23 23:22:00 UTC

[jira] [Commented] (KARAF-4943) bundle:watch doesn't take timezone into account when comparing modification date

    [ https://issues.apache.org/jira/browse/KARAF-4943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16412236#comment-16412236 ] 

Erwin Hogeweg commented on KARAF-4943:
--------------------------------------

This issue can be closed. It appeared to be an incorrect maven-bundle-plugin configuration issue with the maven-bundle-plugin.

> bundle:watch doesn't take timezone into account when comparing modification date
> --------------------------------------------------------------------------------
>
>                 Key: KARAF-4943
>                 URL: https://issues.apache.org/jira/browse/KARAF-4943
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-core
>    Affects Versions: 4.0.8
>         Environment: OS X 10.12.2, Java 8
>            Reporter: Erwin Hogeweg
>            Priority: Major
>
> I noticed that bundle:watch kept restarting the same bundles over-and-over again. After some digging I believe this behavior is caused by BundleWatchImpl:163
>         if (location != null && location.exists() && location.lastModified() > bundle.getLastModified()) {
> The location.lastModified() returns the timestamp in GMT, while the bundle.lastModified() returns the timestamp in local time.
> Verified with Felix and Equinox.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)