Re: [mylyn-context-dev] Juno SR1 MFT contribution

[Steffen Pingel <steffen.pingel@xxxxxxxxxxx>]

Okay, that sounds reasonable. I had assumed you needed something on
top of the UML2 bridge to actually make use of it but if there are
tools out there that get focus just by installing the bridge (do you
have an example?) I'm fine with listing it in a category.

We have always pointed integrators at the source for Mylyn and
provided SDKs only for convenience but didn't encourage their use.
That said, I'm okay with adding the SDK to a category since we have
been getting regular requests for them in the past.

Steffen


On Fri, Sep 21, 2012 at 11:30 AM, Miles Parker <miles.parker@xxxxxxxxxxx> wrote:
>
> UML2 is a connector that Carsten put together to support the (non-Papyrus) UML2 so that's consumer oriented.
>
> re: SDK, I'd argue for inclusion. It's positioned to be more of an end-user oriented SDK, like the EMF and GEF SDK, etc.. I don't want to make it too difficult for people who want to implement their own connector extensions.
>
> BTW, I've created a bug for Modeling asking that they consider including the Mylyn Modeling connectors there as well. Would help drive more adoption I think.
>
> BTW2, I've been using this -- especially the EcoreTools integration which provides the hierarchical editor support in the project explorer -- in the real world now for Reviews, and finding it actually useful. :)
>
> On 2012-09-21, at 11:24 AM, Steffen Pingel <steffen.pingel@xxxxxxxxxxx> wrote:
>
>> That sounds good and is how we handled categorization in the past. I
>> agree that we should only categorize features that user may want to
>> install such as the Papyrus or Ecoretools integration. Not sure that
>> also applies to UML2?
>>
>> In regard to the SDK feature I would prefer if it wasn't categorized
>> since it's target at integrators rather then end users.
>>
>> Steffen
>>
>>
>> On Fri, Sep 21, 2012 at 11:09 AM, Miles Parker <miles.parker@xxxxxxxxxxx> wrote:
>>>
>>> An embarrassed note that while I got the addition of Papyrus and UML2 support into Juno SR1, I neglected to add them to the collaboration category. By the time that change was tested, the train had left the station. So they can be consumed from there, and users can install, but only after unchecking the "Group Items by Category" box. I'm updating the Wiki to reflect that.
>>>
>>> On the same note, I've put in the fix for that and will do Kepler next. I'm thinking that we really only want the consumer (e.g. Ecoretools, UML2 and Papyrus) and SDK features listed there and not the ones that are useless by themselves (EMF and GMF). Make sense to everyone?
>>>
>>> -Miles
>>>
>>>
>>> ______________________________
>>> Miles T. Parker
>>> Senior Solutions Architect
>>> Tasktop
>>> http://tasktop.com
>>> Committer, Eclipse Mylyn and Virgo
>>> Project Lead, Model Focussing Tools and AMP
>>> http://milesparker.blogspot.com
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> mylyn-context-dev mailing list
>>> mylyn-context-dev@xxxxxxxxxxx
>>> http://dev.eclipse.org/mailman/listinfo/mylyn-context-dev
>>
>>
>>
>> --
>> Steffen Pingel
>> Principal Software Engineer, Eclipse Mylyn
>> Mylyn Tasks Lead
>> http://tasktop.com
>> _______________________________________________
>> mylyn-context-dev mailing list
>> mylyn-context-dev@xxxxxxxxxxx
>> http://dev.eclipse.org/mailman/listinfo/mylyn-context-dev
>
> _______________________________________________
> mylyn-context-dev mailing list
> mylyn-context-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/mylyn-context-dev



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