+1. Do we need a Jira ? I tend to think "NO", for tools and site.
Jira
Le 12/06/2018 à 08:36, Sharan Foga a écrit :
+1
It will also need changing at https://ofbiz.apache.org/business-users.html too
Thanks
Sharan
On 2018/06/12 04:59:42, Swapnil Mane wrote:
Hi Dev team,
Looking into this
Le 11/06/2018 à 20:31, Taher Alkhateeb a écrit :
There are 18 emails so far in this thread of which 13 are yours.
- You mentioned stuff from wikipedia
- then you mentioned stuff about licensing
- then you switched to birt
- then you talked about the author
- then you go back to questioning how t
First of all, I think it's always a bad idea to "comment out" any
code, and the general rule of thumb is to prefer deleting.
Second, the framework and plugins are two separate projects. You
cannot crash the standalone framework so that the plugins can work,
because you're making the framework depe
Le 12/06/2018 à 11:56, Taher Alkhateeb a écrit :
First of all, I think it's always a bad idea to "comment out" any
code, and the general rule of thumb is to prefer deleting.
Mmm, what? I just commented out to test. Your comment makes no sense to me, you
could have avoided it.
Of course it's to
Hi Jacques
We have been creating Jira’s for updates to the website
https://issues.apache.org/jira/browse/OFBIZ-9665
https://issues.apache.org/jira/browse/OFBIZ-10339
so I think consistency is good even though it is a small change.
Thanks
Sharan
On 2018/06/12 07:24:24, Jacques Le Roux wrote:
Le 12/06/2018 à 14:21, Jacques Le Roux a écrit :
com.lowagie.text.* is included in the 3.6.1 BIRT runtime jar that we use, and there is a legal agreement between the BIRT team and Bruno Lowagie to
use this version[1].
To be clear here, as you (Taher) outlined, we still need to have in our main
Yes indeed, thanks for the reminder Sharan
Jacques
Le 12/06/2018 à 14:53, Sharan Foga a écrit :
Hi Jacques
We have been creating Jira’s for updates to the website
https://issues.apache.org/jira/browse/OFBIZ-9665
https://issues.apache.org/jira/browse/OFBIZ-10339
so I think consistency is goo
I'm no longer interested in discussing this, I already explained it.
-1 on the comment
-1 on the removal
+1 on excluding the transitive dependency
If you want to fix things for BIRT, I recommend you do it _outside_
the framework.
On Tue, Jun 12, 2018 at 4:36 PM, Jacques Le Roux
wrote:
> Le 12/0
to qualify: +1 on excluding the transitive dependency after testing
that it works
On Tue, Jun 12, 2018 at 4:44 PM, Taher Alkhateeb
wrote:
> I'm no longer interested in discussing this, I already explained it.
>
> -1 on the comment
> -1 on the removal
> +1 on excluding the transitive dependency
>
That's not serious, remains a legal issue as explained at
https://developers.itextpdf.com/question/versions-older-than-5
>
Our users deserver better than saying that I could fix BIRT. You did not get
it, there is nothing to fix in BIRT.
It's unrelated. We
And for those who are not convinced:
https://developers.itextpdf.com/question/can-i-use-itext-without-respecting-agpl-license
jacques
Le 12/06/2018 à 18:15, Jacques Le Roux a écrit :
That's not serious, remains a legal issue as explained at
https://developers.itextpdf.com/question/versions-o
Thanks for your report Scott,
After checking as much as I can, here are my conclusions:
As you reported "com.itextpdf:itextpdf:5.5.6" can't be used, it's AGPL so
incompatible with ASL2
Taher suggested to simply exclude loading it. So only loading
"com.lowagie:itext:4.2.0" which is MPL/GPL
Bu
Thanks Sharan & Jacques,
Here is the Jira for the updates to the website,
https://issues.apache.org/jira/browse/OFBIZ-10433.
- Best Regards,
Swapnil M Mane
www.hotwax.co
On Tue, Jun 12, 2018 at 7:07 PM Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:
> Yes indeed, thanks for the reminder
On Tue, Jun 12, 2018 at 11:47 PM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:
> [...]
> Of course we need to ask the legal team before taking a formal decision
> about it.
> I think we have now enough material to ask, and without opposition I'll
> create a LEGAL Jira in a week.
I thin
14 matches
Mail list logo