Menu
▾
▴
#29 Floggy Eclipse Plugin causes continuous building
This bug has been described in: ID: 2517536
I am using Eclipse 3.5 whit Floggy 1.3.1 and EclipseME/MTJ if you "Add Floggy Nature" to a project, it causes Eclipse to continually rebuild the project without stopping. In order to make this behavior stop, you have to turn off "Build Automatically."
It looks like the fix was not successful or the problem has come back
Hi Tobias, what version of EclipseME/MTJ are you using??
Hi Thiago,
I am using Eclipse 3.5 under jdk1.5.0_22 because I got also the Blackberry plugin installed. MJT is 1.0.1
Is there maybe anything I could do to help to debug this?
Cheers,
Tobias
Automatic builds are a little problematic, the difficulty being is that when any builder runs it can result in some resource being modified. When this happens an automatic build is triggered. In the case of floggy/mjt what seems to happen is that (for example) both builders trigger automatic builds and so this loop occurs.
Previously we had some code that looked at the build delta and decided if a build was necessary, but for a while it seemed redundant and so it was removed... I also seem to recall that there was a problem with mjt packaging, but can't recall the details.
It might be appropriate to re-implement the check to see if the floggy build really needs to do anything and so hopefully avoid the infinite build loop...
Hi Dan, sounds like I have exactly the problem that you describe. Maybe the fix in ID: 2517536 can solve the issue?
Cheers, Tobias
Hi Tobias,
Could you provides us the .project file of your project? Are you working with Floggy and BlabkBerry in the same project?
Hi Thiago,
I could not manage to set up floggy with the Blackberry plugin. So for the Blackberry version I am now using their persistence API. Before I used Netbeans and there I did not have this problem.
So basically the build in cylces occurs with a J2ME project. Here is the configuration:
<?xml version="1.0" encoding="UTF-8"?>
<projectDescription>
<name>checkmytripJ2ME</name>
<comment></comment>
<projects>
</projects>
<buildSpec>
<buildCommand>
<name>org.eclipse.jdt.core.javabuilder</name>
<arguments>
</arguments>
</buildCommand>
<buildCommand>
<name>net.sourceforge.floggy.floggyBuilder</name>
<arguments>
</arguments>
</buildCommand>
<buildCommand>
<name>org.eclipse.mtj.core.preverifier</name>
<arguments>
</arguments>
</buildCommand>
<buildCommand>
<name>org.eclipse.mtj.core.packageBuilder</name>
<arguments>
</arguments>
</buildCommand>
</buildSpec>
<natures>
<nature>org.eclipse.jdt.core.javanature</nature>
<nature>org.eclipse.mtj.core.nature</nature>
<nature>net.sourceforge.floggy.floggyNature</nature>
</natures>
<linkedResources>
<link>
<name>assets_common</name>
<type>2</type>
<location>D:/eclipse/workspace/Assets/assets</location>
</link>
<link>
<name>src_common</name>
<type>2</type>
<location>D:/eclipse/workspace/Common/src</location>
</link>
</linkedResources>
</projectDescription>
Hi,
I just wonder if there are any news on this issue? Can I do something to help investigate this bug?
Cheers,
Toby
Hello,
We are still quite disturbed by this bug and I wonder if a solution was found? Please do not hesitate to tell me if there is any more help we can provide to get this resolved.
Cheers,
Toby
I was very sad when the error was still there after update to 1.4.0 it is really a big pain to not be able to use automatic build due to this bug....
Sorry Tobias, I have to hold my hands up to dropping the ball on this. We recently had our first child and didn't appreciate that 1.4.0 was about to be released. My bad.
I'm doing some testing on a new fix for this problem, but reliably reproducing the problem (for me) is not easy (in osx it seems that the loop is not infinite). If all goes well, would you be willing / able to test the fix ? Currently I'm testing on Helios (3.6) and if this goes well I will test on Ganymede (3.5).
How does this sound to you ?
Hello Dan,
congratulations for your child. I wish you and your family the very best!!!
Sorry for bothering you with this issue.
I have downloaded Eclipse Helios and I installed the latest MTJ 1.1.1 .. and I still got the issue :-(
I thought it might me my project so I created a new Hello World MIDLET and added Floggy nature to it. And the problem is there. :-(
I tried to change the order of the builders but it does not change a thing. As soon as I disable the Floggy builder the problem is gone.
Please tell me if there is something else I can do to spot the reason for this problem?
Cheers,
Toby
Hi Toby,
I'm not altogether surprised that you are also seeing the problem on Helios. Automatic builds are great for developers but not fun for plug-in coders !
I have tried testing on my machine, but am finding it hard to reproduce the problem easily...
I think the problem normally only happens on higher spec machines, what is your system spec (and what OS) ?
I've made a commit which should reduce the changes of a build loop, but there is still a chance that under some circumstances it might still loop.
Would you be willing to test it for us ?