search

liptga / headlesseclipse

Automatically exported from code.google.com/p/headlesseclipse
0 stars 0 forks source link

Unable to force ignoring circular build path problems #12

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. have some plugin-projects with circular dependencies
2. switch "Window -> Preferences -> Java -> Compiler -> Building -> Build
path problems -> Circular dependencies" from "error" to "warning"

What is the expected output? What do you see instead?
I expect headlesseclipse to run with the "Circular build path problems"
settings kept to "warning" but when run with parameters "import build
exportplugins" it seems to set it back to "error":

---8<---*snip*---
> Circular build path problems: warning
> Circular build path problems set to: error
> 
> Incomplete build path problems: error
> Incomplete build path problems set to: warning
> 
> IMPORTING PROJECTS...
---8<---*snip*---

In my project the circular dependency is fine. Is there any way to force
the "warning" mode like it can be done in "GUI mode"?

What version of the product are you using? On what operating system?
HeadlessEclipse 1.1.8 com.ind.eclipse.headlesseclipse.feature.group

Original issue reported on code.google.com by m...@oclab.net on 6 Apr 2010 at 5:06

GoogleCodeExporter commented 9 years ago 
A new parameter will be introduced, like "allowcircularclasspath", but some 
testing 
should be made...

Original comment by laszlo.v...@gmail.com on 8 Apr 2010 at 8:22

GoogleCodeExporter commented 9 years ago 
I already had a look at the code and hard-wired the setting-change to 
"warning". The
new command-line parameter was the next thing in my queue. I planned to post the
patch here, after I found the time to "do it right".

Original comment by m...@oclab.net on 8 Apr 2010 at 9:31

GoogleCodeExporter commented 9 years ago 
Please have a look at the attached patch.

Original comment by m...@oclab.net on 8 Apr 2010 at 10:41

Attachments:

GoogleCodeExporter commented 9 years ago 
Obviously I did a mistake in my testing of the patch. Though it successfully 
changes
the appropriate setting, building of projects with circular dependencies fails 
in
some cases. Therefore the above patch has to be classified as nonsense or at 
least
"incomplete" ...

Original comment by maisel%s...@gtempaccount.com on 9 Apr 2010 at 4:52

GoogleCodeExporter commented 9 years ago 
Can you please send more information about the failures? It would help a lot to 
find a 
solution.

Original comment by laszlo.v...@gmail.com on 12 Apr 2010 at 8:09

GoogleCodeExporter commented 9 years ago 
I postet some info to the google-group some days ago:
http://groups.google.com/group/headlesseclipse/msg/8f891f190a0e2ab0

Currently I am stuck with this problem. Sadly the
"org.eclipse.core.runtime.AssertionFailedException" (see group thread) I 
stumbled
upon seems not to be related to this issue ...

Any hints how to debug / where to look for error-messages?

Original comment by maisel%s...@gtempaccount.com on 12 Apr 2010 at 10:36

GoogleCodeExporter commented 9 years ago 
The last weeks were pretty busy, but nevertheless I'd like to share the 
solution I finally found. On the one hand I extended the patch to allow for 
circular classpaths in the projects that are to be built (see 
allowcircularclasspath_final.patch). The exporterclass had a limitation that 
made my builds fail, since I use custom directory-names. The exporter 
previously ignored projects that reside in directories not named with the 
project name (see pluginexporter.patch). Both patches are based on "revision 
releases/1.1.8".

Original comment by maisel%s...@gtempaccount.com on 20 Aug 2010 at 3:45

Attachments: