RE: [mylar-dev] Removing direct eclipse deps from task manager API

["Mik Kersten" <beatmik@xxxxxxx>]

That's right, and that's what the following bug is all about.  We've
previously did this de-coupling so that mylar.bugzilla.core could be used
standalone, and mylar.bugzilla.core and mylar.bugzilla.ui do have a clean
split (although search still needs to move into core).  In the process we
de-coupled the parts of mylar.tasklist that connector cores will need (i.e.
task and repository stuff).

149981: extract tasks framework from mylar.tasklist
https://bugs.eclipse.org/bugs/show_bug.cgi?id=149981

There will be the question of splitting AbstractRepositoryConnector into
core and UI parts, and of who instantiates connectors when this isn't done
by extension points. 

Tomasz, before we do that could you consider using OSGi in your headless
environment?  OSGi is a great component model and is seeing increasing use
by server side and headless apps.  If it happened to work for you it would
make things easier to use since connectors would not need to be instantiated
explicitly.

Mik

> -----Original Message-----
> From: mylar-dev-bounces@xxxxxxxxxxx [mailto:mylar-dev-bounces@xxxxxxxxxxx]
> On Behalf Of Eugene Kuleshov
> Sent: Friday, July 07, 2006 4:15 PM
> To: Mylar developer discussions
> Subject: Re: [mylar-dev] Removing direct eclipse deps from task manager
> API
> 
> 
>   I guess that would require some decoupling of the UI in existing
> providers. Current provider API does not generalize neither encourage
> repository providers to implement headless API.
> 
>   regards,
>   Eugene
> 
> 
> Mik Kersten wrote:
> > I think that we should all cheat as much as we can ;)  If this headless
> use
> > of Mylar plays out nicely we will have a nice circle of interdependency
> > between four cool open source projects (Mylar, Maven, Subclipse and JIRA
> > Dashboard).  And the best part about this one is that it encourages us
> to
> > continue making the framework work in headless mode.  Some academic
> projects
> > have already used mylar.bugzilla.core in that way, but the real value
> will
> > come from making mylar.tasks work headless since it will enable coding
> to
> > one API but working for all connectors.
> >
> > Mik
> >
> >
> >> -----Original Message-----
> >> From: mylar-dev-bounces@xxxxxxxxxxx [mailto:mylar-dev-
> bounces@xxxxxxxxxxx]
> >> On Behalf Of Eugene Kuleshov
> >> Sent: Friday, July 07, 2006 3:53 PM
> >> To: Mylar developer discussions
> >> Subject: Re: [mylar-dev] Removing direct eclipse deps from task manager
> >> API
> >>
> >>
> >>   Hey! That would be cheating. Aren't your ITAPI project supposed to
> >> implement very same stuff? :-)
> >>
> >>   regards,
> >>   Eugene
> >>
> >>
> >> Tomasz Pik wrote:
> >>
> >>> Good morning/afternoon/evening,
> >>>
> >>>
> >>>> From https://bugs.eclipse.org/bugs/show_bug.cgi?id=149981
> >>>>
> >>> I understand, that new org.eclipse.mylar.tasks plugin
> >>> will depend only on org.eclipse.core.runtime (and 'internal' classes
> >>> went to different location).
> >>> But looking at MANIFEST.MF for org.eclipse.core.runtime I've found:
> >>> Require-Bundle: org.eclipse.osgi;bundle-version="[3.2.0,4.0.0)";visibi
> >>> lity:=reexport,org.eclipse.equinox.common;bundle-version="[3.2.0,4.0.
> >>> 0)";visibility:=reexport,org.eclipse.core.jobs;bundle-version="[3.2.0
> >>> ,4.0.0)";visibility:=reexport,org.eclipse.equinox.registry;bundle-ver
> >>> sion="[3.2.0,4.0.0)";visibility:=reexport,org.eclipse.equinox.prefere
> >>> nces;bundle-version="[3.2.0,4.0.0)";visibility:=reexport,org.eclipse.
> >>> core.contenttype;bundle-version="[3.2.0,4.0.0)";visibility:=reexport,
> >>> org.eclipse.core.runtime.compatibility.auth;bundle-version="[3.2.0,4.
> >>> 0.0)";resolution:=optional
> >>>
> >>> I don't know too much about OSGI Does it means that if I want to use
> >>> org.eclipse.mylar.tasks library in my code outside Eclipse, I'll have
> to
> >>> ad all those dependencies along with org.eclipse.core.runtime (and
> also
> >>> find and add all dependencies of above list)?
> >>>
> >>> Regards,
> >>> Tomek
> >>> _______________________________________________
> >>> mylar-dev mailing list
> >>> mylar-dev@xxxxxxxxxxx
> >>> https://dev.eclipse.org/mailman/listinfo/mylar-dev
> >>>
> >> _______________________________________________
> >> mylar-dev mailing list
> >> mylar-dev@xxxxxxxxxxx
> >> https://dev.eclipse.org/mailman/listinfo/mylar-dev
> >>
> >
> > _______________________________________________
> > mylar-dev mailing list
> > mylar-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/mylar-dev
> >
> 
> _______________________________________________
> mylar-dev mailing list
> mylar-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mylar-dev