Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 350608 - Error refreshing branches for org.eclipse.jpa
Summary: Error refreshing branches for org.eclipse.jpa
Status: RESOLVED DUPLICATE of bug 350734
Alias: None
Product: WTP Releng
Classification: WebTools
Component: releng (show other bugs)
Version: 3.10   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: webtools.releng CLA
QA Contact: David Williams CLA
URL:
Whiteboard:
Keywords:
Depends on: 350734
Blocks:
  Show dependency tree
 
Reported: 2011-06-28 12:13 EDT by Neil Hauge CLA
Modified: 2018-06-29 15:14 EDT (History)
4 users (show)

See Also:


Attachments
Problematic file (79 bytes, text/plain)
2011-06-29 08:22 EDT, Neil Hauge CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Neil Hauge CLA 2011-06-28 12:13:06 EDT
Developers are currently unable to check out the org.eclipse.jpa R3_0_maintenance branch code from CVS.  The Refresh Branches... operation is failing with the following exception:

java.lang.IllegalArgumentException: Revision malformed: branchRevision
	at org.eclipse.team.internal.ccvs.core.client.listeners.LogListener.getBranchRevision(LogListener.java:262)
	at org.eclipse.team.internal.ccvs.core.client.listeners.LogListener.messageLine(LogListener.java:199)
	at org.eclipse.team.internal.ccvs.core.client.Request.executeRequest(Request.java:207)
	at org.eclipse.team.internal.ccvs.core.client.Command.doExecute(Command.java:413)
	at org.eclipse.team.internal.ccvs.core.client.Command$1.run(Command.java:326)
	at org.eclipse.team.internal.ccvs.core.resources.EclipseSynchronizer.run(EclipseSynchronizer.java:1474)
	at org.eclipse.team.internal.ccvs.core.resources.EclipseResource$2.run(EclipseResource.java:262)
	at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344)
	at org.eclipse.team.internal.ccvs.core.resources.EclipseResource.run(EclipseResource.java:259)
	at org.eclipse.team.internal.ccvs.core.client.Command.execute(Command.java:338)
	at org.eclipse.team.internal.ccvs.core.client.Command.execute(Command.java:804)
	at org.eclipse.team.internal.ccvs.ui.operations.RemoteLogOperation.execute(RemoteLogOperation.java:272)
	at org.eclipse.team.internal.ccvs.ui.operations.RepositoryLocationOperation.execute(RepositoryLocationOperation.java:46)
	at org.eclipse.team.internal.ccvs.ui.operations.CVSOperation.run(CVSOperation.java:79)
	at org.eclipse.team.internal.ccvs.ui.repo.RepositoryRoot.fetchTagsUsingLog(RepositoryRoot.java:370)
	at org.eclipse.team.internal.ccvs.ui.repo.RepositoryRoot.refreshDefinedTags(RepositoryRoot.java:346)
	at org.eclipse.team.internal.ccvs.ui.repo.RepositoryManager.refreshDefinedTags(RepositoryManager.java:249)
	at org.eclipse.team.internal.ccvs.ui.repo.RefreshRemoteProjectWizard.internalRefresh(RefreshRemoteProjectWizard.java:143)
	at org.eclipse.team.internal.ccvs.ui.repo.RefreshRemoteProjectWizard.access$0(RefreshRemoteProjectWizard.java:136)
	at org.eclipse.team.internal.ccvs.ui.repo.RefreshRemoteProjectWizard$3.run(RefreshRemoteProjectWizard.java:118)
	at org.eclipse.team.internal.ccvs.ui.repo.RepositoryManager.run(RepositoryManager.java:717)
	at org.eclipse.team.internal.ccvs.ui.repo.RefreshRemoteProjectWizard$2.run(RefreshRemoteProjectWizard.java:111)
	at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
Comment 1 Neil Hauge CLA 2011-06-28 18:12:27 EDT
It appears this is caused by a regression in the platform CVS code.  The changes that have broken our refresh were introduced in the patch for bug 76386.

The file that is causing the problem can be found here:

dev.eclipse.org:/cvsroot/webtools/org.eclipse.jpa/components/jpa/plugins/org.eclipse.jpt.core/src/org/eclipse/jpt/core/internal/resource/orm/translators/EmbeddableAttributesTranslator.java

It is possible that this file is corrupted, and the new code is less tolerant of this, or the file may be perfectly valid in its nearly empty state.

I will see if removing this file alleviates the problem as a potential workaround.
Comment 2 David Williams CLA 2011-06-28 23:43:00 EDT
weird
Comment 3 Neil Hauge CLA 2011-06-29 08:20:25 EDT
It appears that above mentioned file is the only problematic one in our
repository.  Once moved out of the Attic the refresh command succeeds as
expected.  As this file is very old and appears to be empty anyway I am just
going to leave it out of the repo, at least until the underlying issue is
resolved.  So for now Refresh Branches should again succeed.
Comment 4 Neil Hauge CLA 2011-06-29 08:22:40 EDT
Created attachment 198822 [details]
Problematic file
Comment 5 Neil Hauge CLA 2011-06-29 14:01:52 EDT
Opened bug 350734 against platform.
Comment 6 David Williams CLA 2011-09-21 13:12:08 EDT
I assume there's nothing left for us in WTP to do. Thanks for reporting to platform cvs for their benefit.

*** This bug has been marked as a duplicate of bug 350734 ***