geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Geir Magnusson Jr <g...@pobox.com>
Subject Re: 1.1.1 Status - XSD and DTD issues
Date Fri, 18 Aug 2006 17:48:51 GMT
+1

Exactly.  Maybe put a note somewhere saying what schemas were used and
where a user can find them.

geir

David Blevins wrote:
> I personally don't know why we bother to regenerate that tree on every
> build as those schemas are not going to change.  Let's just build them
> once, publish the jars, delete the schemas and be done with it.
> 
> -David
> 
> On Aug 18, 2006, at 9:45 AM, David Jencks wrote:
> 
>>
>> On Aug 18, 2006, at 9:22 AM, Geir Magnusson Jr wrote:
>>
>>> If they are only used during the build process, then don't re-distribute
>>> and therefore this issue then seems out of the critical path for 1.1.1
>>> and can be solved for 1.1.1.1.1.1.1.1.1
>>
>> They are not needed at runtime, but xmlbeans packs the source schemas
>> into the jar with its other binary artifacts.  We might be able to
>> prevent their inclusion into our jars, but I don't see how having them
>> in svn is not redistribution, so I think we need allowable copies of
>> the j2ee 1.4 schemas in our svn.
>>
>> thanks
>> david jencks
>>>
>>> gier
>>>
>>>
>>> Matt Hogstrom wrote:
>>>> They are used by XMLBeans during the build process.  I guess we
>>>> could do
>>>> a one-time generation of the XMLBeans classes but I'd be more
>>>> comfortable with Jencks' input.  If you don't have the schemas you'd
>>>> have to have network connectivity to build I suspect.
>>>>
>>>> Aaron Mulder wrote:
>>>>> Can't we just ship without those?  We have pointers to them on our web
>>>>> site at http://geronimo.apache.org/schemas.html -- is there any
>>>>> additional reason we need them at runtime (e.g. does XMLBeans use the
>>>>> actual schema to validate at runtime)?
>>>>>
>>>>> Thanks,
>>>>>     Aaron
>>>>>
>>>>> On 8/18/06, Matt Hogstrom <matt@hogstrom.org> wrote:
>>>>>> All,
>>>>>>
>>>>>> For those wondering where the Geronimo 1.1.1 release is at here is
a
>>>>>> quick summary and battle plan.
>>>>>>
>>>>>> John Sisson discovered that we have several DTD and XSDs included
in
>>>>>> our build that are copies of
>>>>>> Sun's original material.  The copyright in the material seems to
>>>>>> indicate that we cannot
>>>>>> redistribute the content.  Unfortunately, as Geir has pointed out,
>>>>>> that there is no clear way to
>>>>>> interpret the license and we should manually generate these to stay
>>>>>> legal and avoid any appearance
>>>>>> of impropriety.
>>>>>>
>>>>>> The documents in question reside in both the distribution of the
>>>>>> source as well as the server
>>>>>> itself.  It appears that other open source and commercial vendors
do
>>>>>> distribute these documents in
>>>>>> their original form but the ASF does not have a clear indication
that
>>>>>> we can follow this same
>>>>>> practice.  You can find the documents in
>>>>>> $G_BUILD_TREE/modules/j2ee-schema/src/* as well as the
>>>>>> distributions in $G_DIST/schema/* directories.
>>>>>>
>>>>>> The documents are identified in JIRA
>>>>>> http://issues.apache.org/jira/browse/GERONIMO-2307.
>>>>>>
>>>>>> I'd like to ask anyone that has some spare moments to help out with
>>>>>> putting these together.
>>>>>> Basically, you need to refer to the appropriate specification and
>>>>>> type in the XML exactly like it is
>>>>>> represented for actual elements and either omit or paraphrase the
>>>>>> information embedded in comments
>>>>>> so we do not violate Sun's copyright.
>>>>>>
>>>>>> I know this is frustrating but for their own reasons Sun has imposed
>>>>>> this unfriendly copyright and
>>>>>> we need to abide by it.  We are protecting The ASF, Geronimo and
our
>>>>>> users.
>>>>>>
>>>>>> If you are working on a document please update the above JIRA to
>>>>>> indicate it is partial so others
>>>>>> can see what remains.  Please check the new schemas into their
>>>>>> respective replacements.  When the
>>>>>> replacements are complete we'll build a new distribution and run
it
>>>>>> through a full CTS test to
>>>>>> validate our work.
>>>>>>
>>>>>> Please also consider working with a partner so you can cross check
>>>>>> each other's work.
>>>>>>
>>>>>> Thanks in advance for your patience and help with this important
>>>>>> issue.
>>>>>>
>>>>>> Also, if others have input into the process that I have missed please
>>>>>> provide it as well.
>>>>>>
>>>>>> Thanks to John and Geir for discovering and mediating on this issue.
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>
> 
> 
> 

Mime
View raw message