search

fredsa / forplay

Automatically exported from code.google.com/p/forplay
Apache License 2.0
12 stars 4 forks source link

Import project to eclipse failed #16

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. svn checkout the trunk source code
2. import the project to eclipse
3.

What is the expected output? What do you see instead?
i got lots of errors like this:
Description Resource    Path    Location    Type
org.jbox2d.dynamics.contacts.PositionSolverManifold can not be found in source 
packages. Check the inheritance chain from your module; it may not be 
inheriting a required module or a module may not be adding its source path 
entries 
properly.   ContactSolver.java  /forplay/gwtbox2d/org/jbox2d/dynamics/contacts  line
 784    GWT problems marker

What version of the product are you using? On what operating system?

Please provide any additional information below.

Original issue reported on code.google.com by leei...@gmail.com on 22 May 2011 at 5:43

GoogleCodeExporter commented 9 years ago 
I've checked, and I'm not seeing anything like this on a fresh checkout. Can 
you try syncing the repository and see if you still have this problem?

Original comment by jgw@google.com on 29 May 2011 at 12:35

GoogleCodeExporter commented 9 years ago 
Seems like I have the same kind of problem. I'm trying to import the projects 
from a fresh checkout.

First strange fact : when I tried to import all projects from "forplay" folder, 
there were two projects listed that had no name (or a blank name). I couldn't 
import anything until I unchecked those projects.

When the projects are imported, I have compilation errors in many projects. So 
I decided to start fixing the "core" : the "forplay" project.

=> First, my default GWT installation was 2.2, instead of 2.3 => The new GWT 
Storage file was not found. I switched GWT version and a few errors disappeared.

I still have a lot of red crosses however, that seem related to Flash stuff. 
All the errors are in the forplay.flash package (in the core project), and look 
like this :

forplay.flash.FlashSound can not be found in source packages. Check the 
inheritance chain from your module; it may not be inheriting a required module 
or a module may not be adding its source path entries properly.

Which is strange, since FlashSound is actually here, in the same package... and 
it happens for other classes as well.

The quickfix proposed by Eclipse is "Import GWT module forplay.ForPlay", or 
"Import GWT module flash.ActionScript". I tried both, and it doesn't help.

I guess there's some configuration problem...  maybe linked to the fact that I 
first imported the projects with GWT 2.2 ? I'm gonna try again and see what 
happens.

Original comment by py.ricau on 30 May 2011 at 12:03

GoogleCodeExporter commented 9 years ago 
The fastest way to fix it is to disable the ForPlayFlash module... 

=> I commented the "source" statements in ForPlayFlash.gwt.xml and rebuilt the 
project, and no more red crosses !

<!--   <source path='flash'/> -->
<!--   <public path='flash/as'/> -->

Original comment by py.ricau on 30 May 2011 at 12:12

GoogleCodeExporter commented 9 years ago 
Basically, here's what I've done to be able to import all ForPlay projects 
(core & sample) :

https://github.com/pyricau/forplay-clone-pyricau/commit/a8a99eee87f4f7b04ad7fec2
7a6c5bd3ea371fea

Original comment by py.ricau on 30 May 2011 at 12:19

GoogleCodeExporter commented 9 years ago 
Interesting -- can you tell which plugin is giving you these errors? They sound 
like the kind you'd normally get from the Google plugin for Eclipse, given that 
they're offering you the option to import GWT modules as quick-fixes. 
Strangely, though, I have this plugin as well, and the Flash stuff hasn't been 
a problem.

There's been some discussion of getting rid of these hand-built Eclipse 
projects and replacing them with projects auto-generated by maven. Perhaps that 
will help with the library reference issues (presuming that's what the problem 
is).

Sorry for the bumpy road -- we should be able to get this sorted out soon.

Original comment by jgw@google.com on 3 Jun 2011 at 2:23

GoogleCodeExporter commented 9 years ago

Original comment by jgw@google.com on 3 Jun 2011 at 2:23