[kepler-dev] Problem building Kepler

Chad Berkley berkley at nceas.ucsb.edu
Fri Apr 22 10:55:19 PDT 2005


I think this is related to the port.setContainer(null) calls that we 
talked about earlier.  I haven't had a chance to look into it further 
and probably won't today.  At any rate, I think the problem is on our 
end, we just didn't know we were doing anything wrong :)

chad

Dan Higgins wrote:
> Christopher, Bertram, and others:
> 
>    The primary problem that I know about is related to the cloning issue 
> that has been discussed the last few days.
> 
>    When using the CVS release of PT, Kepler throws a bunch of errors 
> whenever a new Graph panel is built (i.e. when a workflow is opened). 
> This is due to Kepler building the actor tree. It is due to Java 
> variable names not agreeing with the Port name string. Currently, I 
> think there are only 3 or 4 actors where we haven't fixed the problem 
> and they all have dynamic port creation. I think that they do NOT get 
> added to the actor list due to this problem. Chad may have more details 
> on which actors have the problem.
> 
> Dan
> 
> Christopher Brooks wrote:
> 
>> Hi Dan,
>>
>> BTW - I'm just curious, what are the issues with the ptII cvs tree?
>> Is there anything I can do to help?
>>
>> I'm in the process of getting a beta release together, now
>> is a good time for me to fix the ptII cvs tree.
>>
>> This would be a good time to synch the Kepler and ptII trees.
>>
>> Edward and I have talked about making the cvs tree more available.
>>
>> My primary fear is that the ptII tree sometimes does not build.  We
>> have been pretty good about this lately, there have been no major
>> build errors in the kernel or actor packages lately.  However, for
>> example, some of Haiyang's CT work resulted in CT being unstable for
>> months as he worked on the problem.
>>
>> We could fairly easily set up a cvs read only password for the kepler
>> folks to specifically use, which would allow easier access to the
>> cvs tree.
>>
>> Also, about the read-only vs read/write cvs password issue, the
>> problem is that for read/write passwords, I have to request a Unix UID 
>> for the new user from the department and create a Unix
>> account.  Usually, this takes 5 minutes, but sometimes it can take
>> much longer.  In contrast, creating a read-only account never
>> takes more than 2 minutes.
>>
>> The upshot is that I'm more than willing to create read-write
>> accounts for Kepler developers that want them,  I just don't
>> want to create read/write accounts for all Kepler developers.
>>
>> In other news, we are probably going to move the ptII cvs repository
>> to a new machine.  This would happen in June.  More news as it
>> develops.
>>
>>
>> _Christopher
>>
>>
>> --------
>>
>>    Bertram and Jianting,
>>           It's not quite true that you need the CVS version of Ptolemy.
>>       A minor change to the build.xml file may fix your problem. 
>> Search the    build.xml file for 'parser'. You should find the line(s)
>>           <!--copy the exprimental source-->
>>        <copy todir="${kep.build.src}" filtering="yes">
>>          <fileset dir="${srcdir}/${expsrcdir}">
>>            <include name="**"/>
>>            <!--<exclude name="ptolemy/moml/MoMLParser.java"/>-->
>>          </fileset>
>>        </copy>
>>       Remove the comment markers so the the the 'exclude line is
>>            <exclude name="ptolemy/moml/MoMLParser.java"/>
>>       That will remove the offending code (Be sure to run 'ant clean' 
>> before    your start again after making this change.
>>          After this change, you can work with PT4.0.1. (in fact, I 
>> would currently r
>>   ecommend this since there are some issues with the CVS version of PT
>>          Dan
>>       =======
>>       Jianting Zhang wrote:
>>       >I just got this error yesterday when I rebuilt my machine.
>>    >
>>    >The problem is that you need a CVS version of PTII instead of a 
>> source    >release used previously. You may request a read access 
>> account by sending    >mail to ptolemy at eecs.berkeley.edu . Christopher 
>> reponded pretty fast.
>>    >
>>    >Jianting
>>    >
>>    >
>>    >----- Original Message -----    >From: "Bertram Ludaescher" 
>> <ludaesch at ucdavis.edu>
>>    >To: "kepler-dev" <kepler-dev at ecoinformatics.org>
>>    >Sent: Friday, April 22, 2005 10:55 AM
>>    >Subject: [kepler-dev] Problem building Kepler
>>    >
>>    >
>>    >     >
>>    >>Hi:
>>    >>
>>    >>I just updated my Kepler cvs and did an 'ant clean'.
>>    >>
>>    >>The system current doesn't build however (for me).
>>    >>
>>    >>Does anybody have seen this error below before or else know what is
>>    >>broken?
>>    >>
>>    >>thanks!
>>    >>
>>    >>Bertram
>>    >>
>>    >>C:\ny\kepler>ant run
>>    >>ant run
>>    >>Buildfile: build.xml
>>    >>...
>>    >>win.prep:
>>    >>    [echo] Guessing that you are running: Windows
>>    >>
>>    >>lin.prep:
>>    >>
>>    >>init:
>>    >>   [mkdir] Created dir: C:\ny\kepler\dynsrc
>>    >>
>>    >>copy-lib-win:
>>    >>
>>    >>copy-lib-unix:
>>    >>
>>    >>setcommonclasspath:
>>    >>
>>    >>prepare:
>>    >>   [mkdir] Created dir: C:\ny\kepler\build
>>    >>    [copy] Copying 1 file to C:\Ptolemy\ptII4.0.1
>>    >>    [copy] Copying 1 file to C:\Ptolemy\ptII4.0.1
>>    >>   [mkdir] Created dir: C:\ny\kepler\build\src
>>    >>   [mkdir] Created dir: C:\ny\kepler\build\classes
>>    >>    [copy] Copying 457 files to C:\ny\kepler\build\src
>>    >>    [copy] Copying 15 files to C:\ny\kepler\build\classes
>>    >>    [copy] Copying 38 files to C:\ny\kepler\build\configs
>>    >>    [copy] Copying 15 files to C:\ny\kepler\build\configs
>>    >>    [copy] Copying 1 file to C:\ny\kepler\build\configs
>>    >>   [mkdir] Created dir: C:\ny\kepler\build\configs\kepler
>>    >>    [copy] Copying 1 file to C:\ny\kepler\build\configs
>>    >>    [copy] Copying 174 files to    
>> >>C:\ny\kepler\build\configs\ptolemy\configs\kepler\workflows
>>    >>    [copy] Copying 7 files to C:\ny\kepler\build\src
>>    >>    [copy] Copying 1 file to C:\ny\kepler
>>    >>   [mkdir] Created dir: C:\ny\kepler\build\tmp
>>    >>
>>    >>compile:
>>    >>   [javac] Compiling 427 source files to C:\ny\kepler\build\classes
>>    >>   [javac] 
>> C:\ny\kepler\build\src\ptolemy\moml\MoMLParser.java:399:    
>> >>filterAttributeValue(ptolemy.kernel.util.NamedObj,java.lang.String,java.l 
>>
>>   ang.String)    >>in ptolemy.moml.MoMLFilter cannot be applied to    
>> >>(ptolemy.kernel.util.NamedObj,java.lang.String,java.lang.String,java.lang 
>>
>>   .String)
>>    >>   [javac]                 filteredValue =    
>> >>filter.filterAttributeValue(_current,
>>    >>   [javac]                                       ^
>>    >>   [javac] Note: Some input files use or override a deprecated API.
>>    >>   [javac] Note: Recompile with -deprecation for details.
>>    >>   [javac] 1 error
>>    >>
>>    >>BUILD FAILED
>>    >>C:\ny\kepler\build.xml:343: Compile failed; see the compiler 
>> error output
>>       >>for details.
>>    >>
>>    >>_______________________________________________
>>    >>Kepler-dev mailing list
>>    >>Kepler-dev at ecoinformatics.org
>>    
>> >>http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/kepler-dev 
>>
>>    >>
>>    >>       >>
>>    >
>>    >_______________________________________________
>>    >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 Science 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