Check attached build log.
Created attachment 196344 [details] Build log
This was over an year ago, should I last rite it?
Diego, let me take a look firstly. If you don't see action from the scheme herd until September, do it.
The JAVA_PKG_STRICT error comes from the file ${S}/src/sisc/package-info.java This file is (almost) empty, it only contains a comment and a package declaration. I don't know if empty source files are legal for 1.4 specs, but removing that source file before compilation does not seems to break anything. There is nothing the scheme herd can do here, apart from removing that file. @java herd Any comment, suggestion, idea or solution for this?
Java team, can you answer or do we have to kill this?
masked. java: feel free to unmask this once it's fixed
(In reply to comment #6) > masked. > > java: feel free to unmask this once it's fixed > I doubt anyone in the Java team is interested in the long term in this package.
(In reply to comment #7) > (In reply to comment #6) > > masked. > > > > java: feel free to unmask this once it's fixed > > > > I doubt anyone in the Java team is interested in the long term in this package. > And should have remembered to note that we are not the maintainers.
If anyone is wanting to continue maintaining this package then I suggest that Comment #4 is a perfectly acceptable solution.
Thanks Alister to recenter the discussion to its content. Just for information, I engaged myself to help the understaffed scheme herd, and I was asked to take care of this bug, whose resolution is generally trivial (often bad javacflags). (In reply to comment #7) > > I doubt anyone in the Java team is interested in the long term in this package. The package is currently maintained by pchrist and the scheme herd (according to the metadata file). So it is (or was, at the moment I try to solve this issue) not about transferring the maintainership to the java herd, I only asked for advice. I, and the scheme herd, are not Java experts, and I hoped that someone in the java herd could help me and the herd solving this issue, by answering an easy (of I think it should be easy for a java expert) question: Q: Are empty (i.e. containing only a package declaration) java source file legal in the sense of the 1.4 spec? If yes, then some investigation might be needed to know why the checks enforced by JAVA_PKG_STRICT fails. I can do this investigation, I just needs hints about what can cause such issue, because I'm not familiar with eclasses, and I don't want to have to debug it. If those source files are not legal, then I expected one reaction from someone from the java herd about the removal of that file, like "you should do that", or "go with it". Thus, Alistair, thanks you very much for giving the agreement of removing the bad file in comment #9
Couple of months later... Nobody was willing to fix this... Removed from tree.
