On Fri, Nov 23, 2012 at 1:51 PM, Jason van Zyl <ja...@tesla.io> wrote:
> It's not anymore, Mylyn is actually integrated into Netbeans now.

If someone wants to take up a son-of-changes-plugin with a plugable
issue tracker modularity, I'd gently suggest a whole new plugin in the
sandbox. For now, I'm planning to concentrate on incremental changes
to what we've got.


>
> On Nov 23, 2012, at 1:40 AM, Lennart Jörelid <lennart.jore...@gmail.com> 
> wrote:
>
>> True - but Mylyn is also unique to eclipse, unless I'm mistaken.
>>
>> Can we find a better way to support integrations from other IDEs?
>>
>>
>> 2012/11/20 Jason van Zyl <ja...@tesla.io>
>>
>>> I would honestly take a look at the Mylyn APIs for issues. They have all
>>> the connectors and I believe they have all been decoupled from OSGi. It's
>>> the most comprehensive implementation for most issue tracking systems.
>>> There is already support for JIRA there.
>>>
>>> On Nov 20, 2012, at 12:54 PM, Dennis Lundberg <denn...@apache.org> wrote:
>>>
>>>> On 2012-11-20 01:14, Benson Margulies wrote:
>>>>> Ever since JIRA 4.2, they have had a REST API.
>>>>>
>>>>> So I think that we need to make m-c-p learn to use it.
>>>>>
>>>>> Anyone else game to pitch in? Anyone mind the thought of the CXF REST
>>>>> client library as a (not very small) dependency?
>>>>
>>>> I'm interested. Haven't coded REST yet, but I'm most interested in
>>> learning.
>>>>
>>>> We probably need to rethink the configuration a bit, now that we will
>>>> have 3 different ways to communicate with JIRA. This would be a good
>>>> time to make this truly IMS-agnostic, perhaps even a 3.0 version.
>>>>
>>>> We need to have a generic interface for downloading issues from
>>>> different Issue Management Systems. Perhaps we can add it to the
>>>> IssueManagementSystem interface? It might be as simple as this:
>>>>
>>>> public List<Issue> getIssueList();
>>>>
>>>> Then each way of fetching issues would have its own implementation, like
>>>> jira-rest, jira-jql, jira-url, trac-rpc and so on. It would be good if a
>>>> suitable default implementation is selected based on the
>>>> issueManagement/system configuration in the POM. There must also be a
>>>> way for the user to force another implementation.
>>>>
>>>> Thoughts?
>>>>
>>>> --
>>>> Dennis Lundberg
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>>>
>>>
>>> Thanks,
>>>
>>> Jason
>>>
>>> ----------------------------------------------------------
>>> Jason van Zyl
>>> Founder & CTO, Sonatype
>>> Founder,  Apache Maven
>>> http://twitter.com/jvanzyl
>>> ---------------------------------------------------------
>>>
>>> I never make the mistake of arguing with people for whose opinions I have
>>> no respect.
>>>
>>> -- Edward Gibbon
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>> --
>>
>> --
>> +==============================+
>> | Bästa hälsningar,
>> | [sw. "Best regards"]
>> |
>> | Lennart Jörelid
>> | EAI Architect & Integrator
>> |
>> | jGuru Europe AB
>> | Mölnlycke - Kista
>> |
>> | Email: l...@jguru.se
>> | URL:   www.jguru.se
>> | Phone
>> | (skype):    jgurueurope
>> | (intl):     +46 708 507 603
>> | (domestic): 0708 - 507 603
>> +==============================+
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder & CTO, Sonatype
> Founder,  Apache Maven
> http://twitter.com/jvanzyl
> ---------------------------------------------------------
>
> What matters is not ideas, but the people who have them. Good people can fix 
> bad ideas, but good ideas can't save bad people.
>
>  -- Paul Graham
>
>
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Reply via email to