Jeroen,
Would you like to work with me to try to refactor the way system
properties are handled to untangle the initialization dependencies and
to allow you to use more Classpath code as-is?
I'd like to use more of Classpath as-is but I don't think the particular
dependencies we have can be
Mark Wielaard writes:
I just looked at these two jsr's and both are not even available through
a click-through. (Strangely enough both just point to the sun 1.5.0
implementation documentation, which as far as I know doesn't include the
specs at all.)
Yes I was a little surprised to see this
David Holmes wrote:
The JCP also doesn't require the (final) specifications to be provided
under a click-wrap.
Being involved in this at present with another JSR I can assure you that the
JCP does require a click-through license for downloading specs.
I'm not saying you're wrong, but I think it
Being involved in this at present with another JSR I can assure
you that the JCP does require a click-through license for downloading
specs.
I'm not saying you're wrong, but I think it would be useful if you could
point to a specific document that states such a requriement.
I should said
David Holmes wrote:
I should said PMO rather than JCP. The JCP document itself doesn't cover
this, however the PMO seems to require it. If you look at the Spec lead
Guide on jcp.org you'll see that for Proposed Final Draft The PMO will
provide the spec license ... and then for Final Approval
However, I'm sure Spec Leads can pick their license terms, at least
within certain limits. And some JSRs are open-source, at least the
implementation.
I think the spec leads can, within-limits, define the terms for the RI and
TCK - because in a sense they own that. But they don't own the spec
6 matches
Mail list logo
