On Sun, Nov 25, 2012 at 3:47 PM, Dennis Lundberg wrote:
> Hi
>
> Thanks for fixing the Java 6 issue.
>
> Given that there are a lot of stuff I'd like to do for a 3.0 release,
> and that there is a need to get a new version out soonish, I'd like for
> the next release to be 2.9 and include all the
Hi
Thanks for fixing the Java 6 issue.
Given that there are a lot of stuff I'd like to do for a 3.0 release,
and that there is a need to get a new version out soonish, I'd like for
the next release to be 2.9 and include all the old stuff.
When we do a 3.0 later on, I agree that we need to cut do
On Fri, Nov 23, 2012 at 1:51 PM, Jason van Zyl 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 co
It's not anymore, Mylyn is actually integrated into Netbeans now.
On Nov 23, 2012, at 1:40 AM, Lennart Jörelid 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
>
>>
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
> 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 fro
On 22/11/2012, at 1:15 PM, Benson Margulies wrote:
> On Wed, Nov 21, 2012 at 8:59 PM, Brett Porter wrote:
>>
>> On 22/11/2012, at 11:30 AM, Benson Margulies wrote:
>>
>>> Coast is clear.
>>>
>>> I have two proposals to offer:
>>>
>>> 1) Set version to 3.0, remove parameter Q support, thus
On Wed, Nov 21, 2012 at 8:59 PM, Brett Porter wrote:
>
> On 22/11/2012, at 11:30 AM, Benson Margulies wrote:
>
>> Coast is clear.
>>
>> I have two proposals to offer:
>>
>> 1) Set version to 3.0, remove parameter Q support, thus reducing the
>> complexity.
>>
>> 2) Set version to 3.0, remove all
On 22/11/2012, at 11:30 AM, Benson Margulies wrote:
> Coast is clear.
>
> I have two proposals to offer:
>
> 1) Set version to 3.0, remove parameter Q support, thus reducing the
> complexity.
>
> 2) Set version to 3.0, remove all RSS support, thus requiring JIRA 4.2.
>
> In either case, any
Coast is clear.
I have two proposals to offer:
1) Set version to 3.0, remove parameter Q support, thus reducing the complexity.
2) Set version to 3.0, remove all RSS support, thus requiring JIRA 4.2.
In either case, anyone who wants to use an older JIRA can use 2.8.
On Wed, Nov 21, 2012 at 4
Dennis, I'm hard at work on improvement. I'll send mail when I'm done.
On Wed, Nov 21, 2012 at 2:54 PM, Benson Margulies wrote:
> Dennis, I am sure I can back up cxf tonight.
>
> On Nov 21, 2012, at 2:47 PM, Dennis Lundberg wrote:
>
>> Hi Benson
>>
>> Thanks for your efforts. I'm going through t
Dennis, I am sure I can back up cxf tonight.
On Nov 21, 2012, at 2:47 PM, Dennis Lundberg wrote:
> Hi Benson
>
> Thanks for your efforts. I'm going through the code changes now. Will
> follow up in a day or two.
>
> I noticed that your changes broke the builds on Jenkins, because CXF
> 2.7.0 req
Hi Benson
Thanks for your efforts. I'm going through the code changes now. Will
follow up in a day or two.
I noticed that your changes broke the builds on Jenkins, because CXF
2.7.0 requires Java 1.6. I tried going back to 2.6.3, but got a
compilation failure:
G:\apache\maven\trunks\plugins\mave
I've checked in changes so that the maven-changes-plugin talks REST to
JIRA by default, and falls back to RSS when REST isn't there (or if
you force it).
This really requires testing. I don't have access to a copy of JIRA so
old that it has no REST. I don't have access to a copy of JIRA that
does
2012/11/20 Dennis Lundberg :
> 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 sma
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, anyon
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.x
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
On Tue, 20 Nov 2012 18:54:35 +0100
Dennis Lundberg 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 RES
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. Ha
[All join in for the chorus]
The Internet is for maven
The Internet is for maven
Some people seem to think for porn
But, maven, maven, maven!
On Tuesday, 20 November 2012, Benson Margulies wrote:
> I'd have to get it to maven central. And the comments on the forum
> page are not terrifically enc
I'd have to get it to maven central. And the comments on the forum
page are not terrifically encouraging. I'm pretty speedy at coding
rest clients using CXF.
On Mon, Nov 19, 2012 at 7:37 PM, Jason van Zyl wrote:
> You might just want to try using this:
>
> https://marketplace.atlassian.com/plugi
You might just want to try using this:
https://marketplace.atlassian.com/plugins/com.atlassian.jira.jira-rest-java-client
On Nov 19, 2012, at 7:14 PM, 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
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?
-
To un
23 matches
Mail list logo
