[magnolia-dev] [JIRA] Updated: (MAGNOLIA-2969) Enhance magnolia propertiesImportExporter to handle Dates, and to export to a properties file
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-2969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grégory Joseph updated MAGNOLIA-2969: - Fix Version/s: Green (was: 4.3) Pushing this to the next version, sorry. Enhance magnolia propertiesImportExporter to handle Dates, and to export to a properties file - Key: MAGNOLIA-2969 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2969 Project: Magnolia Issue Type: Improvement Components: core Affects Versions: 4.2.1 Reporter: Ryan Gardner Assignee: Grégory Joseph Fix For: Green Attachments: enhancePropertyExporting2.patch, propertiesExporting3.patch In my opinion, one of the biggest hassles in creating a unit test for something that is driven by data in a repository is creating the properties file to drive the test. There was a mostly-implemented properties exporter in core but it didn't support writing out the data in the same format that it reads it in (namely, it didn't write the @uuid information or the @type information that it supports when importing from a properties file) This patch enhances the importer / exporter to the point where you can dump out content to a Properties or to a string representation of the properties. In addition, the Date nodes weren't dumped properly before. I added in some basic support for dumping and retrieving the Calendar objects from the properties file. I think that this, combined with another patch I'm about to submit that adds a dump to properties format to the JCR Queries page in Admin Interface should greatly reduce the pain for creating unit tests that operate using data from a repository. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-2969) Enhance magnolia propertiesImportExporter to handle Dates, and to export to a properties file
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-2969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grégory Joseph updated MAGNOLIA-2969: - Fix Version/s: 4.3 Enhance magnolia propertiesImportExporter to handle Dates, and to export to a properties file - Key: MAGNOLIA-2969 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2969 Project: Magnolia Issue Type: Improvement Components: core Affects Versions: 4.2.1 Reporter: Ryan Gardner Assignee: Grégory Joseph Fix For: 4.3 Attachments: enhancePropertyExporting2.patch, propertiesExporting3.patch In my opinion, one of the biggest hassles in creating a unit test for something that is driven by data in a repository is creating the properties file to drive the test. There was a mostly-implemented properties exporter in core but it didn't support writing out the data in the same format that it reads it in (namely, it didn't write the @uuid information or the @type information that it supports when importing from a properties file) This patch enhances the importer / exporter to the point where you can dump out content to a Properties or to a string representation of the properties. In addition, the Date nodes weren't dumped properly before. I added in some basic support for dumping and retrieving the Calendar objects from the properties file. I think that this, combined with another patch I'm about to submit that adds a dump to properties format to the JCR Queries page in Admin Interface should greatly reduce the pain for creating unit tests that operate using data from a repository. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-2969) Enhance magnolia propertiesImportExporter to handle Dates, and to export to a properties file
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-2969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan Gardner updated MAGNOLIA-2969: --- Attachment: propertiesExporting3.patch This version adds support for exporting metadata and cleans up the previous export slightly. Enhance magnolia propertiesImportExporter to handle Dates, and to export to a properties file - Key: MAGNOLIA-2969 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2969 Project: Magnolia Issue Type: Improvement Components: core Affects Versions: 4.2.1 Reporter: Ryan Gardner Assignee: Grégory Joseph Attachments: enhancePropertyExporting2.patch, propertiesExporting3.patch In my opinion, one of the biggest hassles in creating a unit test for something that is driven by data in a repository is creating the properties file to drive the test. There was a mostly-implemented properties exporter in core but it didn't support writing out the data in the same format that it reads it in (namely, it didn't write the @uuid information or the @type information that it supports when importing from a properties file) This patch enhances the importer / exporter to the point where you can dump out content to a Properties or to a string representation of the properties. In addition, the Date nodes weren't dumped properly before. I added in some basic support for dumping and retrieving the Calendar objects from the properties file. I think that this, combined with another patch I'm about to submit that adds a dump to properties format to the JCR Queries page in Admin Interface should greatly reduce the pain for creating unit tests that operate using data from a repository. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-2969) Enhance magnolia propertiesImportExporter to handle Dates, and to export to a properties file
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-2969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan Gardner updated MAGNOLIA-2969: --- Attachment: enhancePropertyExporting2.patch This updated version supports filtering with a contentfilter and uses the same dateformat used in the JCR. Enhance magnolia propertiesImportExporter to handle Dates, and to export to a properties file - Key: MAGNOLIA-2969 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2969 Project: Magnolia Issue Type: Improvement Components: core Affects Versions: 4.2.1 Reporter: Ryan Gardner Assignee: Philipp Bärfuss Attachments: enhancePropertyExporting2.patch In my opinion, one of the biggest hassles in creating a unit test for something that is driven by data in a repository is creating the properties file to drive the test. There was a mostly-implemented properties exporter in core but it didn't support writing out the data in the same format that it reads it in (namely, it didn't write the @uuid information or the @type information that it supports when importing from a properties file) This patch enhances the importer / exporter to the point where you can dump out content to a Properties or to a string representation of the properties. In addition, the Date nodes weren't dumped properly before. I added in some basic support for dumping and retrieving the Calendar objects from the properties file. I think that this, combined with another patch I'm about to submit that adds a dump to properties format to the JCR Queries page in Admin Interface should greatly reduce the pain for creating unit tests that operate using data from a repository. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
