[protege-discussion] Missing source?

[Jennifer Vendetti]

A couple of small additions to Tania's response:

1).  Our Ant build file is documented on our Web site:

http://protege.stanford.edu/doc/readme.html

2).  If you don't feel like dealing with Ant or JavaCC, you could 
download the source code from the download page on our Web site.  Each 
time we do a build, we put the source code for the build in ZIP file 
format on our downloads page:

http://protege.stanford.edu/download/prerelease/protege-src-3.2.zip

Jennifer

Tania Tudorache wrote:
> Michael,
>
> We have removed the parser classes from the svn code tree. These classes 
> are automatically generated by javacc, if you run the build.xml (If you 
> want only the parser classes to be generated and not to compile all the 
> classes, run the "javacc" target from build.xml, otherwise run the "jar" 
> or "dist" targets).
>
> In order to run the "javacc" target from the build file, you will have 
> to create a copy of the local.properties.template and rename it to 
> local.properties in which you set the right javacc path from your computer.
>
> Tania
>
> Shepherd, Michael wrote:
>   
>> Hi,
>>
>>  
>>
>> I checked out the latest Protégé source code from SVN and I'm getting a compile error that Parser is missing from ClipsKnowledgeBaseFactory.  Didn't there used to be a Parser class in this package, or am I missing a library?
>>
>>  
>>
>> Mike
>>
>>  
>>
>> _______________________________________________
>> protege-discussion mailing list
>> protege-discussion at lists.stanford.edu
>> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
>>
>> Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03 
>>
>>   
>>     
>
> _______________________________________________
> protege-discussion mailing list
> protege-discussion at lists.stanford.edu
> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
>
> Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03 
>