On Thu, Jun 6, 2019 at 7:21 PM Arthur Naseef wrote:
> Looking for clarification here. Our projects can depend on LGPL'ed
> dependencies, right? Here is my understanding...
>
> LGPL is not GPL, so using it as a library in our project should not force
> the license on our software - i.e. we can
Looking for clarification here. Our projects can depend on LGPL'ed
dependencies, right? Here is my understanding...
LGPL is not GPL, so using it as a library in our project should not force
the license on our software - i.e. we can still release under the Apache
License. We do need to include
We can create a component on JIRA, and add JIRAs towards those
components. Same way that we do with native now.
On Thu, Jun 6, 2019 at 5:25 PM Michael André Pearce
wrote:
>
> If we are going down the route of separate repos, are we going to have
> separate jira projects then for every plugin?
>
Same as Jboss-logging, wildfly commons is ASL. no LGPL was really added.
You had raised an issue about a test with a wrong header on a separate
thread... We can update the component as a cleanup, just to make sure about
licensing. But there's no issue per se on licensing.
On Thu, Jun 6, 2019 at
If we are going down the route of separate repos, are we going to have separate
jira projects then for every plugin?
Also just to be clear here we are talking about the
promethius-plugin
kafka-plugin
currently? Or any others also?
> On 4 Jun 2019, at 17:47, Clebert Suconic wrote:
>
> Fair
The file you referenced [1] is just a test and isn't distributed so it's
not in the jar of our dependency. My guess is that it was a mistake and
they can send a commit to re-license the file with ASL 2.
I still don't see a problem, but it's worth checking all the files.
Justin
[1]
I haven’t checked all the files, i don’t have time. But simply the parent
wildfly project is LPGL and I’ve found one file with LGPL, this is a concern,
and going forwards this is risky as they may move more files from Wildfly
project into it.
> On 6 Jun 2019, at 21:10, Michael André Pearce
>
There is a class in there which was taken from wildfly but keeps its gnu
license (as it has to)
https://github.com/wildfly/wildfly-common/blob/d8397e1174a193aaab5db510da514f6039be6742/src/test/java/org/wildfly/common/string/CompositeCharSequenceTestCase.java
As such even so they declare it
This was the dependency added:
org.wildfly.common
wildfly-common
Wildfly Common is ASL 2. See
https://github.com/wildfly/wildfly-common/blob/master/LICENSE.
I could see your point if a dependency on org.wildfly:wildfly-parent was
added as that is LGPL as you
Wildfly project:
https://github.com/wildfly/wildfly/blob/master/LICENSE.txt
> On 6 Jun 2019, at 21:01, Justin Bertram wrote:
>
> Are you sure about that? Wildfly Common is ASL 2. See
> https://github.com/wildfly/wildfly-common.
>
>
> Justin
>
> On Thu, Jun 6, 2019 at 2:47 PM Michael André
Are you sure about that? Wildfly Common is ASL 2. See
https://github.com/wildfly/wildfly-common.
Justin
On Thu, Jun 6, 2019 at 2:47 PM Michael André Pearce
wrote:
> http://www.apache.org/legal/resolved.html
>
> It’s a category x, in my understanding.
>
> > On 6 Jun 2019, at 20:46, Michael
Hi All,
Whilst i missed the vote on this as was busy, on going through it finally,
unfortunately it seems theres been an LPGL license dependency added since 2.8.0.
I’ve found the PR that introduced it, and comment on it, but we need to revert
that PR before any further releases.
Mike
> On
http://www.apache.org/legal/resolved.html
It’s a category x, in my understanding.
> On 6 Jun 2019, at 20:46, Michael André Pearce
> wrote:
>
> Hi All,
>
> It seems https://github.com/apache/activemq-artemis/pull/2661 introduced an
> LPGL dependency into ActiveMQ Artemis.
>
> Can we please
Hi All,
It seems https://github.com/apache/activemq-artemis/pull/2661 introduced an
LPGL dependency into ActiveMQ Artemis.
Can we please revert this.
Thanks
Mike
Are you able to get to this Jean-Baptiste?
If not, perhaps another PMC member can run the commands instead
(examples below)?
Thanks,
Robbie
On Thu, 23 May 2019 at 18:12, Robbie Gemmell wrote:
>
> Great, thanks Jean-Baptiste.
>
> Robbie
>
> On Thu, 23 May 2019 at 18:06, Jean-Baptiste Onofré
Hi
I notice this ticket filed from a while ago -
https://issues.apache.org/jira/browse/AMQ-7149. Currently if you wish to
use the HTTP client, you need to make sure you have the stomp module on
your classpath, as the http module references the XStreamSupport class.
I've attempted to pull the
16 matches
Mail list logo
