[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [m2e-users] SVN Checkouts failing due to process locks caused by m2e
|
I used to use subclipse, but there were some things I didn't like about
it, some merges got messed up and I decided to try subversive instead.
I've never gone back, but I can't honestly say that one is any better
than the other. Subversive has also been improved. It used to lack the
feature of tagging revisions to more than one project with a single
revision number, something subclipse had first, but now subversive has
it too.
In any case, this issue is not really about that. It's about what
eclipse and/or m2e does when confronted with new code placed in its
workspace by the SCM client, whichever one it is.
On 10/27/2011 06:19 PM, Stephen Coy wrote:
Personally, I've found subclipse to be considerably more robust than subversive. The subversive synchronisation view in particular was a real PITA.
YMMV,
Steve C
On 28/10/2011, at 9:45 AM, Steve Cohen wrote:
OK, will keep my eye on this. I know SVN Repo is provided by subversive but wasn't sure what all the interactions were.
Do you think it is preferable to use SCM plugin for checkouts in eclipse? I have now installed m2eclipse-subversive.
On 10/27/2011 03:03 PM, Igor Fedorenko wrote:
FYI, SVN Repository Perspective is provided by Subversive.
In any case, I do not have a good explanation of this behaviour. If I
understand you correctly, you have workspace autobuild off, which means
there should be no build after project import. Something else makes
changes to workspace, but I don't know what that might be.
Even if you do have autobuild on, I still doubt the problem is caused by
m2e. Eclipse platform acquires workspace exclusive lock for entire
duration of the build, and this lock should guarantee exclusive
workspace access for all involved builders. It is simply impossible for
m2e builder to make workspace modifications outside of that exclusive lock.
--
Regards,
Igor
On 11-10-26 3:47 PM, Steve Cohen wrote:
Guess I did not make myself clear.
I was not using the SCM plugin at all.
Rather, I used subversive to check out a branch into my eclipse
workspace (SVN Repository Perspective -> Check out).
Eclipse immediately started to do some build stuff (I presume it was
code generation) resulting in the error that another process had the
folder locked so that the checkout could not complete. This was in spite
of the fact that automatic build was turned off.
On 10/26/2011 01:55 PM, Igor Fedorenko wrote:
I am not sure I understand. From your original question and the stack
trace you provided in another email you are using subversive plugin,
which is the scm plugin m2e-subversive integrates with.
--
Regards,
Igor
On 11-10-26 2:14 PM, Steve Cohen wrote:
On looking up m2eclipse-subversive, I see that it's primarily designed
for the scm plugin, which I have never used, so I have doubts that its
absence is relevant here.
Or should I be using that plugin?
On 10/26/2011 12:39 PM, Steve Cohen wrote:
Thanks, Igor.
m2e: 1.0.100.20110804-1717
subversive: 0.7.9.I20110819-1700
m2eclipse-subvestive: Had not heard of that one. Is that spelled
right?
(if it's m2eclipse-subversive, I hadn't heard of that either). Perhaps
that is my problem. However it's spelled, where do I find it?
The problem is reproducible but intermittent. I was eventually able to
overcome it by repetition.
Steve
On 10/26/2011 11:46 AM, Igor Fedorenko wrote:
This does not provide enough information to be able to tell anything
specific.
What are exact versions of m2e, subversive and
m2eclipse-subvestive do
you use?
Do you get any exceptions?
Is the problem reproducible or intermittent? What are exact steps to
reproduce the problem?
As a workaround, you can always do the checkout on command line, then
use import as maven project wizard to import the projects in your
workspace.
--
Regards,
Igor
On 11-10-26 12:08 PM, Steve Cohen wrote:
I am trying to check out a set of projects on a new branch I just
created in SVN (subversive plugin). Checkout is failing with a
message
the folder is locked by some external process. That external process
can
only be m2e generating code - I haven't done anything with these
folders
in weeks. Even though I have set eclipse to not build
automatically, it
is doing something. I have seen m2e do some build operations
previously,
even though this option was off. These were not serious problems
before,
now they are.
How can this be addressed?
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users
