[jboss-dev] Re: Locks on eclipse files in svn

[Andrew Lee Rubinger]

BTW, Adrian, in EJB3 we use the convention of the m2eclipse Plugin via:

"mvn eclipse:m2eclipse -Peclipse"

...where the "eclipse" profile ensures that we don't allow the Eclipse 
compiler's output to leak into something that may get published/deployed.

Again, I'm against the convention of publishing IDE-specific files in 
SVN for just this reason: each developer should be free to generate the 
metadata that best suits him/her.  Otherwise we'll get conflicts like 
this (Adrian regens as eclipse:eclipse, we do it some other way, etc...)

S,
ALR

Adrian Brock wrote:
> Andrew,
> 
> You appear to have an old lock on some eclipse files in svn
> can you remove it? I'm trying to update trunk to use the
> mvn eclipse:eclipse generated files now that the project is
> fully mavenised.
> 
> $ svn info https://svn.jboss.org/repos/jbossas/trunk/ejb3/.project
> Path: .project
> Name: .project
> URL: https://svn.jboss.org/repos/jbossas/trunk/ejb3/.project
> Repository Root: https://svn.jboss.org/repos/jbossas
> Repository UUID: 84be2c1e-ba19-0410-b317-a758671a6fc1
> Revision: 89010
> Node Kind: file
> Last Changed Author: ejort
> Last Changed Rev: 29674
> Last Changed Date: 2005-03-22 19:37:16 +0100 (Tue, 22 Mar 2005)
> Lock Token: opaquelocktoken:cc9885ac-c73c-0410-839a-d44aa957f212
> Lock Owner: ALRubinger
> Lock Created: 2007-10-18 19:23:17 +0200 (Thu, 18 Oct 2007)
> Lock Comment (1 line):
> 

-- 
Andrew Lee Rubinger
Sr. Software Engineer
JBoss, a division of Red Hat, Inc.
http://exitcondition.alrubinger.com