[jira] Created: (MRM-1162) nexus.index.time always set to 19700101010000.000+0100

View: New views
8 Messages — Rating Filter:   Alert me  

[jira] Created: (MRM-1162) nexus.index.time always set to 19700101010000.000+0100

by JIRA jira@codehaus.org :: Rate this Message:

Reply (Restricted by the Administrator) | Reply to Author | View Threaded | Show Only this Message

nexus.index.time always set to 19700101010000.000+0100
------------------------------------------------------

                 Key: MRM-1162
                 URL: http://jira.codehaus.org/browse/MRM-1162
             Project: Archiva
          Issue Type: Bug
          Components: indexing
    Affects Versions: 1.2
            Reporter: michael gantert


Hi,
I made an upgrade from 1.1.2 to 1.2. If I scan my repository and look afterwards in the generated nexus index properties file there is always has the wrong timestamp (nexus.index.time) set:
----------
#Wed Apr 01 09:22:43 CEST 2009
nexus.index.time=19700101010000.000 +0100
nexus.index.id=snapshots-third-party


--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[jira] Updated: (MRM-1162) nexus.index.time always set to 19700101010000.000+0100

by JIRA jira@codehaus.org :: Rate this Message:

Reply (Restricted by the Administrator) | Reply to Author | View Threaded | Show Only this Message


     [ http://jira.codehaus.org/browse/MRM-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maria Odea Ching updated MRM-1162:
----------------------------------

    Fix Version/s: 1.2.1

> nexus.index.time always set to 19700101010000.000+0100
> ------------------------------------------------------
>
>                 Key: MRM-1162
>                 URL: http://jira.codehaus.org/browse/MRM-1162
>             Project: Archiva
>          Issue Type: Bug
>          Components: indexing
>    Affects Versions: 1.2
>            Reporter: michael gantert
>             Fix For: 1.2.1
>
>
> Hi,
> I made an upgrade from 1.1.2 to 1.2. If I scan my repository and look afterwards in the generated nexus index properties file there is always has the wrong timestamp (nexus.index.time) set:
> ----------
> #Wed Apr 01 09:22:43 CEST 2009
> nexus.index.time=19700101010000.000 +0100
> nexus.index.id=snapshots-third-party

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[jira] Commented: (MRM-1162) nexus.index.time always set to 19700101010000.000+0100

by JIRA jira@codehaus.org :: Rate this Message:

Reply (Restricted by the Administrator) | Reply to Author | View Threaded | Show Only this Message


    [ http://jira.codehaus.org/browse/MRM-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=171804#action_171804 ]

Michael K commented on MRM-1162:
--------------------------------

I made the same experience, but when I touch anyone file in the repository and do scanning of repository via Archiva once again, the nexus.index.time is correct.
But unfortunatelly the  repository index  in the eclipse-view 'Maven Indexes' doesn't run properly anyway.

> nexus.index.time always set to 19700101010000.000+0100
> ------------------------------------------------------
>
>                 Key: MRM-1162
>                 URL: http://jira.codehaus.org/browse/MRM-1162
>             Project: Archiva
>          Issue Type: Bug
>          Components: indexing
>    Affects Versions: 1.2
>            Reporter: michael gantert
>             Fix For: 1.2.1
>
>
> Hi,
> I made an upgrade from 1.1.2 to 1.2. If I scan my repository and look afterwards in the generated nexus index properties file there is always has the wrong timestamp (nexus.index.time) set:
> ----------
> #Wed Apr 01 09:22:43 CEST 2009
> nexus.index.time=19700101010000.000 +0100
> nexus.index.id=snapshots-third-party

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[jira] Commented: (MRM-1162) nexus.index.time always set to 19700101010000.000+0100

by JIRA jira@codehaus.org :: Rate this Message:

Reply (Restricted by the Administrator) | Reply to Author | View Threaded | Show Only this Message


    [ http://jira.codehaus.org/browse/MRM-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=171807#action_171807 ]

michael gantert commented on MRM-1162:
--------------------------------------

After some rebuilding of the index by Archiva the timestamp was correct, but than, as you mentioned, the index is not working with m2eclipse (unknown format: -7)...


> nexus.index.time always set to 19700101010000.000+0100
> ------------------------------------------------------
>
>                 Key: MRM-1162
>                 URL: http://jira.codehaus.org/browse/MRM-1162
>             Project: Archiva
>          Issue Type: Bug
>          Components: indexing
>    Affects Versions: 1.2
>            Reporter: michael gantert
>             Fix For: 1.2.1
>
>
> Hi,
> I made an upgrade from 1.1.2 to 1.2. If I scan my repository and look afterwards in the generated nexus index properties file there is always has the wrong timestamp (nexus.index.time) set:
> ----------
> #Wed Apr 01 09:22:43 CEST 2009
> nexus.index.time=19700101010000.000 +0100
> nexus.index.id=snapshots-third-party

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[jira] Assigned: (MRM-1162) nexus.index.time always set to 19700101010000.000+0100

by JIRA jira@codehaus.org :: Rate this Message:

Reply (Restricted by the Administrator) | Reply to Author | View Threaded | Show Only this Message


     [ http://jira.codehaus.org/browse/MRM-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maria Odea Ching reassigned MRM-1162:
-------------------------------------

    Assignee: Maria Odea Ching

> nexus.index.time always set to 19700101010000.000+0100
> ------------------------------------------------------
>
>                 Key: MRM-1162
>                 URL: http://jira.codehaus.org/browse/MRM-1162
>             Project: Archiva
>          Issue Type: Bug
>          Components: indexing
>    Affects Versions: 1.2
>            Reporter: michael gantert
>            Assignee: Maria Odea Ching
>             Fix For: 1.2.1
>
>
> Hi,
> I made an upgrade from 1.1.2 to 1.2. If I scan my repository and look afterwards in the generated nexus index properties file there is always has the wrong timestamp (nexus.index.time) set:
> ----------
> #Wed Apr 01 09:22:43 CEST 2009
> nexus.index.time=19700101010000.000 +0100
> nexus.index.id=snapshots-third-party

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[jira] Updated: (MRM-1162) nexus.index.time always set to 19700101010000.000+0100

by JIRA jira@codehaus.org :: Rate this Message:

Reply (Restricted by the Administrator) | Reply to Author | View Threaded | Show Only this Message


     [ http://jira.codehaus.org/browse/MRM-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maria Odea Ching updated MRM-1162:
----------------------------------

    Fix Version/s:     (was: 1.2.1)
                   1.2.2

> nexus.index.time always set to 19700101010000.000+0100
> ------------------------------------------------------
>
>                 Key: MRM-1162
>                 URL: http://jira.codehaus.org/browse/MRM-1162
>             Project: Archiva
>          Issue Type: Bug
>          Components: indexing
>    Affects Versions: 1.2
>            Reporter: michael gantert
>            Assignee: Maria Odea Ching
>             Fix For: 1.2.2
>
>
> Hi,
> I made an upgrade from 1.1.2 to 1.2. If I scan my repository and look afterwards in the generated nexus index properties file there is always has the wrong timestamp (nexus.index.time) set:
> ----------
> #Wed Apr 01 09:22:43 CEST 2009
> nexus.index.time=19700101010000.000 +0100
> nexus.index.id=snapshots-third-party

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[jira] Commented: (MRM-1162) nexus.index.time always set to 19700101010000.000+0100

by JIRA jira@codehaus.org :: Rate this Message:

Reply (Restricted by the Administrator) | Reply to Author | View Threaded | Show Only this Message


    [ http://jira.codehaus.org/browse/MRM-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=180274#action_180274 ]

michael gantert commented on MRM-1162:
--------------------------------------

With Archiva 1.2.1 and current version of m2eclipse plugin i can use the index without problems

> nexus.index.time always set to 19700101010000.000+0100
> ------------------------------------------------------
>
>                 Key: MRM-1162
>                 URL: http://jira.codehaus.org/browse/MRM-1162
>             Project: Archiva
>          Issue Type: Bug
>          Components: indexing
>    Affects Versions: 1.2
>            Reporter: michael gantert
>            Assignee: Maria Odea Ching
>             Fix For: 1.2.2
>
>
> Hi,
> I made an upgrade from 1.1.2 to 1.2. If I scan my repository and look afterwards in the generated nexus index properties file there is always has the wrong timestamp (nexus.index.time) set:
> ----------
> #Wed Apr 01 09:22:43 CEST 2009
> nexus.index.time=19700101010000.000 +0100
> nexus.index.id=snapshots-third-party

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[jira] Closed: (MRM-1162) nexus.index.time always set to 19700101010000.000+0100

by JIRA jira@codehaus.org :: Rate this Message:

Reply (Restricted by the Administrator) | Reply to Author | View Threaded | Show Only this Message


     [ http://jira.codehaus.org/browse/MRM-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maria Odea Ching closed MRM-1162.
---------------------------------

       Resolution: Cannot Reproduce
    Fix Version/s:     (was: 1.2.2)

The index time was fixed after upgrading the nexus indexer in Archiva 1.2.1.

> nexus.index.time always set to 19700101010000.000+0100
> ------------------------------------------------------
>
>                 Key: MRM-1162
>                 URL: http://jira.codehaus.org/browse/MRM-1162
>             Project: Archiva
>          Issue Type: Bug
>          Components: indexing
>    Affects Versions: 1.2
>            Reporter: michael gantert
>            Assignee: Maria Odea Ching
>
> Hi,
> I made an upgrade from 1.1.2 to 1.2. If I scan my repository and look afterwards in the generated nexus index properties file there is always has the wrong timestamp (nexus.index.time) set:
> ----------
> #Wed Apr 01 09:22:43 CEST 2009
> nexus.index.time=19700101010000.000 +0100
> nexus.index.id=snapshots-third-party

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira