New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FedoraLdp [PREVIEW] #492
Closed
Closed
FedoraLdp [PREVIEW] #492
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* See the License for the specific language governing permissions and | ||
* limitations under the License. | ||
*/ | ||
package org.fcrepo.http.api; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some day, we should move this to a new module for just LDP things (and make -http-api required it).
Fedora nodes refactor
Updated Modeshape to Beta2, which required mock object updates
The specific functionality that's causing the symptom noted in PT # 79728226 was introduced via commit 068c346 Rationale for the PR: ReadOnlyExternalPropertiesFedoraFileSystemConnectorIT fails when trying to delete a file generated when running BasicReadWriteFedoraFileSystemConnectorIT. The former makes no use of this file, and hence shouldn't try to delete it (indirectly via AbstractFedoraFileSystemConnectorIT). This fixes the specific build error that result from attempting to delete a file that's still held on by another Java process. The file lock was observed on Windows Java 7u67 (and 7u25). I used the Windows handle command to see that the file was indeed being held open by a java process. I was unable to get further details about which thread was holding the file open. As this seems to be a common problem on Windows, it's not clear to me whether this is worth investigating.
cbeer
force-pushed
the
ldp-resource
branch
2 times, most recently
from
October 2, 2014 15:16
f9b7f49
to
4ffb2be
Compare
…es in the response
… other preferences
…nclude a link to the description/binary
resource would conflict
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.