Re: [Pando-devel] Issues with Fifpa Console

[Cameron R. <cr...@sy...>]

Great!   Good luck with your thesis presentation.

Cameron.

Volodymyr Babiy wrote:
> Hi,
>
> Sorry for not replying to your email sooner, I just came 
> back from my classes. Also, the instructions you have 
> provided, will help me to work with pando project.  I will 
> make sure, from now on, to follow pando developing 
> principals and practices.  Also, currently I am preparing 
> the presentation for tomorrow. So, I think I should have 
> some time tonight to look at the README file and make sure 
> I did not miss any steps. Tomorrow, I will resume the work 
> on the FIPA Console prototype. If I would not be able to 
> solve the issue tonight, it will be decently solved 
> tomorrow.
>
> Cheers
> Volodymyr Babiy
>
>
> On Tue, 08 Jan 2008 10:56:10 -0500
>   Cameron Ross <cr...@sy...> wrote:
>   
>> Hi Vlad,
>>
>> I'm just going through the fipa console plug-in and I'm 
>> having some 
>> problems getting it to run (I've followed the README). 
>> Specifically, I 
>> get a null pointer exception when I type in "agents" at 
>> the console 
>> command line.  Note that I do not get the message 
>> "Activated FIPA 
>> Console" when I run the launcher and that the 
>> ConsolePms.activate() is 
>> never entered when I run it in the debugger. 
>>
>> Some other generral comments:
>> 1) The "Pms" suffix doesn't have meaning within the 
>> Pando project.  
>> Please rename ConsolePms to ConsoleActivator.
>> 2) The fipa agent plug-ins 1 and 2 use the @dot 
>> convention for binary 
>> outputs whereas the console plug-in uses bin.  I don't 
>> see why these 
>> aren't consistent.
>> 3) The pando_core.jar file has been copied into each of 
>> the prototype's 
>> lib folders.  Please remove pando_core.jar from the 
>> agent plug-ins and 
>> have the console plugin export the jar.  The agent 
>> plugins can then 
>> import the jar using the "Import-Package:" directive 
>> within their 
>> respective manifests.
>>
>> Finally, I've made a few changes to the pando codebase 
>> that you'll need 
>> to retrieve.  Here is a general process to follow with 
>> regard to 
>> checking code into the Pando repository.  Please follow 
>> this each and 
>> every time you do a checkin.
>> 1) Run ant -f module_build.xml all and ant -f 
>> module_build.xml test from 
>> the PANDO_DEV_HOME/code/modules directory.  If errors or 
>> warnings result 
>> then clean them.
>> 2) Run ant -f module_build.xml clean from the 
>> PANDO_DEV_HOME/code/modules directory.
>> 3) Update the Pando SVN repository from the root 
>> directory (i.e. 
>> PANDO_DEV_HOME).
>> 4) Run ant -f module_build.xml all and ant -f 
>> module_build.xml test from 
>> the PANDO_DEV_HOME/code/modules directory.  If errors or 
>> warnings result 
>> then clean them.
>> 5) Run ant -f module_build.xml clean from the 
>> PANDO_DEV_HOME/code/modules directory.
>> 6) Commit the Pando SVN repository from the root 
>> directory (i.e. 
>> PANDO_DEV_HOME).
>> 7) Send an email to the pando-devel list announcing that 
>> you've modified 
>> the repository.
>>
>> Cheers,
>> Cameron.
>>
>> -------------------------------------------------------------------------
>> Check out the new SourceForge.net Marketplace.
>> It's the best place to buy or sell services for
>> just about anything Open Source.
>> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
>> _______________________________________________
>> pando-devel mailing list
>> pan...@li...
>> https://lists.sourceforge.net/lists/listinfo/pando-devel
>>     
>
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
> _______________________________________________
> pando-devel mailing list
> pan...@li...
> https://lists.sourceforge.net/lists/listinfo/pando-devel
>
>