Folks, Unless actively restrained, I will strive to cook up a minimal solution within the current methodology to get the plugin into working condition.
If the Atlassian people didn't have their frustrating attitude toward Maven Central, I'd just use their component. Once I have it working, anyone who wants to engage in major refactoring is welcome to do so. On Tue, Nov 20, 2012 at 1:10 PM, Dennis Lundberg <denn...@apache.org> wrote: > Yes, we should have a look at it. > > The github implementation in the Changes Plugin uses Mylyn under the > hood. The problem we have is that we need these implementations to play > nicely together with the good old changes.xml format. Might be an idea > to do thing the other way around - convert changes.xml issues to Mylyn > issues. > > On 2012-11-20 19:05, Jason van Zyl wrote: >> 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 >> >> >> >> >> >> > > > -- > Dennis Lundberg > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
