No problem at all. I thought we could fix it in 1.0.x too for a short while
until it just hit me right now that this is not possible.
On 2/13/07, Emmanuel Lecharny (JIRA) <jira@apache.org> wrote:
>
>
> [
> https://issues.apache.org/jira/browse/DIRSERVER-852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472807]
>
> Emmanuel Lecharny commented on DIRSERVER-852:
> ---------------------------------------------
>
> Yeah, you are plain right.
>
> This is only a problem (and even ...) on 1.5.0. But we have to investigate
> it further.
> This issue has nothing to do with 1.0.1. My bad
>
> > CreateTimestamp and ModifyTimestamp are sill using the startupTime of
> the server
> >
> --------------------------------------------------------------------------------
> >
> > Key: DIRSERVER-852
> > URL: https://issues.apache.org/jira/browse/DIRSERVER-852
> > Project: Directory ApacheDS
> > Issue Type: Bug
> > Affects Versions: 1.0.2, 1.0.1
> > Reporter: Emmanuel Lecharny
> > Assigned To: Alex Karasulu
> > Fix For: 1.5.0
> >
> >
> > The server still use the server starting time to feed those two fields.
> We should use the current time instead of this static date.
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>
|