[ https://jira.jboss.org/browse/SHRINKWRAP-232?page=com.atlassian.jira.plug... ] Dan Allen updated SHRINKWRAP-232: --------------------------------- Description: The Archive#delete(ArchivePath) operation should return the Asset (or Node) being removed (at the specified ArchivePath) rather than returning boolean. This both avoids having to have an extra call to get the asset before removing it, and it's consistent with the familiar behavior of the JDK Map API. // Removes the Asset in the archive at the specified Path and returns the removed Asset Node delete(ArchivePath path); The only thing I'm not sure about is whether the Asset return type is sufficient for when you delete a directory path. was: The Archive#delete(ArchivePath) operation should return the Asset (or Node) being removed (at the specified ArchivePath) rather than returning boolean. This both avoids having to have an extra call to get the asset before removing it, and it's consistent with the familiar behavior of the JDK Map API. // Removes the Asset in the archive at the specified Path and returns the removed Asset Asset delete(ArchivePath path); The only thing I'm not sure about is whether the Asset return type is sufficient for when you delete a directory path. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/SHRINKWRAP-232?page=com.atlassian.jira.pl... ] Andrew Rubinger resolved SHRINKWRAP-232. ---------------------------------------- Assignee: Andrew Rubinger Resolution: Done -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira