RE: [mylar-dev] Need advice on how to go about implementing aconnector

["Nathan Hapke" <nhapke@xxxxxxxxx>]

Comments inline:

________________________________

	From: mylar-dev-bounces@xxxxxxxxxxx
[mailto:mylar-dev-bounces@xxxxxxxxxxx] On Behalf Of Peter Thomas
	Sent: December 16/2006 23:54
	To: Mylar developer discussions
	Subject: Re: [mylar-dev] Need advice on how to go about implementing
aconnector
	
	
	Thanks Eugene and Nathan for your help.  I have decided to go with REST
and am busy implementing the connector eclipse-plugin.  I got a basic http
client working which is able to retrieve XML representation of a task from the
server.  Now I'm trying to get things working from the plugin side (using the
Trac connector as a reference) and am stuck, would appreciate if you can point
me in the right direction: 
	
	1) I'm testing by doing "Run Eclipse Application" and my plugin is shown
as loaded when I check About --> Plug-in Details.  But I'm not able to see
"JTrac" in the list of available repository types.  What is the trick to getting
a new entry into the list of choices when you try to "Add Task Repository".
I've implemented AbstractRepositoryConnectorUi and AbstractRepositoryConnector.
Admittedly, since I am trying to get just a "vertical slice" working, some of
the AbstractRepositoryConnector methods are returning null, though I tried my
best to focus on the ones that matter.  I have tried to set the "Extensions"
just like the Trac connector etc. 

Once you fulfill the extension point org.eclipse.mylar.tasks.ui.repositories for
connectorCore, connectorUi and externalizer, (and maybe
org.eclipse.mylar.tasks.ui.editors too) you should be in business.
	
	2) Is it a must that you have to have a "headless" version and a "ui"
version defined as separate plugins.  I'm currently having everything in one
plugin and the activator is a subclass of "AbstractUIPlugin". 

Must, no, I don't think so.  Good idea, yes.  I'd say you'd be better off to
have both plugins and start with everything in the ui one, and refactor to
separate headless stuff into the .core as you have time.
	
	3) I am able to use Apache Http Client libraries exported by
org.eclipse.mylar.context.core, which is very helpful.  However when I run unit
tests that need the HttpClient, they fail because they depend on commons-logging
which is not exported.  Is this intentional?  I am able to proceed now by
manually adding commons-logging in a lib folder as a dependency for my plugin.  
	 
167362: move httpclient dependency to Orbit
https://bugs.eclipse.org/bugs/show_bug.cgi?id=167362

Nathan