[
https://issues.apache.org/jira/browse/DIRSTUDIO-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12702672#action_12702672
]
Stefan Seelmann commented on DIRSTUDIO-486:
-------------------------------------------
Hi Jürgen,
you are totally right, the version spec is required at the beginning of an LDIF
file, so it should always be added.
What I meant with "no sense" was the following:
- If you right-click on an entry and select Advanced->Copy Entry as LDIF only
one LDIF record is copied. I use this quite often to extract some sample data
from a directory to an LDIF file. I copy one entry and paste it into an LDIF
file, then the second and the third and so on. In that case I don't want the
version spec on top of each LDIF record.
- The modification logs is a rolling log file. On each modification another
LDIF fragment is added to the log. So I think in that case it makes no sense to
add the version spec in front of each LDIF fragment.
So IMHO the version spec should be added when producing complete LDIF files,
but not for LDIF fragments.
> Include Version Specifier in LDIF export
> ----------------------------------------
>
> Key: DIRSTUDIO-486
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-486
> Project: Directory Studio
> Issue Type: Bug
> Affects Versions: 1.4.0
> Reporter: Jürgen Weber
> Assignee: Stefan Seelmann
> Fix For: 1.5.0
>
>
> Studio does not include a Version Specifier ("version: 1") in the generated
> LDIF export
> (see http://www.novell.com/coolsolutions/feature/5997.html -> LDIF Content
> Records)
> E.g. the Novell LDAP classes for Java will not accept an LDIF that does not
> contain the Version Specifier.
> Perhaps Studio could make this optional, e.g. by a setting on the Text
> formats preferences page:
> [x] add Version Specifier
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
