Re: [Subclipse-users] Bug? "Entry already exists"

Did you try just doing a Refresh in Eclipse after the first commit
failed? All I can think of is the commit failing is causing the code
to refresh the status from not being triggered. So we still think the
files are unversioned as opposed to added. That would be the only
reason we would try to add the file again.

If you are just looking for a way to get this change committed, any
file that is showing this problem if you just open in Eclipse and add
a space/remove it and save that should force the status to be
refreshed.

Your other error about the folder is more suspicious. Unless you have
done more fiddling with your working copy then you are telling us,
that sounds like the original add did not succeed for the folder.
That would not be a Subclipse bug as we only call the API to do the
add and your previous log clearly shows we did that. It is up to the
Subversion API (JavaHL or SVNKit) to actually do the add correctly.
This is all done indepndent of the commit though, so I do not see how
a failed commit would impact the add at all.

Mark

On Wed, Apr 13, 2011 at 11:56 PM, Arpe, Kevin C
<Kevin.C.Arpe_at_jpmorgan.com> wrote:
> Hi,
>
>
>
> I am using Subclipse 1.6.17 with Eclipse Helios SR2 (20110301-1815).
>
> I ran "Install Software Updates" before doing this test again.
>
>
>
> Here is my scenario that fails.  I can reproduce everytime.
>
>
>
> In an SVN project in Eclipse:
>
> 1) Add a new file (anything is OK).
>
> 2) Team -> Commit…
>
> 3) Leave the message blank
>
> 4) Commit will fail because my repository has a hook to prevent empty
> messages.
>
>
>
> =======
>
> add -N C:\eclipse\workspace\JPM-AS400\meta
>
>     A         C:/eclipse/workspace/JPM-AS400/meta
>
> add -N C:\eclipse\workspace\JPM-AS400\meta\jar-export-for-ctstudio.jardesc
>
>     A
> C:/eclipse/workspace/JPM-AS400/meta/jar-export-for-ctstudio.jardesc
>
> commit -m "" C:/eclipse/workspace/JPM-AS400/.classpath
> C:/eclipse/workspace/JPM-AS400/meta
> C:/eclipse/workspace/JPM-AS400/meta/jar-export-for-ctstudio.jardesc
>
>     Sending        C:/eclipse/workspace/JPM-AS400/.classpath
>
>     Adding         C:/eclipse/workspace/JPM-AS400/meta
>
>     Adding
> C:/eclipse/workspace/JPM-AS400/meta/jar-export-for-ctstudio.jardesc
>
>     Transmitting file data ...
>
>     A repository hook failed
>
> svn: Commit failed (details follow):
>
> svn: Commit blocked by pre-commit hook (exit code 1) with output:
>
> Empty comments are not allowed.
>
> =======
>
>
>
> 5) Try the commit again.  Team -> Commit…
>
> 6) Enter a message
>
> 7) It fails with a new error message.
>
>
>
> =======
>
> add -N C:\eclipse\workspace\JPM-AS400\meta\jar-export-for-ctstudio.jardesc
>
>     Entry already exists
>
> svn: 'C:\eclipse\workspace\JPM-AS400\meta\jar-export-for-ctstudio.jardesc'
> is already under version control
>
> =======
>
>
>
> When I run svn status at the command line, the files are already added.
> Makes sense.  I need to run:
>
> svn delete --force --keep-local <added-files>
>
>
>
> Then I try commit again (with a message) and it works.
>
>
>
> Step 7 seems like a bug, or I am using Subclipse wrong.
>
>
>
> Can you please advise?
>
>
>
> Thanks,
>
> Arpe
>
>
>
> This email is confidential and subject to important disclaimers and
> conditions including on offers for the purchase or sale of securities,
> accuracy and completeness of information, viruses, confidentiality, legal
> privilege, and legal entity disclaimers, available at
> http://www.jpmorgan.com/pages/disclosures/email.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
------------------------------------------------------
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=2719750
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].