Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mylyn-integrators] Mylyn API usage from a headless application 
Thanks for these information - they help a lot!
I think we will wait (for now) with our headless integration until Mylyn has official support for such an environment! 

With best regards,
MarkusT

On 04.09.2013 14:54, Steffen Pingel wrote:

Hi,
the changes are still work in progress and will be released as part of Mylyn 3.10 in October at the earliest. That release (or more likely 3.11) will be shipped as part of Eclipse Luna. The release will be backwards compatible with 3.8 and Juno though so you could consume it and still retain compatibility with older Eclipse releases.
If you need to consume Mylyn 3.8 in a headless context you would have to use Mylyn internals to create a repository manager instance etc. and register connectors manually since the extension point is in the UI. 

Steffen
On Wed, Sep 4, 2013 at 2:23 PM, Markus Tiede <Markus.Tiede@xxxxxxxxx <mailto:Markus.Tiede@xxxxxxxxx>> wrote: 

    Hello Steffen,

    thank you for the detailed comments and the bug references!

    So if I understand correctly there is currently no official way to
    use this kind of API e.g. on an RCP target basis for Mylyn (3.8.3)
    that came with Juno?

    With best regards,
    MarkusT


    On 04.09.2013 13:12, Steffen Pingel wrote:

        Hi,

        that's great to hear that you are reusing Mylyn in this way.
        We have indeed started working on improving the core/ui split
        to support use cases of this sort better. I would recommend
        taking a look at these two bugs:

         386117: [api] tasks.core relevant extensions should not be
        declared in tasks.ui,
        https://bugs.eclipse.org/bugs/show_bug.cgi?id=386117
         316253: [api] provide access to instance of
        IRepositoryManager through core API,
        https://bugs.eclipse.org/bugs/show_bug.cgi?id=316253

        The first one is about moving the connector extension point
        into the tasks.core bundle to enable discovery of connectors
        in headless contexts. The tasks framework would still require
        the extension registry so this would work best in OSGi
        environments but connectors could be used through the
        framework without the UI more easily.

        The second change is about moving life-cycle management of
        repositories and the task list into a core bundle and exposing
        the data model as an OSGi service. This would allow headless
        clients to work with the default task list and repository
        instances which are currently only accessible from the UI.
        Another goal of the change is to extract the code for creating
        the model instance. This would allow clients to instantiate
        their own tasks model with separate connector instances,
        caches etc. more easily. Those model instance wouldn't
        interact with the Mylyn UI but still support all core
        functionality such as query synchronization.

        It'd be great if you could comment on the bugs and let us know
        what your requirements are and help evaluate the proposed
        changes. Also, please feel encouraged to file new bugs if you
        have other requirements that aren't already captured in Bugzilla.

        Steffen




        On Mon, Sep 2, 2013 at 5:15 PM, Markus Tiede
        <Markus.Tiede@xxxxxxxxx <mailto:Markus.Tiede@xxxxxxxxx>
        <mailto:Markus.Tiede@xxxxxxxxx
        <mailto:Markus.Tiede@xxxxxxxxx>>> wrote:

            Hello,

            we, the Jubula team, are currently working on a better
        integration
            with various ALM tools using the Mylyn API.

            We aim for a connector and repository neutral solution to
        report
            test results (via auto-generated comments) to arbitrary
        tasks for
            any task repository that is supported by Mylyn. This is so far
            looking pretty good using the Mylyn Tasks / Core API from
        within a
            standalone RCP UI application.Therefore we're using the
            "TasksUiUtil" and "TasksUi" API to access the global
        repository
            manager.

            Since we would also like to report those information from our
            commandline tools (e.g. our headless tool for test execution
            "testexec") during a nightly CI run we are currently
        searching for
            a solution to gain access to e.g. all configured
        repositories for
            a given workspace from within a headless context (an RCP
            application without an active workbench; the platform
        itself is
            running).

            I've already found some information [1] discussing this
        topic but
            as we would like to implement a connector independent solution
            this is currently too specific for our needs.

            So my questions are:
             - Are there already any Mylyn services / platform mechanism
            present (which I've missed so far) to achieve this?
             - If not, are there any plans to move the code to
        retrieve the
            repository manager so that it would also be usable from a
        non-UI
            context?

            Thanks in advance for any comments and with best regards,
            MarkusT

            [1]
        http://wiki.eclipse.org/Mylyn/Integrator_Reference#Headless_and_standalone_use

            --     BREDEX GmbH
            Mauernstr. 33
            38100 Braunschweig

            Tel.: +49-531-24330-0 <tel:%2B49-531-24330-0>
        <tel:%2B49-531-24330-0>
            Fax: +49-531-24330-99 <tel:%2B49-531-24330-99>
        <tel:%2B49-531-24330-99>
            http: www.bredex.de <http://www.bredex.de>
        <http://www.bredex.de>


            Geschäftsführer: Achim Lörke, Ulrich Obst, Andreas Vogel
            Amtsgericht Braunschweig HRB 2450

            _______________________________________________
            mylyn-integrators mailing list
        mylyn-integrators@xxxxxxxxxxx
        <mailto:mylyn-integrators@xxxxxxxxxxx>
        <mailto:mylyn-integrators@xxxxxxxxxxx
        <mailto:mylyn-integrators@xxxxxxxxxxx>>

        https://dev.eclipse.org/mailman/listinfo/mylyn-integrators
-- Steffen Pingel 
        Principal Software Engineer, Eclipse Mylyn
        Mylyn Tasks Lead
        http://tasktop.com


        _______________________________________________
        mylyn-integrators mailing list
        mylyn-integrators@xxxxxxxxxxx
        <mailto:mylyn-integrators@xxxxxxxxxxx>
        https://dev.eclipse.org/mailman/listinfo/mylyn-integrators


    _______________________________________________
    mylyn-integrators mailing list
    mylyn-integrators@xxxxxxxxxxx <mailto:mylyn-integrators@xxxxxxxxxxx>
    https://dev.eclipse.org/mailman/listinfo/mylyn-integrators




--
Steffen Pingel
Principal Software Engineer, Eclipse Mylyn
Mylyn Tasks Lead
http://tasktop.com


_______________________________________________
mylyn-integrators mailing list
mylyn-integrators@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mylyn-integrators

Back to the top