hi brian
i didn't even think to open jira issues for the various things we've
discussed on the list, but that seems like a good idea, so i'll start
diong that.
yes... i think that would be fine.
- keeping track of changes
- having a issue number for the commits
- easier to find discussions related to a particular
modifications
- possibility to track if a discussion resulted in
commits (or was resolved 'wontdothat' ;).
- reminder for me ;)
if it's not a pain, that would be great for these particular changes. in
general, i don't think it's necessary.
done.
i attached a diff to JCR-174. but it contains all the
modifications not only those related to the etag issue.
the latter affects
contrib\jcr-server\server\src\java\org\apache\jackrabbit\server\io\PrimaryItemExportCommand.java
contrib\jcr-server\server\src\java\org\apache\jackrabbit\server\io\AbstractExportCommand.java
contrib\jcr-server\server\src\java\org\apache\jackrabbit\server\io\DirListingExportCommand.java
contrib\jcr-server\server\src\java\org\apache\jackrabbit\server\io\FileExportCommand.java
contrib\jcr-server\server\src\java\org\apache\jackrabbit\server\io\ExportContext.java
contrib\jcr-server\server\src\java\org\apache\jackrabbit\webdav\simple\DavResourceImpl.java
contrib\jcr-server\server\src\java\org\apache\jackrabbit\webdav\simple\NodeResource.java
contrib\jcr-server\webdav\src\java\org\apache\jackrabbit\webdav\WebdavRequestImpl.java
regards
angela
