[kepler-dev] Problems with Eclipse Install

Christopher Brooks cxh at eecs.berkeley.edu
Mon Oct 29 16:01:54 PDT 2007


Hi Derik,

Ok, after looking this, the problem is ptolemy/data/properties
includes ptolemy/codegen, which is excluded somewhere in the Kepler
build.  Yes, ptolemy/data/properties is not needed for Kepler, it is 
part of the PtHOMAS project (http://chess.eecs.berkeley.edu/pthomas).

Thus, the solution would be to exclude ptolemy/data/properties from
the Eclipse build of Kepler.

I think we need a nightly build target that builds Kepler under
Eclipse.

Building Ptolemy under Eclipse is somewhat annoying.  Building Kepler
and Ptolemy under Eclipse is _really_hard_.  Perhaps including a
.classpath.default file that could be copied would be a solution.


_Christopher

Dan writes:
--------

    At least a few of the error messages are due to code in 
    "ptolemy/data/properties/**" . This directory is excluded in the ant 
    build of Ptolemy (and is thus apparently not needed).
    
    Dan
    
    Derik Barseghian wrote:
    > Ken,
    >
    > Sorry for the delay. I was out on Friday and bumped into a numerous  
    > problems with getting cvs Kepler running under Eclipse on XP, but now  
    > have it up.
    >
    > Some of the problems I had to resolve:
    > 	- Eclipse had problems with reading ptII's tcljava.htm file  
    > (strange. A corrupt checkout from Friday? (...despite numerous  
    > syncs?) I simply deleted this file for now and that fixed that).
    >
    > 	-Eclipse suddenly stopped launching at one point until I deleted its  
    > configuration directory and moved eclipse to c:\eclipse (maybe it  
    > didn't like launching from my Desktop, a path with spaces in its name).
    >
    > 	- Had to change Kepler VM arguments (the paths) to have quotes  
    > around them, so spaces were understood.
    >
    > I'm running java 1.5 update 13.
    >
    > I get the same 11 errors you mention below, but like Izabell I am  
    > able to Proceed on the "Proceed with launch" dialog when I click Run  
    > and Kepler launches and runs fine. Do you not receive this option?  
    > Apologies if you've already said as such in another email...
    >
    > Derik
    >
    >
    > On Oct 27, 2007, at 5:32 PM, Izabell Caraconcea wrote:
    >
    >   
    >> Hello Ken,
    >> I installed Kepler few months ago and it worked fine with Eclipse  
    >> until yesterday.
    >> Yesterday I checked-out the newest available source code from CVS.
    >> Now I'm getting EXACTLY the same eleven errors you're getting when  
    >> you build the project.
    >> An update of JDK from 1.5.11 to 1.5.13 did not help.
    >> I'm using Eclipse 3.1.2
    >>
    >> Despite the errors, Kepler runs, displays the actors tree and  
    >> executes (simple) workflows. I don't understand that. Basic classes  
    >> in Ptolemy seem to be affected. Perhaps I will get stuck later,  
    >> with more complex workflows.
    >>
    >> Tonight I will be trying to create an independent project with my  
    >> own actors, then see whether I'm able to use them. Before, under  
    >> the old version of Kepler, I played (successfully) with the  
    >> beginner's actors (HelloWorld, Scale, etc) Afterwards I wanted to  
    >> develop specific actors within a new directory. The first actor did  
    >> not appear in the tree. It had a kar file, though. So, I decided to  
    >> update Kepler... now I got in trouble again :)
    >>
    >> Please, let me know if you will figure out a solution!!
    >> Same kind request to the developers of Kepler....
    >>
    >> Thank you very much,
    >> Izabell
    >>
    >>
    >> On 10/27/07, Kenneth Evans, Jr. <evans at aps.anl.gov > wrote: Hi,
    >>
    >> The build is not working for me, and I cannot continue to spend  
    >> this much
    >> time on it.  This is my status:
    >>
    >> 1. I have followed the instructions in "Using Eclipse for Kepler
    >> Development".
    >>
    >> 2. My checkout of kelper and ptII are synchronized with the  
    >> repository.
    >>
    >> 3. The classpath is almost certainly wrong.
    >>
    >> 4. I am using :pserver:anon:@source.eecs.berkley.edu.  This may be  
    >> different
    >> from the development server.  In addition, in between when I did  
    >> this the
    >> first time and later, I got CVS differences (now updated).  This  
    >> may be
    >> because the repository is changing or because MacAfee deleted  
    >> shutdown.bat
    >> as soon as it came in, possibly confusing CVS.  It seems it would  
    >> be better
    >> for people like me to check out from a stable TAG in any event.  In
    >> particular, keeping .classpath.default synchronized with ptII must be
    >> difficult.
    >>
    >> 5. The problem with shutdown.bat can apparently be fixed if the  
    >> arguments
    >> are reordered.  The following seem to work (according to my IT group):
    >>
    >> McAfee seems to only detect:
    >> "C:\WINDOWS\system32\shutdown -r -t 0 -f"
    >>
    >> and if you change the string slightly:
    >> "C:\WINDOWS\system32\shutdown -r -t 1 -f"
    >>
    >> or:
    >> "C:\WINDOWS\system32\shutdown -r -f -t 0"
    >>
    >> I cannot prevent the deletion at work, so fixing it so there is no  
    >> false
    >> positive would be good.
    >>
    >> 6. I have copied .classpath.default to .classpath per the  
    >> instructions.  I
    >> no longer have the ptII project added to the build path.
    >>
    >> 7.  I have run the ant build, as suggested, which failed.  The  
    >> reason, in
    >> part, is that it uses ${env.PTII}.  I don't have that environment  
    >> variable
    >> set.  I should not need to with the Eclipse setup, and I would  
    >> guess the ant
    >> build is not set up for the Eclipse instructions.  After running  
    >> the ant
    >> script, the errors I get have changed, so it apparently did  
    >> something.  In
    >> particular, I could not remove ptII from the required projects on  
    >> the build
    >> path before.  I would really like to work in Eclipse.  It is  
    >> becoming the
    >> IDE of choice these days.  I have got even larger projects running in
    >> Eclipse.  (With less trouble ;-)
    >>
    >> 8. I turned off three Error / Warnings on both _projects_ (not in  
    >> the Global
    >> Preferences are suggested in one article, since I fix those  
    >> warnings in my
    >> projects and want to know about them).  These were for  
    >> serialVersionUID and
    >> the first two for Generic Types. This reduced the warnings from  
    >> over 4000 to
    >> 2105.  This should probably be mentioned in the Eclipse instructions.
    >>
    >> 8. In the ptII project and in the link to it in the kelper project,  
    >> I now
    >> have both .class and .java files in the source directories.  The bin
    >> directory is not being used.  I checked the "Create separate source  
    >> and
    >> output folders" option when I checked it out.  (Actually, it is my  
    >> default
    >> and was already checked.)
    >>
    >> 9.  I get 11 errors currently:
    >>
    >> Severity and Description        Path    Resource        Location
    >> Creation Time   Id
    >> CodeGenerator cannot be resolved        kepler/ptII/ptolemy/data/ 
    >> properties
    >> PropertySolver.java     line 210        1193502384730   1690690
    >>
    >> Severity and Description        Path    Resource        Location
    >> Creation Time   Id
    >> The import ptolemy.codegen cannot be resolved
    >> kepler/ptII/ptolemy/data/properties     PropertySolver.java      
    >> line 13
    >> 1193502384730   1690689
    >>
    >> Severity and Description        Path    Resource        Location
    >> Creation Time   Id
    >> The method addTokenSentListener(FirstTokenSentListener) is  
    >> undefined for the
    >> type IOPort     kepler/ptII/ptolemy/data/properties/token
    >> PortValueSolver.java    line 99 1193502384555   1690666
    >>
    >> Severity and Description        Path    Resource        Location
    >> Creation Time   Id
    >> The method removeTokenSentListener(FirstTokenSentListener) is  
    >> undefined for
    >> the type IOPort kepler/ptII/ptolemy/data/properties/token
    >> PortValueSolver.java    line 137        1193502384555   1690667
    >>
    >> Severity and Description        Path    Resource        Location
    >> Creation Time   Id
    >> The type AtomicActor is already defined kepler/ptII/ptolemy/actor
    >> AtomicActor.java        Unknown 1193502394755   1691188
    >>
    >> Severity and Description        Path    Resource        Location
    >> Creation Time   Id
    >> The type CompositeActor is already defined      kepler/ptII/ptolemy/ 
    >> actor
    >> CompositeActor.java     Unknown 1193502394749   1691187
    >>
    >> Severity and Description        Path    Resource        Location
    >> Creation Time   Id
    >> The type EditorDropTarget is already defined
    >> kepler/ptII/ptolemy/vergil/basic        EditorDropTarget.java    
    >> line 88
    >> 1193502376966   1690230
    >>
    >> Severity and Description        Path    Resource        Location
    >> Creation Time   Id
    >> The type FiringEvent is already defined kepler/ptII/ptolemy/actor
    >> FiringEvent.java        Unknown 1193502394738   1691185
    >>
    >> Severity and Description        Path    Resource        Location
    >> Creation Time   Id
    >> The type IOPort is already defined      kepler/ptII/ptolemy/actor
    >> IOPort.java     Unknown 1193502394737   1691184
    >>
    >> Severity and Description        Path    Resource        Location
    >> Creation Time   Id
    >> The type NondeterministicMerge is already defined
    >> kepler/ptII/ptolemy/domains/pn/kernel    
    >> NondeterministicMerge.java      line
    >> 73      1193502381524   1690500
    >>
    >> Severity and Description        Path    Resource        Location
    >> Creation Time   Id
    >> The type ProcessThread is already defined
    >> kepler/ptII/ptolemy/actor/process       ProcessThread.java       
    >> Unknown
    >> 1193502391062   1691008
    >>
    >> 10. Christopher Brooks mentioned instructions at:
    >>
    >> http://chess.eecs.berkeley.edu/ptexternal/nightly/doc/coding/ 
    >> eclipse.htm
    >>
    >> These seem to be for Ptolemy.  For the Eclipse setup I should not  
    >> have to
    >> even build Ptolemy.  (It says so ;-)  In any event I didn't take  
    >> the time to
    >> get a Bash script running, since running config would not have  
    >> fixed the
    >> Kepler project anyway.  I note that ptII also has  
    >> a .classpath.defaults.  I
    >> tried putting that in .classpath for ptII at one time.  I still got  
    >> errors
    >> and had both .class and .java in the source directories.  I recall  
    >> that the
    >> bin directory got populated when I did that.  I since started over  
    >> from
    >> scratch so I am back to pretty much what should result from the
    >> instructions.  (The whole process is _very_ time consuming.)
    >>
    >> So that is where I stand and what I have learned.  I could probably  
    >> debug it
    >> more to where I got it working.  However, at this point it seems  
    >> that I
    >> would need to make changes to the files and configuration.  I think  
    >> that is
    >> better done at your end, given my inexperience with the project.   
    >> If it is a
    >> simple mistake on my part, I don't see it.
    >>
    >> Thanks for your help.
    >>
    >>        -Ken
    >>
    >>
    >> _______________________________________________
    >> Kepler-dev mailing list
    >> Kepler-dev at ecoinformatics.org
    >> http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/ 
    >> kepler-dev
    >>
    >>
    >>
    >> -- 
    >> Ph.D. Candidate
    >> Dr. Shiyong Lu's Research Lab
    >> Department of Computer Science
    >> Wayne State University
    >> Detroit, MI 48202
    >> _______________________________________________
    >> Kepler-dev mailing list
    >> Kepler-dev at ecoinformatics.org
    >> http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/ 
    >> kepler-dev
    >>     
    >
    > ----------
    > Derik Barseghian
    > http://www.nceas.ucsb.edu/ | office: 805-893-5127
    > Rm 3411, Marine Science Research Building, UCSB
    > Santa Barbara, CA, 93106-6150
    >
    > _______________________________________________
    > Kepler-dev mailing list
    > Kepler-dev at ecoinformatics.org
    > http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/kepler-dev
    >   
    
    
    -- 
    *******************************************************************
    Dan Higgins                                  higgins at nceas.ucsb.edu
    http://www.nceas.ucsb.edu/    Ph: 805-893-5127
    National Center for Ecological Analysis and Synthesis (NCEAS) Marine Scienc
   e Building - Room 3405
    Santa Barbara, CA 93195
    *******************************************************************
    
    _______________________________________________
    Kepler-dev mailing list
    Kepler-dev at ecoinformatics.org
    http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/kepler-dev
--------


More information about the Kepler-dev mailing list