[kepler-dev] Once Again Issues in buidling kepler 2.0

David Welker david.v.welker at gmail.com
Fri Apr 23 04:45:10 PDT 2010


Hi Bala,

The classpath should be handled for  you by the build system. Can you  
look in your ptolemy/lib dir? It should have batik-all-1.6.jar.

If it doesn't let me know. If it does, can you provide a print out of  
your compile errors?

-David



On Apr 23, 2010, at 5:20 AM, AMARNATH, Balachandar wrote:

> Dear David,
>
>       Yes, i did that successfully. But When i run ant run, it  
> starts compiling the sources and ended up with error. Many of the  
> imports were not resolved. Do i need to export jar files inthe  
> classpath ?
>
> regards
> Bala
>
> From: David Welker [mailto:david.v.welker at gmail.com]
> Sent: 23 April 2010 16:02
> To: AMARNATH, Balachandar
> Cc: kepler-dev-owner at kepler-project.org; kepler-dev at kepler-project.org
> Subject: Re: [kepler-dev] Once Again Issues in buidling kepler 2.0
>
> It is certainly a network issue. I just issued the same commands you  
> did and Ptolemy downloaded fine.
>
> Maybe it is a firewall issue? As the build instructions (https://kepler-project.org/developers/teams/build/documentation/build-system-instructions 
> ) if you do not have access to port 22, you need to download ptolemy  
> manually. You can use the following command:
>
> svn co https://source.eecs.berkeley.edu/svn/chess/ptII/trunk  
> <kepler.modules>/ptolemy/src
> Hope that helps!
>
> -David
>
> On Apr 23, 2010, at 3:04 AM, AMARNATH, Balachandar wrote:
>
>> Dear David Welker,
>>
>>  Thanks for the repply. I still encounter the issue.I ran the  
>> exactly the same commands.
>>
>>
>> *****************************
>> [change-to] ptolemy revision:57640
>> [change-to] svn co -r57640 svn://source.eecs.berkeley.edu/chess/ 
>> ptII/branches/rel-8-0-beta-2 c:\Home 
>> \BAAMARNA5617\kepler-2.0\MyModules\ptolemy-8.0\src
>> [change-to] svn: Unknown hostname 'source.eecs.berkeley.edu'
>> [change-to]
>> BUILD FAILED
>> ERROR: It appears that the command did not execute properly and  
>> exited with an exit code of: 1
>> ******************************************
>>
>>
>>
>> Any hint to come out of the issue ?
>>
>> regards
>> Balachandar
>> From: David Welker [mailto:david.v.welker at gmail.com]
>> Sent: 23 April 2010 12:27
>> To: AMARNATH, Balachandar
>> Subject: Re: [kepler-dev] Again Issues in buidling kepler 2.0
>>
>> Hi  Balachandar,
>>
>> This looks like a network problem. We use the svn protocol for  
>> ptolemy because using other protocols causes certain issues to  
>> arise. Using this protocol is not a problem.
>>
>> I would suggest you try the command again. It should work.  
>> Sometimes with partial downloads, issuing the command again can  
>> cause issues that can be resolved by deleting <kepler.modules>  
>> ptolemy to start clean, but it usually works without doing that.
>>
>> -David
>>
>>
>> On Apr 22, 2010, at 11:03 PM, AMARNATH, Balachandar wrote:
>>
>>>
>>>
>>>
>>> Dear All,
>>>
>>> I could write an actor and instantiate in kepler 1.0 but the same  
>>> is not working with kepler 2.0 (I installed kepler 2.0 using  
>>> <kepler>.jar version).
>>>
>>> I am trying to write a simple actor using Kepler 2.0. I was  
>>> advised by the documentation to build the kepler from svn and use  
>>> to develop the actor.
>>>
>>> So, I again, I ran the following command
>>>
>>> >  svn co https://code.kepler-project.org/code/kepler/branches/releases/release-branches/build-area-2.0 
>>>  build-area
>>> >  cd cd build-area
>>> >  ant change-to -Dsuite=kepler-2.0
>>>
>>> But it ran for sometime and finally end up with error. The last  
>>> few stack trace is given below
>>>
>>>
>>> *****************************
>>> [change-to] ptolemy revision:57640
>>> [change-to] svn co -r57640 svn://source.eecs.berkeley.edu/chess/ 
>>> ptII/branches/rel-8-0-beta-2 c:\Home 
>>> \BAAMARNA5617\kepler-2.0\MyModules\ptolemy-8.0\src
>>>
>>> [change-to]
>>>
>>> BUILD FAILED
>>> ERROR: It appears that the command did not execute properly and  
>>> exited with an exit code of: 1
>>> ******************************************
>>>
>>> Is this because of the svn protocol it uses to connect to the  
>>> berkey.edu server ? Is it possible to connect with 'https'
>>>
>>> Can anyone help me out ?
>>>
>>>
>>> With thanks and regards
>>> Balachandar
>>>
>>>
>>>
>>> The information in this e-mail is confidential. The contents may  
>>> not be disclosed or used by anyone other than the addressee.  
>>> Access to this e-mail by anyone else is unauthorised.
>>> If you are not the intended recipient, please notify Airbus  
>>> immediately and delete this e-mail.
>>> Airbus cannot accept any responsibility for the accuracy or  
>>> completeness of this e-mail as it has been sent over public  
>>> networks. If you have any concerns over the content of this  
>>> message or its Accuracy or Integrity, please contact Airbus  
>>> immediately.
>>> All outgoing e-mails from Airbus are checked using regularly  
>>> updated virus scanning software but you should take whatever  
>>> measures you deem to be appropriate to ensure that this message  
>>> and any attachments are virus free.
>>> _______________________________________________
>>> Kepler-dev mailing list
>>> Kepler-dev at kepler-project.org
>>> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
>>
>> This mail has originated outside your organization, either from an  
>> external partner or the Global Internet.
>> Keep this in mind if you answer this message.
>>
>> The information in this e-mail is confidential. The contents may  
>> not be disclosed or used by anyone other than the addressee. Access  
>> to this e-mail by anyone else is unauthorised.
>> If you are not the intended recipient, please notify Airbus  
>> immediately and delete this e-mail.
>> Airbus cannot accept any responsibility for the accuracy or  
>> completeness of this e-mail as it has been sent over public  
>> networks. If you have any concerns over the content of this message  
>> or its Accuracy or Integrity, please contact Airbus immediately.
>> All outgoing e-mails from Airbus are checked using regularly  
>> updated virus scanning software but you should take whatever  
>> measures you deem to be appropriate to ensure that this message and  
>> any attachments are virus free.
>
> This mail has originated outside your organization, either from an  
> external partner or the Global Internet.
> Keep this in mind if you answer this message.
>
> The information in this e-mail is confidential. The contents may not  
> be disclosed or used by anyone other than the addressee. Access to  
> this e-mail by anyone else is unauthorised.
> If you are not the intended recipient, please notify Airbus  
> immediately and delete this e-mail.
> Airbus cannot accept any responsibility for the accuracy or  
> completeness of this e-mail as it has been sent over public  
> networks. If you have any concerns over the content of this message  
> or its Accuracy or Integrity, please contact Airbus immediately.
> All outgoing e-mails from Airbus are checked using regularly updated  
> virus scanning software but you should take whatever measures you  
> deem to be appropriate to ensure that this message and any  
> attachments are virus free.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mercury.nceas.ucsb.edu/kepler/pipermail/kepler-dev/attachments/20100423/004a51db/attachment.html>


More information about the Kepler-dev mailing list