Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [iot-pmc] Discussion/Vote on Eclipse Kapua - GXT Version: 2.2.5

Yes, exactly. Kura moved to GWT since version 2.0.


In terms of approach yes, in terms of technology let's see. The two (Kura and Kapua) have different requirements. 



Stefano

From: iot-pmc-bounces@xxxxxxxxxxx <iot-pmc-bounces@xxxxxxxxxxx> on behalf of Mike Milinkovich <mike.milinkovich@xxxxxxxxxxx>
Sent: Friday, October 7, 2016 3:59:37 PM
To: iot-pmc@xxxxxxxxxxx
Subject: Re: [iot-pmc] Discussion/Vote on Eclipse Kapua - GXT Version: 2.2.5
 

I was under the impression that Kura has recently moved from GXT to GWT.

Is that correct?

If so, does that show the path forward for Kapua?

On 10/7/2016 9:44 AM, Morson, Stefano wrote:

Hi,


I confirm the same approach used for Kura: A flag in the maven config that will make the build fully consume GXT in a non-EPL-compatible fashion and that this flag is always kept turned off at Eclipse.


I agree with the idea to look for more license-friendly alternative. Unfortunately the replacement was not possible for the first contribution that's why we asked for a works-with dependency.


Since GXT is not going to change his licensing model, we'll not consider it a long term solution and we already started planning concretely for an alternative.


Hope this answers your doubts,


Stefano

From: iot-pmc-bounces@xxxxxxxxxxx <iot-pmc-bounces@xxxxxxxxxxx> on behalf of Jens Reimann <jreimann@xxxxxxxxxx>
Sent: Friday, October 7, 2016 2:15:53 PM
To: PMC list for IoT top level project
Subject: Re: [iot-pmc] Discussion/Vote on Eclipse Kapua - GXT Version: 2.2.5
 
Stefano just joined the mailing list. This e-mail is his anchor to the discussion, so that he can reply in the same thread.

On Thu, Oct 6, 2016 at 2:20 PM, Jens Reimann <jreimann@xxxxxxxxxx> wrote:
I asked the Eurotech guys to have a look at this question.

On Thu, Oct 6, 2016 at 11:59 AM, Kai Kreuzer <kai@xxxxxxxxxxx> wrote:
The same request was done by Kura two years ago and has only been tentatively accepted by Technology PMC at that time.


Can you confirm that the same setup will be put in place for Kapua, i.e. having a flag in the maven config that will make the build fully consume GXT in a non-EPL-compatible fashion and that this flag is always kept turned off at Eclipse?

In general, I agree with Gunnar that "GPL seem risky for potential adopters“ and that it would be favorable to look for more license-friendly alternatives.

Wes stated in 2014 that "we understand this is not a viable long term option.  We are looking into others but as noted, it will take some time.  But, this is what we have today.“ 
Do I have to understand this request from Kapua in the way that GXT is now seen as the long term option after all?

Regards,
Kai


On 6 Oct 2016, at 11:25, Julien Vermillard <jvermillard@xxxxxxxxx> wrote:

+1 to "Eclipse Kapua would like to use "GXT Version: 2.2.5 " as a works with-dependency [1]."

--
Julien Vermillard

On Thu, Oct 6, 2016 at 11:24 AM, Jens Reimann <jreimann@xxxxxxxxxx> wrote:
I am assuming +1 for works-with?!

On Thu, Oct 6, 2016 at 10:20 AM, Julien Vermillard <jvermillard@xxxxxxxxx> wrote:
+1

--
Julien Vermillard

On Thu, Oct 6, 2016 at 9:00 AM, Jens Reimann <jreimann@xxxxxxxxxx> wrote:
Eclipse Kapua would like to use "GXT Version: 2.2.5 " as a works with-dependency [1].

The web component is only seen as an addition and Kapua can also work without the Web UI.

Kapua will not distribute the any binaries which contains this dependency from Eclipse download locations.

As I am an involved in the process I will not vote.

Please discuss or vote with an indication of works-with or pre-req.

Cheers

Jens

Back to the top