You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Alex Karasulu (JIRA)" <ji...@apache.org> on 2009/08/25 02:00:59 UTC
[jira] Created: (DIRSHARED-34) LdifEntry.toString() should print
LDIF rather than diagnostic information
LdifEntry.toString() should print LDIF rather than diagnostic information
-------------------------------------------------------------------------
Key: DIRSHARED-34
URL: https://issues.apache.org/jira/browse/DIRSHARED-34
Project: Directory Shared
Issue Type: Improvement
Reporter: Alex Karasulu
Right now toString prints some diagnostic information about the LDIF: a pretty print thingy. It should instead print out the LDIF in the proper syntax. It should also have a write() method that takes a writer and/or a stream.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRSHARED-34) LdifEntry.toString() should print
LDIF rather than diagnostic information
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSHARED-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSHARED-34:
---------------------------------------
Fix Version/s: 0.9.20
(was: 1.0.0-RC1)
> LdifEntry.toString() should print LDIF rather than diagnostic information
> -------------------------------------------------------------------------
>
> Key: DIRSHARED-34
> URL: https://issues.apache.org/jira/browse/DIRSHARED-34
> Project: Directory Shared
> Issue Type: Improvement
> Reporter: Alex Karasulu
> Fix For: 0.9.20
>
>
> Right now toString prints some diagnostic information about the LDIF: a pretty print thingy. It should instead print out the LDIF in the proper syntax. It should also have a write() method that takes a writer and/or a stream.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (DIRSHARED-34) LdifEntry.toString() should print
LDIF rather than diagnostic information
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSHARED-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny resolved DIRSHARED-34.
----------------------------------------
Resolution: Fixed
Fixed a long time ago.
> LdifEntry.toString() should print LDIF rather than diagnostic information
> -------------------------------------------------------------------------
>
> Key: DIRSHARED-34
> URL: https://issues.apache.org/jira/browse/DIRSHARED-34
> Project: Directory Shared
> Issue Type: Improvement
> Reporter: Alex Karasulu
> Fix For: 1.0.0-RC1
>
>
> Right now toString prints some diagnostic information about the LDIF: a pretty print thingy. It should instead print out the LDIF in the proper syntax. It should also have a write() method that takes a writer and/or a stream.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRSHARED-34) LdifEntry.toString() should print
LDIF rather than diagnostic information
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSHARED-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSHARED-34:
---------------------------------------
Fix Version/s: 1.0.0-RC1
> LdifEntry.toString() should print LDIF rather than diagnostic information
> -------------------------------------------------------------------------
>
> Key: DIRSHARED-34
> URL: https://issues.apache.org/jira/browse/DIRSHARED-34
> Project: Directory Shared
> Issue Type: Improvement
> Reporter: Alex Karasulu
> Fix For: 1.0.0-RC1
>
>
> Right now toString prints some diagnostic information about the LDIF: a pretty print thingy. It should instead print out the LDIF in the proper syntax. It should also have a write() method that takes a writer and/or a stream.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.