Search Mailing List Archives


Limit search to: Subject & Body Subject Author
Sort by: Reverse Sort
Limit to: All This Week Last Week This Month Last Month
Select Date Range     through    

[protege-discussion] Help : Protege 4 client server (Bleeding edge version)

Dinbandhu Laxman Gauda Dinbandhu_Gauda at infosys.com
Wed Oct 31 04:07:43 PDT 2012


Hi,

I am not able to deploy Protégé 4 server  on Windows 7 (32 bit) even though exe is installed for x32 bit.

Similar issue is with clean.full as well

Attached is a log from ant build.

Thanks
-Dinu

-----Original Message-----
From: protege-discussion-bounces at lists.stanford.edu [mailto:protege-discussion-bounces at lists.stanford.edu] On Behalf Of Timothy Redmond
Sent: Wednesday, 31 October, 2012 12:52
To: protege-discussion at lists.stanford.edu
Subject: Re: [protege-discussion] Help : Protege 4 client server (Bleeding edge version)

On 10/30/2012 10:08 PM, Dinbandhu Laxman Gauda wrote:
> Hi Timothy,
>
> Attached is a log text file.  I looked at org.protege.owl.server.jar 
> file and looks like SetMetaprojectDataDir.class file is missing. I 
> infact .java file is also missing from 
> org.protege.owl.server\src\main\java\org\protege\owl\server\command
> folder
>
> Thanks
> -Dinu
>

Thanks very much for the help.  This problem was completely my mistake - actually I made several mistakes to make this happen.  It has been broken for a bit and I didn't notice.  If you update and try again I think that it will work.  (I just ran the installer in both linux and
windows.)

One of the things that I changed to fix this was to change the ant clean target and add a clean.full target.  The clean target now just cleans up the built artifacts in the checked out directories.  The clean.full target will also clean up the Protege OWL server files that have been installed in the system directories.

You have also helped me see that I can simplify this process when the server is ready for release.  The current version involves two projects (the server project and the server deployer project) that get built.  If anything goes wrong in either one then the build fails.  But really all we need to distribute is the deployer project together with a built copy of the server.

-Timothy


_______________________________________________
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

**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely 
for the use of the addressee(s). If you are not the intended recipient, please 
notify the sender by e-mail and delete the original message. Further, you are not 
to copy, disclose, or distribute this e-mail or its contents to any other person and 
any such actions are unlawful. This e-mail may contain viruses. Infosys has taken 
every reasonable precaution to minimize this risk, but is not liable for any damage 
you may sustain as a result of any virus in this e-mail. You should carry out your 
own virus checks before opening the e-mail or attachment. Infosys reserves the 
right to monitor and review the content of all messages sent to or from this e-mail 
address. Messages sent to or from this e-mail address may be stored on the 
Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: log-with-everything-deploy.txt
URL: <http://mailman.stanford.edu/pipermail/protege-discussion/attachments/20121031/b6cc3c9c/attachment-0002.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: log-with-everything-clean.full.txt
URL: <http://mailman.stanford.edu/pipermail/protege-discussion/attachments/20121031/b6cc3c9c/attachment-0003.txt>


More information about the protege-discussion mailing list