From: Frank Pursel <frank.pursel@gmail.com>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 32947@debbugs.gnu.org
Subject: [bug#32947] Add java-xalan.
Date: Wed, 13 Apr 2022 23:43:30 +0000 [thread overview]
Message-ID: <CANp2FMcxbFARyTOH+7xdLeb+WGPxO1-LvEhaFAU=Le41tDRZMg@mail.gmail.com> (raw)
In-Reply-To: <2533f258c513aeb666823c6c3a48748f988a9ee6.camel@telenet.be>
[-- Attachment #1: Type: text/plain, Size: 3166 bytes --]
Maxime,
You wrote, WDIT?
I think that IntStack.java has almost no economic value and so the
comparison to a commercial package is not really appropriate. We
could ask upstream (file a bug report) but the question is pretty
awkward. We are not asking for a bug fix, or for clarification of a
behaviour. We are questioning if they are meeting their own stated
licensing criteria! Besides that such a ticket is very difficult to
resolve. I would feel bad asking this of them because I imagine they
are no better equipped to answer questions about JDK1.0 than we are.
Worse, if we believe such impropriety is possible why would be believe
what they tell us anyway? I think to ask for this to be investigated,
at minimum, you would need to find the actual file from JDK1.0 that
you feel was appropriated. I don't think we should be asking upstream
to work on investigation of a suspicious licensing that cannot improve
their software in any functional way.
I appreciate your keen sensitivity to the code but I don't think this
feedback to apache is helpful and is likely not even true.
Sincerely,
Frank Pursel
On Tue, Apr 12, 2022 at 9:33 AM Maxime Devos <maximedevos@telenet.be> wrote:
> Frank Pursel schreef op ma 11-04-2022 om 16:36 [+0000]:
> > I looked at the org.apache.xml/uitls/IntStack.java file you pointed
> > out. I think the header license certainly prevails here for
> > several reasons. First it is subpackage of the org.apache tree for
> > which the source license is clearly stated.
>
> I can search for a leak of the source code of Windows, copy it to
> another project, obfuscate its origin a bit by removing author
> information, copyright information and the old license header and
> add a ASL license header and rename it to fit inside the other project.
> That doesn't make it actually ASL, it just makes it a copyright
> violation.
>
> > Second, looking at the code (without being a java guru; the code is
> > that simple) we can see that there is no dependency on any JDK.
> > The statement '@since JDK1.0' appears to be true in the sense that
> > any JDK can compile this since 1.0. We demonstrate that it builds
> > with JDK8 whenever we run this package through guix build and so, I
> > see no licensing concerns over the '@since JDK1.0' annotation.
>
> This is not what @since means, at least according to the Javadoc
> documentation (maybe Apache Xalan assigns its own custom meaning).
> According to
> <
> https://docs.oracle.com/javase/8/docs/technotes/tools/windows/javadoc.html
> >:,
>
> This tag means that this change or feature has existed since the
> software release specified by the since-text value, for example:
> @since 1.5.
>
> For Java platform source code, the @since tag indicates the version
> of the Java platform API specification [...]
>
> so IMO it looks like this code was once part of JDK 1.0.
>
> Maybe this is OK, maybe the license of JDK 1.0 allows this, maybe it
> doesn't but Apache has gained some kind of permission from Sun, maybe
> it's not legally OK, maybe it never was part of JDK 1.0. I think we'll
> just have to ask upstream what's going on, WDYT?
>
> Greetings,
> Maxime.
>
[-- Attachment #2: Type: text/html, Size: 3876 bytes --]
next prev parent reply other threads:[~2022-04-13 23:44 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-05 15:18 [bug#32947] [PATCH 0/3] Add java-xalan Danny Milosavljevic
2018-10-05 15:20 ` [bug#32947] [PATCH 1/3] gnu: Add java-cup Danny Milosavljevic
2018-10-05 15:20 ` [bug#32947] [PATCH 2/3] gnu: Add java-jakarta-regexp Danny Milosavljevic
2018-10-05 15:20 ` [bug#32947] [PATCH 3/3] gnu: Add java-xalan Danny Milosavljevic
2018-10-05 15:46 ` Julien Lepiller
2018-10-05 15:28 ` [bug#32947] [PATCH 1/3] gnu: Add java-cup Julien Lepiller
2018-10-05 16:00 ` Danny Milosavljevic
2018-10-05 16:13 ` Julien Lepiller
2018-10-05 15:52 ` Julien Lepiller
2018-12-19 14:05 ` [bug#32947] Add java-xalan Julien Lepiller
2022-03-17 21:08 ` Frank Pursel
2022-03-17 21:50 ` Maxime Devos
2022-03-17 21:53 ` Maxime Devos
2022-03-17 21:57 ` Maxime Devos
2022-03-18 17:40 ` Maxime Devos
2022-03-18 18:15 ` Frank Pursel
2022-03-18 18:22 ` Frank Pursel
2022-03-18 19:19 ` Maxime Devos
2022-03-18 17:29 ` Frank Pursel
2022-03-18 17:59 ` Maxime Devos
2022-03-18 19:16 ` Frank Pursel
2022-03-18 20:07 ` Maxime Devos
2022-03-18 20:42 ` Frank Pursel
2022-03-19 15:58 ` Maxime Devos
2022-03-22 17:45 ` Maxime Devos
2022-03-22 18:18 ` Julien Lepiller
2022-03-30 17:43 ` Maxime Devos
2022-03-30 18:41 ` Maxime Devos
2022-03-30 20:23 ` Frank Pursel
2022-04-03 8:32 ` Maxime Devos
2022-04-05 13:12 ` Maxime Devos
2022-04-05 21:09 ` Frank Pursel
2022-04-09 13:40 ` Maxime Devos
2022-04-11 16:36 ` Frank Pursel
2022-04-12 9:32 ` Maxime Devos
2022-04-13 23:43 ` Frank Pursel [this message]
2022-04-14 8:30 ` Maxime Devos
2022-04-14 16:07 ` Frank Pursel
2022-04-14 20:33 ` Maxime Devos
2022-04-14 20:49 ` Frank Pursel
2022-04-16 21:02 ` Maxime Devos
2022-04-19 17:13 ` Frank Pursel
2022-04-19 18:44 ` Maxime Devos
2022-04-19 18:55 ` Frank Pursel
2022-03-19 15:41 ` Frank Pursel
2022-03-19 16:38 ` Frank Pursel
2022-03-23 1:32 ` Frank Pursel
2022-03-23 14:14 ` Frank Pursel
2022-08-19 22:05 ` Vagrant Cascadian
2022-06-24 15:23 ` [bug#32947] [PATCH 0/3] Add java-xalan: reverse ping Maxime Devos
2022-07-14 23:46 ` [bug#32947] [PATCH 0/3] Add java-xalan Frank Pursel
2022-08-20 0:57 ` [bug#32947] Add java-xalan-interp Frank Pursel
2022-09-20 21:25 ` [bug#32947] Add java-xalan-interp CVE Frank Pursel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CANp2FMcxbFARyTOH+7xdLeb+WGPxO1-LvEhaFAU=Le41tDRZMg@mail.gmail.com' \
--to=frank.pursel@gmail.com \
--cc=32947@debbugs.gnu.org \
--cc=maximedevos@telenet.be \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).