On Jul 18, 2006, at 11:00 AM, Gentry, Michael (Contractor) wrote:

I think I'm going to make the strategic decision, for now, that

I think you mean tactical decision ;-)

XML/DTD/etc is data and not code and doesn't need the ASF header.
Jean/etc can chime in on this later if they want.

I think that you should include the ASF header in XSD and DTD files. They are part of the IP of the project and should have the appropriate copyright notices. I don't think I'd hold up release because of this issue, but it should be done at some point.


Also, I'm not going to add headers to the generated classes, such as
_Artist.java and Artist.java, since these are produced from a template

Right.

and we don't want the standard templates to have the ASF headers in
them.

It looks like many test classes don't have headers, either, but I'll add
it to them.

Cool.

Craig

Thanks,

/dev/mrg


-----Original Message-----
From: Andrus Adamchik [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 18, 2006 11:09 AM
To: [email protected]
Subject: Re: NOTICE Text



On Jul 18, 2006, at 11:04 AM, Gentry, Michael ((Contractor)) wrote:

Ooops, misread what you said originally.  Thanks.

I'm adding the ASF license to a few files which were missing the OS
one,
but everything else is looking good so far.  Do you think
org/apache/cayenne/dba/types.xml (and kin) need it, too?  My gut
feeling
is no.

I don't know. I guess we can add the header as XML comment. Probably
wouldn't hurt.

What about HTML files?  I'm guessing no on that one, too.  At
least for now ...

At least not in cayenne-other/wiki-docs, as those are generated.

Andrus

Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:[EMAIL PROTECTED]
P.S. A good JDO? O, Gasp!

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to