[protege-discussion] Build Questions (was Re: Question on some old classes/methods)

[Mark Feblowitz]

I'm trying to do source level debugging to the point of failure, 
which is in the method. I can't do that in eclipse without having 
generated line number in the jar for the debug. So I'm trying to 
build the protege.jar from either the source distribution or the 
Subversion repository (the latter seems to work better.

I've been able to get the protege core and protege owl plugin to 
compile without errors (with a little extra help from ant where 
eclipse isn't doing the tric.

One thing I noticed is that the build file for protege does not 
correctly identify javacc.home. Is that a known problem or just 
something I had needed to handle?

Also, when trying to run the constructed protege.jar, an exception is 
thrown that makes me wonder whether I have all of the right parts in the jar:

Exception in thread 
"org.lexgrid.ui.extension.protege.LgProtegeEditor" 
java.lang.NoClassDefFoundError: com/hp/hpl/jena/rdf/arp/StatementHandler
at 
edu.stanford.smi.protegex.owl.jena.JenaKnowledgeBaseFactory.createKnowledgeBase(JenaKnowledgeBaseFactory.java:77)
at edu.stanford.smi.protege.model.Project.createDomainKB(Project.java:323)
at 
edu.stanford.smi.protege.model.Project.createDomainKnowledgeBase(Project.java:341)
at edu.stanford.smi.protege.model.Project.<init>(Project.java:253)
at edu.stanford.smi.protege.model.Project.<init>(Project.java:237)
at edu.stanford.smi.protege.model.Project.<init>(Project.java:273)
at edu.stanford.smi.protege.model.Project.<init>(Project.java:262)
at 
org.lexgrid.ui.extension.protege.LgProtegeEditor$SwingFrameAccess.init(LgProtegeEditor.java:166)
at 
org.lexgrid.ui.extension.protege.LgProtegeEditor.getSwingFrame(LgProtegeEditor.java:338)
at 
org.lexgrid.ui.extension.protege.LgProtegeEditor$SwingInitThread.run(LgProtegeEditor.java:266)

Do I need anything else other than the protege core and protege owl 
plugin (and the jars they reference)?

Thanks,

Mark


At 02:48 PM 10/17/2006, Tania Tudorache wrote:
>Mark,
>
>If you use the latest Protege 3.2 beta, than you should use Java 1.5.
>
>The Parser class is automatically generated by the Protege build 
>script. The instructions for building Protege out of the svn 
>repository or source code distribution are here: 
>http://protege.stanford.edu/doc/readme.html
>
>However, I don't think that you need to recompile Protege. I 
>suppose, you can use the Protege jars and only recompile the Eclipse 
>plugin code.
>
>Tania
>
>
>Mark Feblowitz wrote:
>>My prior questions had to do with my efforts to update the LexGrid 
>>"Protege in Eclipse" project. All seems to be well, with the 
>>exception of the Protege Owl Plugin's Metadata Tab.
>>
>>I'm trying to debug and have the need to debug the source of 
>>Protege. I've imported the Protege core, but have a persistent 
>>problem with two build errors:
>>
>>         The project was not built since its build path is 
>> incomplete. Cannot find the class file for 
>> javax.swing.plaf.metal.DefaultMetalTheme.
>>
>>     The type javax.swing.plaf.metal.DefaultMetalTheme cannot be
>>     resolved. It is indirectly referenced from required .class files
>>     Protege/src/edu/stanford/smi/protege/util   ProtegePlasticTheme.java
>>I'm using the IBM 1.5 JRE. When I switch to the Sun 1.5 JRE, I get 
>>4 errors about
>>
>>     "Parser cannot be resolved to at type"
>>and 42 errors about
>>
>>     jThe declared package "javax.swing.plaf.metal" does not match the
>>     expected package "edu.stanford.smi.protege.util"
>>
>>I'm doing this work within ecplise 3.2.0
>>
>>What should I be using for my JRE? Any additional jars in the build 
>>path needed to reference javax.swing.plaf.metal.DefaultMetalTheme?
>>
>>Thanks,
>>
>>Mark
>>
>>
>>At 06:24 PM 10/13/2006, Tania Tudorache wrote:
>>>Mark,
>>>
>>>We are very careful not to delete or move public classes or methods.
>>>
>>>The
>>>
>>>edu.stanford.smi.protege.util.FileHandler
>>>
>>>is in the same place :)
>>>
>>>In which version did Protege have a detachCurrentTab() method in
>>>ProjectView? I think the method you are looking for is the
>>>detachCurrentView().
>>>
>>>The DefaultEntry is still in the same place:
>>>
>>>edu.stanford.smi.protege.plugin. DefaultEntry
>>>
>>>Are you using the right jars?
>>>
>>>Tania
>>>
>>>
>>>
>>>
>>>Mark Feblowitz wrote:
>>> > Add to that
>>> >
>>> >          edu.stanford.smi.protege.util.FileHandler
>>> >
>>> >
>>> > At 05:05 PM 10/13/2006, Mark Feblowitz wrote:
>>> >
>>> >> I was wondering what became of these two classes in Protege:
>>> >>
>>> >>          edu.stanford.smi.protege.ui.ProjectView - specifically
>>> >> detachCurrentTab()
>>> >>
>>> >>          edu.stanford.smi.protege.plugin.DefaultEntry
>>> >>
>>> >> Have these been moved, removed or replaced? What would be the 
>>> new equivalents?
>>> >>
>>> >> Thanks,
>>> >>
>>> >> Mark
>>> >> _______________________________________________
>>> >> 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
>>> >
>>> >
>>>
>>>_______________________________________________
>>>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