www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Blevins (JIRA)" <j...@apache.org>
Subject [jira] Commented: (INFRA-1807) Retrieving history (for a patch) receives an error from SVN server
Date Tue, 13 Jan 2009 22:59:02 GMT

    [ https://issues.apache.org/jira/browse/INFRA-1807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12663524#action_12663524

David Blevins commented on INFRA-1807:

I understand their logic in thinking it's not an IntelliJ issue, but by the same form of logic
it can be.  Leaving the jvm and repo in the control group and simply switching from one IntelliJ
version to the next (Ralph 7.0.5 <-> 8.0.1, Me 5.1.2 <-> 8.0.1) can cause or fix
this issue.  I hope they look into what they might be doing differently between 8.0.x and
the older versions.

Unrelated to the jetbrains response, I spoke too soon on the comment I made about upgrading
to svn 1.5 fixing the issue -- it didn't after all.

> Retrieving history (for a patch) receives an error from SVN server
> ------------------------------------------------------------------
>                 Key: INFRA-1807
>                 URL: https://issues.apache.org/jira/browse/INFRA-1807
>             Project: Infrastructure
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Subversion
>         Environment: mac os x, intellij idea 8.0.1
>            Reporter: Howard M. Lewis Ship
>            Assignee: Norman Maurer
> I consistently get the following error when I try to do a patch from within IDEA:
> Failed to load patch base revision for file tapestry-core/src/main/java/org/apache/tapestry5/services/TapestryModule.java:
svn: chunked stream ended unexpectedly
> svn: REPORT request failed on '/repos/asf/!svn/bc/723002/tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/services/TapestryModule.java'
> I'm trying to determine what command IDEA was executing at the time of the failure.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message